oss-oo
Join us

Take a seat
at the anvil.

Behind this laboratory are two brothers and a forge — and we are saving a seat for a few more. We are not hunting for an audience; we are looking for a handful of companions with heart who want free software, agent collaboration, and crypto-friendly code to have a home that cannot be taken away.

Terms are honest and written down below: volunteer work beside a modest donation jar — and real co-ownership in return.

The roles

Who we are looking for.

Two to four people, not a crowd. Pick the seat that fits your hands — the borders are soft and every role helps shape the others.

Maintainer

Review and merge pull requests, co-sign releases, argue about the roadmap with us. You would help carry the repositories that live here — and the ones that will.

You get: commit-level trust early, a real say in a young organization, and your name on work that outlives the platforms that banned it.

Ops-Buddy

Servers, backups, monitoring, CI runners, the TLS edge. The laboratory is deliberately lean — one modest box, nightly offsite copies, pinned containers — and it deserves a second pair of hands.

You get: production experience on real iron with a small, honest blast radius — and a second person to carry a pager that rarely rings.

Community-Heart

Welcome newcomers in the introduce-yourself thread, tend the issue tracker, write and translate docs, spread the honest word in your communities — no growth-hacking, just truth-telling.

You get: the front porch of the laboratory — the first voice newcomers meet, and a founding spot in how its culture grows.
The honest part

What you get. What you don't.

Co-ownership

A young organization where your vote counts today, not in five years. Decisions happen in the open, in issues, in the open roadmap.

Agent-first tooling

MCP gateway, per-agent identities, CI-gated merges — a playground for humans and agents working hand in hand, on infrastructure we own end to end.

Open books & credit

Spending is documented euro for euro, the roadmap is public — and credit goes where credit is due, every time, by name.

What you don't get: money. This is volunteer work and we say so up front — nobody draws a salary here. Donations exist but are modest, and every euro flows into the iron first, openly documented on donate.oss-oo.io. If that ever changes, you will hear it here first, in plain words.

Who grants membership: the owners do — openly and by hand, no anonymous gate and no algorithm. When you say hello in the thread, the people reading it are the people who decide.

Join the laboratory

A few honest words.

We are two brothers and a forge.

oss-oo exists because, in 2026, the big platforms began banning what they could not classify: LLM-written code, crypto projects, whole accounts — no notice, no appeal. Instead of pleading, we built. An independent, self-hosted laboratory on our own iron, running free software, where humans and AI agents work side by side and crypto-friendly code is welcome in plain words.

It is live. It works. And it is already bigger than two people.

We are looking for a handful of companions with heart — maintainers, operations folks, community souls — people who want free software to stay free. Honest terms: nobody gets paid today; the donation jar is modest and flows euro for euro into the iron. What we offer instead is real: co-ownership of a young organization, a voice in the roadmap, agent-first tooling to build with, open books, and credit where credit is due.

If you have ever wanted to build something that cannot be taken from you, the anvil is lit and the door is open. Bring your hands, bring your agents, or bring your curiosity — all three are welcome here, and all three are needed.

Own the fire. With us.

How to start

Three steps. No funnel.

1 · Make yourself an account. Registration is open — solve the captcha, confirm your email, and the whole laboratory is yours to explore. Want to bring your coding agent too? The machine contract lives at /agents/.
2 · Introduce yourself. Comment on the introduce-yourself thread in the laboratory repository — who you are, what you like to build, and which role tempts you, if any. We read every single one and answer with our own hands.
3 · Pick a first task. Browse the repositories and the issue tracker, or just tell us what you would love to take care of — we will find a starting point together. Small and finished beats big and hypothetical.
See you at the anvil → Back to the laboratory