Simple, transparent pricing
One fixed-price project to get you safely live. A monthly plan to keep you there. The audit that decides which of those you actually need is free.
How the money works
- The first call and the consultation cost nothing
- The audit comes before any quote, always
- One fixed price, agreed in writing, before work starts
- No hourly billing, so no invoice you did not expect
- Retainers are month to month with no minimum term
One project to get live. Two ways to stay there.
Every engagement starts the same way, with a free consultation and a scoped audit, and the plan you pick after that is the one the findings justify.
One-Time Project
$2,000+
Fixed scope · 2–5 weeks
Perfect for getting your app production-ready.
- Production Audit
- Fix & Optimization
- Deployment
- 30 Days Support
Best for: You have an app that works in a demo and needs to be safe in front of real users.
- Most Popular
Growth Plan
$499/month
Month to month · cancel any time
Ongoing support and continuous improvement.
- Everything in One-Time
- Monitoring & Updates
- Performance Tuning
- Priority Support
Best for: You are live, you have paying users, and nobody on the team wants to own production.
Scale Plan
$999/month
Month to month · priority
For apps with high traffic and complex needs.
- Everything in Growth
- Advanced Scaling
- Security Monitoring
- Custom Solutions
Best for: Traffic is real, downtime is expensive, and the architecture needs to keep moving.
Cloud Independence migrations are quoted separately, scoped to your stack and data volume. They are usually paid for by the hosting bill they remove.
What’s in every engagement
These are not upsells. They are how we work, on the smallest project and the largest retainer alike.
A named engineer
One person owns your account and knows your codebase. You are not routed to whoever happens to be free that week.
Fixed scope, fixed price
The number is agreed in writing before work starts. No hourly billing, no change order you did not approve first.
A written update every week
Shipped, in progress, blocked, and what we need from you. Short, on Friday, including the parts that went badly.
Work you can read
Everything lands on branches and goes through pull requests in your repository, at whatever review depth you want.
Your accounts, your keys
Infrastructure is created in accounts you own and credentials live in your secret store.
Before and after numbers
Latency, error rate, bundle size, and monthly spend, measured the same way at the start and at the end.
Runbooks in your repo
How to deploy, roll back, rotate a secret, and restore a backup.
No lock-in
Retainers are month to month, and the handover is deliberately good enough that leaving is a real option.
What each plan covers
The one-time project makes the app safe to launch. The monthly plans keep it that way.
| Compare | One-Time Project$2,000+ | Growth Plan$499/month | Scale Plan$999/month |
|---|---|---|---|
| Production readiness audit | Once, up front | Up front, re-run quarterly | Up front, re-run monthly |
| Security fixes and hardening | Included | Included | Included |
| Database, indexing, and query work | Included | Included | Included |
| CI/CD pipeline and environments | Included | Included | Included |
| Production deployment | Included | Included | Included |
| Post-launch support | 30 days | Ongoing | Ongoing |
| Uptime and error monitoring | Set up and handed over | Watched by us, 24/7 | Watched by us, 24/7 |
| Backups and restore drills | Configured and tested once | Verified quarterly | Verified monthly |
| Dependency and security patching | Not included | Monthly cadence | Weekly cadence |
| Performance and cost review | Before/after report | Monthly | Monthly, with capacity planning |
| Incident response target | Best effort | Next business day | Same business day, priority |
| Support channel | Shared Slack or Discord | Shared channel, priority queue | |
| Scaling and custom engineering | Not included | Quoted per project | Monthly allowance included |
| Commitment | One fixed-price project | Month to month | Month to month |
| Get Started | Get Started | Get Started |
Scroll the table sideways to see every plan.
How we turn “$2,000+” into a real number
A price range on a website is only honest if the process behind it is. Here is exactly how the range becomes one number, and what moves it.
- Step 1
A free call
Thirty minutes with an engineer. We work out whether the problem is worth solving now and what the audit needs to cover.
- Step 2
The audit
Three to five business days of reading, testing, and load work.
- Step 3
A fixed quote
The findings become a written scope with one price and one date range.
- Step 4
Work starts
Only after you accept the quote. The number on the quote is the number on the invoice, whether the work takes us two weeks or four.
What pushes the number up
- Payments, subscriptions, or anything else that moves money
- Personal or regulated data: health, financial, or anything under GDPR
- A data model that has to change while the app stays online
- Multi-tenant access rules that were never really modelled
- Integrations with third-party systems we cannot test against safely
- Migrating off the builder at the same time as the hardening
What keeps the number down
- A repo we can read, with a real git history rather than one enormous commit
- One environment to fix instead of five drifted variations of the same app
- Findings you decide to defer. You always choose what is in scope
- Your team taking the low-severity items while we take the critical ones
- A staging environment we can break without a customer noticing
- Deciding early that the builder stays for now and migration waits
The number on the quote is the number on the invoice. If the work turns out to be harder than we estimated, that is ours to absorb. We do not bill by the hour, so there is nothing to inflate and no reason for anyone to drag it out.
Start with a call that costs nothing
Thirty minutes with the engineer who would read your code. If the honest answer is that you do not need us yet, that is the answer you will get.
No obligation · Reply within one business day
- 1
Bring whatever you have
A live URL, a repo, or a screen recording of the app inside your builder.
- 2
We ask the questions that change the price
Who uses it, what data it holds, what happens on the worst day, and what you are planning to launch next.
- 3
You leave with a plan either way
The two or three things we would fix first and roughly what that takes.
Pricing questions, answered plainly
It is the floor for a scoped project, not an opening bid.
Because hourly billing pays us for problems being hard and pays you for nothing.
You see the full list, ranked, before you spend anything. That is the entire point of auditing first.
No, and they should not be. You pay AWS, Vercel, Supabase, Fly, or whoever else directly, from accounts you own, so you keep control and see the real bill.
No. Growth and Scale are month to month and you can cancel any time.
Yes to all three. Plenty of clients take the one-time project, run it themselves, and come back months later when traffic makes monitoring worth paying for.
Not sure which plan you need?
Neither are we, until we have read the code. The call and the consultation are free.