Service · Software developmentSoftware development
Maintenance and support that keep your software boring, in the good sense
Our maintenance service keeps your website, app or platform running and up to date every month: dependency and security updates, health checks and monitoring, daily snapshots, automatic certificate renewal, bug fixes and small improvements. Every change goes through a test environment first, and you get a plain monthly note of what was done.
What we do for you
- A first audit: what runs, how it is deployed, what is backed up, what would break first
- Health checks on every service and monitoring that alerts us before your users notice
- Daily snapshots of servers and regular database backups, with a restore actually tested
- SSL certificates renewed automatically
- Security and dependency updates applied in dev, checked in uat, then released to prod
- Bug fixes and small changes within the scope agreed each month
- A monthly note in plain language: incidents, updates, changes, what we recommend next
Who it is for
- Fits: businesses whose app was built by a freelancer or agency that is no longer around
- Fits: teams that ship features but have nobody watching servers, backups and updates
- Fits: owners who want one contact who knows the system when something goes wrong
- Does not fit: systems we are not allowed to read or deploy; we need access to the code and the servers
How we run our own systems
This is what we do every day on our own infrastructure, and what we bring to yours: every project has dev, uat and prod environments and a preview address per branch; builds run on GitHub Actions, never on the production server; apps run with Docker Compose and health checks; servers get daily snapshots; a failed release rolls back automatically. Agents watch our servers every five minutes and feed a health page; we also automated SSL renewal on four AWS servers.
The building blocks
- Health checks. Docker's HEALTHCHECK instruction tells Docker how to test that a container is still working; a container that fails it is marked unhealthy, which our monitoring watches.
- Snapshots. On Google Cloud, snapshot schedules back up persistent disks automatically (hourly, daily or weekly) with a retention period you must set; Google recommends them as a best practice for Compute Engine workloads. We use the equivalent on other clouds.
- Certificates. Let's Encrypt issues certificates through the ACME protocol; renewal means repeating issuance, so we automate it rather than rely on a calendar reminder.
- Releases. Changes are built on GitHub Actions, a CI/CD platform that builds, tests and deploys code when events happen in a repository.
What happens when something breaks
- Detect. A health check or a user report raises an alert.
- Contain. Roll back the last release or restart the failing service; restore from a snapshot only if needed.
- Tell you. A short message with what happened and what is affected, as soon as we know.
- Fix. The cause fixed in dev, verified in uat, released to prod.
- Learn. A note in the monthly report and, if useful, a new check so it is caught earlier next time.
What we need from you
- Access to the code repository, servers or cloud accounts, and the domain's DNS
- The list of people to warn in case of an incident, and when
- Your priorities: what must never stop, what can wait until Monday
Questions we get
Can you take over an app we did not build with you?
Usually yes. We start with a short audit and tell you plainly what is risky, what is missing (backups, tests, environments) and what we would fix first.
Do you guarantee 100% uptime?
No one honestly can. We set up the checks, backups and rollbacks that keep incidents rare and short, and we report every one of them.
What counts as a small change?
Text, settings, a new field, a minor fix: things that fit in the monthly time agreed. Bigger features are estimated separately before we start.
Where is our app hosted?
Where it makes sense: on our own server with Docker, on your cloud account, or where it already runs. The code and data stay yours.
Sources
- Docker Docs: Dockerfile reference, HEALTHCHECK (checked 2026-10-06)
- Google Cloud documentation: create schedules for disk snapshots (checked 2026-10-06)
- Let's Encrypt: how it works (checked 2026-10-06)
- GitHub Docs: understanding GitHub Actions (checked 2026-10-06)