FAQ
Questions buyers actually ask
Who hosts my database, is it me?+
Yes, and that is deliberate. Cloud accounts are opened in your company name in week one and billed to you. We work inside your accounts. See how we work to spec.
Can I just use Firebase?+
Often, yes, and on a first version we will usually tell you to. The honest version of when it stops being the right answer is in Firebase, Supabase, or your own.
What stops me getting a $70,000 bill?+
Hard instance and concurrency limits, per-key rate limiting, secret scanning, budget alerts at three thresholds, and a costed load test before launch. And the uncomfortable fact that platform spending caps are usually alerts, not brakes. See the bill that arrives when you are not looking.
Will I be locked in to you?+
No. Your accounts, your repository, your keys. Data access goes through one layer, so moving is a project of weeks rather than months. Replace us and you change one password. See how we work to spec and Firebase, Supabase, or your own.
Why does the invisible part cost as much as the app?+
Because it is where scale, cost and reliability are decided. Uptime, success rate under bad conditions, speed of the one operation that matters, and behaviour at 10x volume: those numbers are what you are actually buying.
How do I judge backend work if I cannot see it?+
Uptime, success rate under bad conditions, speed of the one operation that matters, and behaviour at 10x volume. We hand you all four in writing.
Can you connect to the system we already use?+
Almost certainly, including old ones. What matters is what happens when that system is down. We define that for every integration. See connecting to everything else you already run.
What happens if a provider changes their API?+
Versions are pinned and monitored, so it becomes a ticket rather than an outage.
Do you do REST or GraphQL?+
Both. We pick per project and explain the choice in plain words. See standards for the API itself.
Are my backups actually working?+
They are on our projects, because we restore one as a test before handover. An untested backup is a rumour.
What does it cost to run each month?+
You get the figure at today’s volume and at 10x volume, before launch. It is step 7 of how we work.
Can our own developer take it over?+
Yes. Documented API, runbook, and accounts already in your name. Handover is a normal ending, not a penalty.
Do you build the admin panel too?+
That is a separate service, Web Apps & Admin Panels, usually scoped together with this.
Do you handle subscription billing?+
The payment integration, yes. The billing logic, proration, dunning, upgrades mid-cycle, is its own hard problem and lives on SaaS Development.
