Guides · Owning your product
Guides · Owning your product
Self-hosting wins on the monthly bill and loses on your time; a managed platform is the reverse. A basic server runs from about $4 a month, while a small managed stack like Vercel Pro plus Supabase Pro sits near $45 a month, so on paper self-hosting looks cheaper. The number that flips it is maintenance: running your own stack costs an engineering hour every week and, at industry rates, 15% to 30% of the build price a year. This guide puts cost, control, risk and maintenance side by side, with real numbers, and says plainly who should not self-host.
This is the comparison chapter of our guide on what full ownership of a self-hosted SaaS actually takes. That hub covers the work owning your infrastructure demands; this page is the decision itself, managed or self-hosted, with the numbers next to each other.
Choose managed when a small operational surface and shipping fast matter more than control. Choose self-hosted when data location, independence from a vendor, or full control of the stack is worth an hour of upkeep every week.
A managed platform runs the machine and hands you a dashboard; self-hosting means the machine is yours to run. Cloud providers put that line in writing. In AWS's shared-responsibility model, the provider secures the infrastructure while you handle the operating system, the application and the configuration. Self-host and everything above the bare hardware is yours.
The managed fee is predictable and climbs with scale; the self-hosted floor is low and your time is the variable cost. Here is the same small product priced both ways.
| What you pay | Managed platform | Self-hosted |
|---|---|---|
| Monthly infrastructure | ~$45 (Vercel Pro $20 + Supabase Pro $25) | From $4 a VPS |
| Setup | Minutes | Days, folded into a ₪3K–18K+ build |
| Upkeep per year | Included in the fee | ~1 hour a week, plus 15–30% of build cost |
| Cost as you grow | Climbs with seats and usage | Flat server, your hours are the cost |
| Who answers at 3am | Their on-call | You |
Read the table by the bottom two rows, not the top one. The monthly bill favours self-hosting by roughly ten to one, and it is the least important line. The upkeep row is where the money actually goes.
Self-hosting gives you full control of the stack and removes vendor lock-in. In exchange you inherit every failure the platform used to absorb, including the expensive ones.
One client ran an automated app with no cap on concurrent jobs, no spending limit and no real stop switch. One unsupervised day produced an AI bill of over $1,000. A managed platform might have throttled it; self-hosted, that guardrail is yours to build. Self-hosting also moves the whole security burden onto you, and the permission holes and exposed secrets we keep finding are in security holes we keep finding in AI-generated apps. A managed stack quietly closes some of them; on your own, nobody does that for free.
Maintenance is where self-hosting gets expensive. Backups, monitoring, security patching and deploys add up to an hour of attention every week and, at industry rates, 15% to 30% of the build cost a year.
On a ₪35K–60K platform that is ₪5K–18K a year, every year, before a single new feature. A managed platform folds that work into its fee, which is a large part of what the fee buys. Why we price the build itself by scope, and what each tier includes, is in what it costs to rebuild a no-code app for production, and the tier ranges are on the pricing page.
The server is the cheap part of self-hosting. The expensive part is the hour, every week, that keeps backups, patches and monitoring honest. Budget that hour, or it finds you the week something breaks.
Do not self-host if any of these is true. Each one means the operational weight will land on someone who cannot carry it yet.
If all five are true, managed is not a compromise, it is the correct decision. If even one points the other way, regulated data, a client's own hardware, or a vendor you cannot depend on, self-hosting starts to earn its cost.
We pick the side with one question: if this goes down at 3am, who answers, and does the data have to stay in one place? The answers usually point one way before the pricing does.
A legal-document AI we built self-hosts by requirement, not preference. It runs on the client's own machine because privileged legal material cannot leave the building, so the whole stack lives where the data does. Most of our 15 shipped apps run managed or hybrid instead, because the data allowed it. The common middle path is managed hosting with a self-hosted AI engine over private data, which keeps the operational surface small while the sensitive part stays in your hands. If you want that decision made in writing for your product, get a written quote that names what stays managed and what you self-host. It is valid for 14 days. More of the questions founders ask before choosing are on the FAQ page.
Founder and main developer at Zyntari. Building apps and AI solutions since 2024; before that, 12 years in sales and client-portfolio management and co-founder of two companies. More about the team · LinkedIn