It runs, and it should keep running.
Something is finished — and that is where the work nobody sees begins. We maintain and operate software, servers and websites, including things we did not build ourselves.
What we do
Updates to the server, the runtime and the dependencies. Certificates, before they expire. Backups that can actually be restored. Someone watching whether it still runs — and telling you when it does not. Small changes while it is live, without a project around them.
What we do not do
We take nothing on blindly. Before the first monthly invoice there is an inventory — what we have not understood, we cannot hold.
How it runs
- Inventory. We look at what is there: technology, access, backups, open ends. The result is a list with findings, not an invoice.
- Handover. Access, monitoring and backups are put in order and documented — so that somebody else could carry on.
- Operation. Monthly, with a short report: what was done, what was noticed, what is coming up.
What we already hold
The sites and the reservation platform of Bürgerinitiative Flingern run on our server and are operated by us — including the peak just before the street festival, when everyone checks the programme at once.
That we also take on other people’s work is not a claim: the Global Bucket Solutions site had been unreachable since December 2025. One day after the handover a landing page was up — at the previous provider, without a migration. Both are listed under References.
What it costs
Monthly, by scope. A modest site is a low two-figure sum, an application with a database and sign-in is more. The inventory is charged once and credited back once the operation starts.
If nothing has been decided yet
If it is not yet settled whether what exists should be carried on at all, that is not an operations question. darue settles that first — and is not bound to an answer that says Karuki.