Operations
Operations & infrastructure
Your system runs and somebody is responsible for it: deployment, databases, monitoring, provider migrations.
What you get
- Deployment, database operations and monitoring, with alert rules taken from real failures
- Provider migrations, costed before they start
Approach
How we go about it
We take on operations for the systems we built: deployment, databases, updates, backups. Alert rules come out of the failures that actually occurred, so the same fault is noticed next time before a user reports it. If a provider gets too expensive, we cost the migration before we propose it. When something fails: we monitor availability, error rates and database load. An alert goes to us, not to you. What counts as an incident, the hours in which we respond and how quickly, are set per system in the contract — that depends on what the system does and what an outage there costs. We do not make blanket commitments before we know the system.
Operations in the log
Entries of this kind from every system we have worked on.
- Operations
Turned a real outage into alert rules, so the same failure is noticed next time before anyone phones about it.
- Operations
Built our own bare-metal Kubernetes cluster, because managed nodes would have cost more at this load profile.
- Operations
Moved tenant separation into the infrastructure: a namespace, a database and a network rule of its own for every tenant.
- Operations
Automated hibernation for idle tenants: shutting them down and starting them again on demand.
More services
The other services
Build
Software & platforms
Applications and multi-tenant platforms for companies whose processes no longer fit a standard product.
Data
Data & analytics
Bringing figures from separate systems together, reconciling them and making them fit to report on — including the places where two systems give different numbers.
Build
AI integration
Putting language models into existing processes: a fixed output format, visible cost, a swappable provider.
Build
Automation
Letting software do the recurring manual work — with a dry run, an approval and a log.
Advisory
Advisory & architecture review
A second pair of eyes on architecture, security, and which part of the plan can be dropped.
Training
Training & enablement
Your team takes the system over and carries on developing it.
We will tell you whether this is the right service.
Describe in a few sentences which system this is about and what it has to do. We will tell you which service fits and what a first step looks like.