Nobody owns it any more.
The contractor or agency that built it has moved on. Your team uses the app every day. But keeping it running is nobody's job. So nobody does it.
Managed operations for custom Next.js apps
Your Next.js app, looked after. Without hiring anyone.
We take over the day-to-day running of the app your agency built: monitoring, patches, deploys, backups and incidents.
- price
- from [$X] / application / month
- stack
- Next.js · React · Node
- hosts
- Vercel · AWS · VPS
01The problem
It works. Until it doesn't.
Custom apps rarely fail all at once. Small things slip, and nobody is watching.
Small failures go unnoticed.
A certificate expires. A dependency gets a critical security advisory. A deploy fails halfway. Each is a small fix on the day. Found by a customer six hours later, it's an outage.
A full-time hire is the wrong size.
Most months, a stable app needs a few hours of skilled attention. A full-time engineer means a full salary for that. They take time to hire. And when they're on leave, you're back where you started.
02The service
What we take over
Six areas move from nobody's job to ours. Each one shows up in your monthly report.
-
monitor
Monitoring and alerting
Uptime and performance checks, with alerts that reach an engineer, not an unread inbox.
-
patch
Dependency and security patching
Updates and security fixes are tested in staging before anything reaches production.
-
deploy
Deploy pipeline
We keep builds and deploys working as Node, Next.js and your host change underneath them.
-
backup
Backups and restores
Scheduled database and asset backups, with restores we actually test.
-
incident
Incident response
When something breaks, we respond within an agreed window and keep you updated until it's resolved.
-
report
Monthly report
What we changed, what we caught, and anything that needs a decision from you.
03How it works
How we take it over
Three steps. You keep ownership of everything. We take on the work.
-
Step 1
Access and audit
You give us access to the repository, hosting, DNS and database. We review how the app is built, deployed and backed up. You get our findings in writing before we change anything.
-
Step 2
We instrument and take the queue
We set up monitoring, alerting and backups, and fix what the audit flagged as urgent. From then on, alerts, security advisories and failed builds come to us first.
-
Step 3
Monthly report and a named contact
Each month you get a written report. You also get a named contact who knows your app and answers your questions directly.
04Stack
Built for custom JavaScript apps
We look after applications written in JavaScript or TypeScript by developers, on this stack.
- Framework
- Next.js, React
- Runtime
- Node.js
- Hosting
- Vercel, AWS, VPS
Not for CMS sites
We don't look after WordPress, Shopify, Webflow, Wix or other CMS and site-builder platforms.
A custom Next.js front end that pulls content from a headless CMS is in scope. We look after the app, not the CMS platform.
Not sure which you have? Ask on the call. It takes a minute to check.
05Pricing
One plan. Priced per application.
No tiers to compare. Every application gets the full service. The price depends on how much there is to look after.
The plan
Managed operations
From [$X] per application / month
- Monitoring and alerting
- Dependency and security patching, checked in staging
- Deploy pipeline maintenance
- Database and asset backups, with tested restores
- Incident response within an agreed window
- Monthly report and a named contact
What sets your price
- Traffic
- More traffic means more to monitor, and more at stake when something fails.
- Environments
- Production, staging, preview. Each environment is one more thing we maintain.
- Response window
- How quickly you need us to respond, and whether that includes nights and weekends.
You get a fixed monthly price in writing before you commit.
Building new features isn't included. The plan covers keeping what you have running.
06FAQ
Questions before you book
Anything else, ask on the call or email us.
What access do you need?
Four things: your code repository, your hosting account, your DNS, and your database. We ask for the lowest level of access that lets us do the work.
Where the platform allows it, we use named accounts, not shared passwords. You can see who changed what, and remove our access at any time.
What happens if something breaks at 3am?
Monitoring alerts us, not your inbox. What happens next depends on the response window in your agreement.
If it includes out-of-hours cover, we start work within that window. If it covers business hours, we start at the beginning of the next business day. You choose which before you sign.
Either way, you get a written summary afterwards: what failed, what we did, and what we're changing so it doesn't happen again.
Who owns the code and infrastructure?
You do. The repository, hosting accounts, domains and data stay in your name, in accounts you control. We work inside them.
If any of it is still in your old agency's accounts, we'll help you move it into yours during onboarding.
What response times do you commit to?
The ones written into your agreement. We set your response window with you, based on how critical the app is to your business. The price reflects it.
We don't publish one number here. An online shop and an internal dashboard need different cover. Your monthly report lists each incident with when it was detected and when we responded, so you can check.
Will you work alongside our existing developer?
Yes. If a developer or agency still builds features for you, they keep doing that. We look after the app in production.
We agree up front who deploys what. Our patches go through the same staging check as their changes.
How do I cancel?
Email us with [NOTICE PERIOD] notice. Before we step back, you get a handover note: what's running, where the backups are, which alerts are set up, and which credentials to rotate.
Everything is already in your accounts, so there's nothing to migrate. We then remove our access and confirm it in writing.
07Next step
Tell us about your app. We'll tell you what it needs.
Twenty minutes. We'll ask how it's built and hosted, tell you whether we're a fit, and give you a rough idea of cost.