Open source

Three forges, and a rule about who wrote the code

We publish what we build. Where it goes depends on one question: how much of the code was written by a machine. That distinction is not a purity test — it is a maintenance contract, and we would rather state it than let people guess.

Publication policy

Where a repository is allowed to live

AI-assisted accepted

GitLab CE

Self-hosted, on our own instance, and the primary home of everything we publish. Repositories are public and readable without an account. AI-written code is welcome here as long as it is reviewed by a person who can explain every line — which is the only licence condition we actually enforce.

  • Public, no sign-up to read.
  • Issues and merges open.
  • Primary forge, mirrored outward.
AI-assisted accepted

GitHub

A public mirror of the same repositories, for the people who will never hear of a self-hosted instance. Same content, same licence, same commit history — not a reduced copy. Issues are handled on the GitLab side and mirrored back.

  • Read-only mirror of GitLab.
  • No accounts required to read.
  • Releases mirrored with the tags.
Human-written only

Codeberg

Reserved for code written by human beings, start to finish, and only once it is a product rather than a fragment. Nothing has been published there yet. When something is, it will be because we want a forge that cannot be bought — not as a gesture of purity.

  • No AI-assisted commits, ever.
  • Only when the tool is usable.
  • Currently empty — honestly.

Every repository carries its licence in the repository root, a human-readable description, and a statement of how much AI assistance the code received.

The catalogue

Projects we build, with the forge they belong on

Snapshot · September 2026

No public repository yet

As of September 2026 none of our repositories is published under a public account. The five builds listed below exist and are running; they sit in private repositories or in repositories owned by the partner organisations that commissioned them. We will publish them as each reaches a state worth reading — not as a screenshot gallery.

If you maintain one of these projects and want your organisation’s copy to stay where it is, say so and we will list it here as external instead of moving it.

Rust backend

ChosenImpact backend services

Catalog and pricing comparator, telemetry and feedback service, plus three shared crates: pricing engine, provider adapters for five clouds, and the zero-PII common library. Owned by ChosenImpact MTÜ.

partner-owned
Go + React

Eesti Open Policy Design Dashboard

Public-source policy design platform on Go, PostgreSQL with PostGIS, and deck.gl. Published on a Gitea instance under VEIS MTÜ, AGPL-3.0, attribution notice mandatory in any deployment.

public · AGPL-3.0
Packaging

Epson Perfection 3170 driver package

The 32-bit SANE bridge for a 64-bit Ubuntu, packaged as an amd64 .deb and verified on Ubuntu 26.04. Small enough to read in an afternoon, useful enough that people keep asking for the package.

ready to publish
Automation

Form-routing pipelines

The three webhooks behind this site’s contact, data subject and abuse forms: validation, language tagging, dead-letter queue and a plain-text archive. The first candidate for publication.

ready to publish
Web

This website

Static HTML, one stylesheet, six language files and a canvas cellular automaton. Every token, radius and motion duration is written down in brand-spec.md, which travels with the code.

private until decided

Licences

Copyleft where it matters, permissive where it helps

A repository owned by a partner keeps the partner’s licence. Our own tools default to a licence that keeps improvements in the commons, and each one states it in the first screen of the README.

Licence and attribution obligations per project.
Project Licence Obligation
Eesti Open Policy Design Dashboard AGPL-3.0 Keep the VEIS MTÜ attribution visible in the interface. Removing it is a violation.
ChosenImpact backend Partner licence Follow the licence chosen by ChosenImpact MTÜ; we do not relicense their code.
Our own tools AGPL-3.0 default State it in the README. Apache-2.0 on request for a plugin or a driver.