Continuity
Codebahn is run by one person. That number does not change by promising it will. So this page works the other way: it makes the damage small instead of pretending the risk is not there, scenario by scenario. The founder's own account of why is on the blog: what happens if I'm not here.
Three things you can do today, without asking us:
- Clone. Every clone is a complete copy of the repository, history included.
- Mirror. A push mirror to a second host keeps a live copy elsewhere with every push.
- Export. The organisation export restores into stock Forgejo, and the round trip has been tested.
The founder dies or is ill for months
In place: the three steps above, none of which need us. Backups go daily to a second provider in another EU region, and a restore is tested every week, as described on the security page and repeated in the Security and Exit Addendum for Assurance and Custom.
In progress (as of 21 September 2026): a second engineer under contract with Hackerman AB, bound by the same confidentiality obligations as an employee, able to keep the service running and to tell customers what is happening. As of 21 September 2026, nobody but the founder has access.
Planned: alerts that reach that engineer when the founder goes quiet.
The founder is still here but has stopped
In place: what you can check yourself: the dated changelog, the status page with its history, and the weekly restore test.
There is nothing to promise here. This scenario resists structural fixes; the signal is visible to the customer, not to us.
The money runs out
In place: Codebahn is self-funded, with no investors. If we end the service, you get at least 90 days' written notice (Terms 10.6). The domain codebahn.net is registered until 29 April 2028, checkable in WHOIS.
In progress (as of 21 September 2026): moving infrastructure to direct debit against a balance kept ahead of running costs by at least six months.
Someone offers to buy the company
In place: there are no investors, so nobody can force a sale. If the company were sold, the Terms require 30 days' notice of assignment (16.3), the exit terms (10.5 to 10.9) still hold, and leaving costs nothing (10.8).
We make no commitment about whether a sale could happen.
We decide to stop
In place: at least 90 days' written notice (10.6). After the end, your organisation stays readable for 30 days (10.4, 10.7). A switch we help with completes within 30 days (10.5). No exit fees (10.8). The procedure is at Leaving.
A dependency fails or there is a breach
In place: backups sit with a different provider than production. Incident communication follows the process described on the security page.
In progress (as of 21 September 2026): the contracted engineer described above, so an incident is handled when the founder is unreachable.
Insolvency or another legal event
In place: the exit terms above. For Assurance and Custom, the addendum 8.4 says they survive "to the extent we are able to perform them". The protection that does not depend on us is the copy you already hold: clones, mirrors, exports.
Bankruptcy law can override a contract. That is true here as anywhere.
This page is reviewed every six months, and sooner if one of the "in progress" rows above becomes true.