Service
Hosting and maintenance
After launch, a system needs someone to update it, keep a copy, and notice when it stops — that is our job.
Who it is for
Clients who do not want to run a server themselves, or who want a second pair of eyes on a machine at their site.
What it covers
- Running a web app, Nextcloud, or an operator system
- Backups, and a check that a copy actually opens
- Updates in an agreed window
- A channel for failures during working hours
What you get
- The same team that wrote the system also runs it
- A backup is restored once as a test, not only created
- A clear list of what the care includes
How we do it
We host with us or maintain an installation on your network, watch whether the system is breathing, and keep a backup we actually test to open — not one that merely “exists”. We update in agreed windows, and during working hours there is a living person on the channel when something breaks.
Everything is written down in advance: what we monitor, how far back we keep copies, and when someone is there to pick up — no endless promises. The same team that wrote the system also runs it, so it knows every corner. And maintenance is not mandatory — you can take the code and look after it yourself; care is a separate agreement.
How an engagement runs
01. Place
We decide where the system lives and who can sign in.
02. Launch
We deploy it and check the address and the first login.
03. Copies
We take a backup and restore it once to prove it.
04. Rhythm
We write when updates happen and how a failure is reported.
Questions on this topic
Do you keep data in a public cloud?
Only if that is written down. By default we mean a machine with us or with you, not a shared account in someone else’s panel.
Is maintenance required?
No. You can take the code and run it yourselves. Maintenance is a separate agreement.