Announcement
Launching konnos.
the forge that respects your code
Why
Modern code hosting consolidated into a handful of US-based platforms whose terms of service grant them broad rights to use the code stored on them. For most teams that’s a quiet compromise — convenience traded for a thin slice of agency. For some teams it isn’t.
konnos is for the second group. A forge you self-host on hardware you control, in a jurisdiction you choose. Data sovereignty is the entire point. GDPR is native, not a checkbox. No telemetry, no model training on private repos, no automatic upselling.
What konnos is today
A self-hostable forge distribution. A charcoal-and-hot-rose theme, a custom logo and login surface, a Docker Compose file tuned for production, and a migration script that moves entire orgs and personal repos from GitHub to a fresh konnos instance with LFS intact.
The reference instance is the one running this very site: code.konnos.org. The same Docker Compose that runs that instance ships in the repo. If you can run a single container behind a reverse proxy, you can run konnos.
What konnos is NOT today
Honest scope is part of the point. konnos at v0 is a forge that respects your code — and nothing more.
- ·No SaaS offering. You self-host. That’s the whole product.
- · No plugin system beyond what the core forge supports.
- · No editor or IDE-side integrations.
- ·No marketing language about being “AI-native” or any flavor of AI feature. konnos at v0 doesn’t ship those, so it won’t claim them.
When something new ships, the docs and the ROADMAP get a ✅. Until then, the badge is 📋, and we treat the feature as something we’d like — not something you can install.
How to try it
On any Linux box with Docker:
git clone https://code.konnos.org/konnos/konnos.git cd konnos cp .env.example .env # set POSTGRES_PASSWORD docker compose up -d
Visit your domain, complete the install wizard, sign in. For production, the same docker-compose.yml is what runs code.konnos.org.
How to help
The good first issues are the easiest entry: scoped tickets with clear acceptance criteria. Theme work, locale translations, deploy guides for other PaaS providers, a make-verify CI target.
Real-time chat is in the Matrix room. Async discussion is on the issue tracker. The CONTRIBUTING file covers the DCO sign-off and code style.
konnos is BDFL today (one maintainer, casting vote on direction). Five active contributors with three merged PRs each over a six-month window triggers an elected maintainer council. See GOVERNANCE for the trigger details.
Thanks
konnos stands on the shoulders of two decades of open-source forge work. Inherited copyright notices and license terms are preserved verbatim in LICENSE.
Read the source. Try the quickstart. See you in the community.
— flndrn