01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Web2 · Service Software maintenance and support
A named team that keeps your software running: monitoring, security patches, dependency upgrades, bug fixes and small features, with an agreed response time.
In short
Software needs attention after launch: dependencies age, security patches arrive, usage grows and small bugs surface. We take on the running of systems we built — and systems we did not — with a named engineer, monitoring and alerting, a monthly allocation for fixes and improvements, and a response window agreed in writing.
- How to engage
- Dedicated engineering pod, Modernization audit
- Practice
- Web2
Signs this is the right service
- The team that built the system has moved on, and nobody is confident changing it.
- Frameworks and dependencies are several versions behind and security advisories are piling up.
- Incidents are found by customers before they are found by you.
- You need small, steady improvements but not a full-time team.
What you get
Takeover audit
A review of code, infrastructure, access and documentation before we accept responsibility, with the risks written down.
Monitoring and alerting
Uptime, errors, performance and cost watched continuously, with alerts that reach a person.
Security and upgrades
Dependency updates, security patches and framework upgrades on a schedule, tested before release.
Fixes and small features
A monthly allocation of engineering time, prioritised with you, for bugs and improvements.
Incident response
An agreed response window, a named engineer, and a written review after any serious incident.
The process
- 01
Audit and access
We read the system before we promise anything about it, and set up least-privilege access.
- 02
Stabilise
Monitoring, backups, a tested restore and the most urgent patches come first.
- 03
Agree the cadence
Response windows, the monthly allocation and how work is prioritised, in writing.
- 04
Run and report
A monthly report of what was fixed, upgraded and spent, and what we recommend next.
TypeScriptNode.jsGoPostgreSQLAWSTerraformOpenTelemetry
Software maintenance & support: common questions
Do you support software you did not build?
- Yes, after a takeover audit. We need to understand a system before accepting responsibility for it, and the audit tells you what state it is in.
What response times do you offer?
- They are agreed per engagement and written into the contract, according to how critical the system is and the hours you need covered.
How is support priced?
- As a monthly retainer sized to the system and the response window. How unused time is treated is agreed up front.
What if the system needs more than maintenance?
- The audit will say so. If a rewrite or a migration is the honest answer, we scope it separately instead of hiding it inside a support contract.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.