GET INVOLVED
zegit is early. The thesis is set, the core is being built in the open — and the best time to shape it is now.
We are a small team of engineers based in Sweden. We built zegit because we have lived the gap between "we follow good practice" and being able to prove it — the audit that reconstructs a story from CI logs, the release that nobody can say with certainty went through the right controls. That gap is uncomfortable enough at human scale. With autonomous coding agents entering the picture, it becomes a structural problem. The EU Cyber Resilience Act makes it a legal one.
We are opinionated about how good engineering works: test-driven, trunk-based, continuous delivery — not as a methodology preference but because those three disciplines are the structural prerequisites for a coherent, tamper-evident evidence record. We build in the open. The platform is pre-release and under active development; the thesis is set, the toolchain is taking shape, and the evidence model is still being defined — which is exactly why design partners matter now.
To be concrete about "early" — so you know what you'd be looking at:
unsigned to validated to a signed, in-toto attestation.Not ready to reach out yet? That's fine — say hello at info [at] zegit.dev and we'll keep you posted as things land. No list, no spam — just a reply when there's something real to show.
For teams who want provable delivery now — especially those facing CRA obligations or bringing coding agents into a regulated codebase. Work directly with us: shape the roadmap, get hands-on help wiring zegit into your pipeline, and influence the evidence model before it sets. We are taking a small number of design partners at this stage.
For people who want to support the initiative — angels, operators, and others who believe good engineering should be the path of least resistance and that compliance should fall out as a byproduct. Reach out to talk about backing zegit.
Email us at info [at] zegit.dev. Tell us which track interests you — design partner or backer — and a sentence about your setup or what drew you to the project. We read everything and reply to everything.