Software maintenance and support for the systems you depend on
Someone has to keep the lights on after the original team moves on, and read the code before touching it.
- Django
- Python
- Linux
- AWS
- Oracle Cloud
What we build
What maintenance and support covers
We keep software running after the launch is over: taking over codebases the original developer can no longer support, patching dependencies, triaging bugs and upgrading frameworks before they become a liability. We extended the Django application behind HoRes Hospitality Solutions, delivering the changes they needed while making the code easier to maintain, and we run Sera, our own app, on iOS and Android for thousands of users ourselves. The same discipline applies to code we did not write.
-
01
Codebase takeover and onboarding
We read the code, set up a working local environment and map the architecture before we plan or promise any change.
-
02
Initial audit and health report
Dependencies, security exposure, test coverage, deployment process and documentation gaps, written down so you see the real state.
-
03
Dependency and framework upgrades
Libraries, frameworks and language versions kept current in small, tested steps instead of one risky jump years later.
-
04
Security patching and hardening
Known vulnerabilities in dependencies, configuration and access fixed and prioritized by what is actually exposed.
-
05
Bug triage and prioritization
An open issue list turned into a ranked plan agreed with you, so effort goes to what affects users most.
-
06
Monitoring, alerting and backups
Failures caught before users report them, with backups checked by restoring them, not just by confirming they exist.
Typical problems we solve
Situations that bring teams to us
-
The developer who built this is gone.
We start every takeover the same way, an audit of the code, its dependencies, tests, deployment and documentation, before we plan or touch anything.
-
Something breaks and nobody knows why.
We put monitoring and alerting in place so failures surface with enough detail to find the real cause, then fix that cause, not just the symptom.
-
We are afraid a rewrite is the only way forward.
We default to small, continuous improvements to the code you already have, and only recommend a rewrite when the audit shows it genuinely pays off.
-
Requests keep piling up and nothing gets decided.
We turn the backlog into a shared, ranked list based on impact and risk, and review it with you regularly instead of working by whoever asks loudest.
Relevant work
Work we have delivered.
A selection of projects our engineers have built and shipped. Open any of them for the details.
-
Smoother days for hotel staff
Django improvements for HoRes Hospitality Solutions
We improved and extended the Django application behind a hotel management system, delivering the requested changes quickly while making the code easier to maintain and daily work clearer for hotel staff.
Own products
We ship and run our own software, too.
Products we design, build and operate ourselves, used by real people every day. Your project gets the same care.
-
Cycle and intimacy tracker
Sera
A private cycle and intimacy tracker built for women who value privacy. Deployed on iOS and Android and trusted by thousands of users.
How we work
How we take over and keep it running
-
01
Audit before we touch anything
We read the code, run it locally and check dependencies, security exposure, tests and deployment before proposing changes.
-
02
Agree what to fix first
Audit findings and your bug list become one ranked plan, agreed with you, instead of a queue worked in arrival order.
-
03
Small, verified changes
Fixes and upgrades ship in small steps with tests and monitoring, so we see the effect of each change on its own.
-
04
Stay on, document, hand over
Documentation is kept current as we go, so your own team, or another one, could pick the codebase up at any point.
How every engagement runs
-
Clear scope and estimate
You know what you get, when, and what it costs before work starts.
-
Working software early
Short iterations with results you can see and test.
-
Transparent communication
Direct contact with the engineers, regular updates and no surprises.
-
Support after release
We stay responsible for what we delivered.
Questions and answers
Frequently asked questions
-
Can you take over a codebase with no documentation?
Yes, this is a normal starting point for us. We begin with an audit: reading the code, running it locally, checking dependencies and tests, and writing down what we find. That audit becomes the basis for what we propose next, and for the documentation the project was missing.
-
What happens when something breaks in production?
We diagnose from logs and monitoring rather than guessing, fix the underlying cause, and tell you what happened and what changed. Where monitoring or backups were missing, fixing that gap becomes part of the work so the next incident is caught sooner.
-
How do you decide what gets fixed first and how long it takes?
We rank the backlog by impact and risk together with you rather than working requests in the order they arrive, and revisit that ranking as priorities change. Timeline depends on the size of the change and what else is in flight, which we discuss request by request.
-
Do we still own the code, or does maintenance lock us in?
The code, repositories and accounts stay yours throughout. We document as we work specifically so another team could take over if you ever wanted that, which is also how we approach codebases we take over ourselves.
-
Will you rewrite our software or improve what is already there?
Our default is small, continuous improvement to the code you already have, since a rewrite carries real risk and cost. We only propose a rewrite when the audit shows the existing code genuinely cannot be extended safely, and we explain why before recommending it.
Contact
Tell us what you need kept running
Describe the system, its stack, how it is hosted and any documentation you have. We will reply with the questions we need answered before we can start.
- We get back to you as soon as possible.
- A short call to understand your goals and scope.
- A written proposal with an estimate. No obligation.
Message sent!
We'll get back to you soon.
Capabilities
Other services
-
Websites
Fast, search-friendly websites that explain what you do and turn visitors into enquiries.
-
Web applications
Customer portals, internal tools, dashboards and workflow systems on backends built for real load.
-
AI agents and automations
AI agents, integrations and automated workflows that take repetitive work off your team and run reliably in production, not just in a demo.
-
Desktop programs
Cross-platform desktop applications for demanding workflows, specialized hardware and data visualization.
-
Mobile applications
Android and iOS apps, from public app-store products to internal tools for teams in the field.
-
Embedded software
Firmware and control software for devices and specialized hardware, connected to the apps and systems around them.
-
Consulting and architecture
Requirements, technology choices, architecture review and delivery planning, so you invest in the right thing from day one.
-
Not sure which service fits?
Describe your project and we will recommend the right approach, even if it is not us.