Open Source & Reuse

AI-generated, human-reviewed

For public administration, reuse has become policy: what is built with tax money should not cost another authority a second time. Open CoDE is the shared platform German federal and state governments provide for exactly that.

The gap between “published on Open CoDE” and “actually reusable” is wide, though. A repository that hard-wires one authority’s configuration, carries no licence or ships an undocumented data model is public — and still reusable by nobody. We build software so that gap disappears.

Typical project scope

• Licence selection and upkeep: EUPL-1.2 or AGPL-3.0, with third-party code cleanly separated so the framework’s licence is not mistaken for yours
• Separation of the reusable core from tenant-specific configuration
• A documented data model with consistent field conventions — the precondition for a second municipality to use the same structure
• Interfaces rather than bespoke routes: a REST API alongside the UI so specialist systems can dock on
• Reproducible deployment (Docker), so adoption does not fail at setup
• Operations and maintenance after publication — open source without upkeep is an archive

What we settle first

Publishing does not automatically mean anyone adopts. So we establish early who the audience is, what that audience actually needs in order to take the code over — licence, installation path, a named contact — and who answers outside contributions later. A repository without an addressee is effort without effect.

Next step: Get in touch