Turnkey Stores as a Service: Agency Economics on a NitroCart License
Turnkey Stores as a Service
Agencies that already sell clients websites and ad management eventually hit the same wall: how do you launch online stores for clients without buying a separate license per project or parking them on a shared builder with someone else's brand in the footer. NitroCart Enterprise gives you 15 concurrent storefronts on one key, which is what makes white label online stores for agencies workable — each client gets their own VDS, their own domain, their own admin panel, and you sell a result, not an engine. Full platform details are on the NitroCart homepage.
What this is and who needs it
Launching client stores as a service means an agency buys one engine license and runs several independent installations for different clients on it, earning money on the launch fee and monthly upkeep rather than reselling software. It fits agencies already running paid ads or social management for clients who want to add "store launch" to their service list without hiring a backend developer per project, and web studios tired of explaining to clients why their site looks identical to a hundred others on the same builder.
Selection criteria
- License economics. What one purchase costs and how many installs it covers determines the margin on every client after the first.
- Client isolation. A separate server, domain and admin panel per installation, versus a shared database that risks bleeding data between clients as you scale.
- Layout uniqueness. Identical HTML/CSS across every client is a risk for their SEO and ad accounts, especially when two of your clients compete in the same niche.
- Launch speed. How many billable hours it takes to stand up one client's copy directly sets the cost of delivering the service.
- Update model. Patching the core by hand — hunting for files, risking a conflict with customization — versus a signed patch, which you still apply to each server individually, but without a rebuild or hand-editing files.
- Storefront flexibility. One catalog template for every client, or an engine that covers different niches — catalog, single-product page, multi-landing, ticketing.
- Client transparency. Does the client get real control of their own server and domain, or does everything depend on the agency never revoking access.
- Access handoff flexibility. Can the agency decide exactly what to hand the client — limited admin access or the whole server — or does the model force one fixed option.
Comparison table
| Model | What you sell | Client owns the server | Layout uniqueness across clients | Economics at 9+ clients |
|---|---|---|---|---|
| Agency reselling a SaaS builder | A hosted storefront on monthly rent | No, platform infrastructure | Shared builder engine | Platform's cut eats into every client sale |
| Agency on a custom build / freelance stack | Bespoke development per client | Usually yes | Yes, but every build starts from zero | High per-project labor cost, margin tied to developer rate |
| Agency on NitroCart Enterprise | Launch + ongoing upkeep on one engine | Yes, own VDS per client | Yes, CSS/JS/id regenerated per install | $3,590/year license paid off by three clients over a year, 12 more installs with no extra engine fee |
| Client buys a SaaS store directly from a vendor | Nothing — client self-serves | No | No | Agency isn't part of the economics at all |
How this works in NitroCart
Every client installation is deployed through the Telegram Mini App, typically 15-30 minutes per install, including a free Let's Encrypt SSL certificate on the client's own domain. The Enterprise license covers up to 15 IPs — up to 15 independent engine installs running at once, each with its own admin panel in English or Russian, with no single console sitting above all client installs. The storefront switches between 4 formats with one field in the admin: a standard catalog, a single-product page, a multi-offer landing, and event ticketing. Under the hood, each installation gets its own regenerated map of CSS classes, ids, variables, JS names and paths — two client copies never match in markup, even off the same theme, which matters when two of your clients operate in the same niche and can't look like clones of each other. Updates are signed patches with no image rebuild, applied per installation — there's no single button that patches all ten servers at once. A built-in SEO module handles meta tags, sitemap, a blog with categories and tags, and JSON-LD on every install independently. Clients get order notifications via Telegram, and any payment provider connects through a configurable API redirect matching whatever system that particular client uses. Extra functionality installs as ZIP plugins from the admin with no SSH, and survives image updates.
Themes and design: what's available now and what's planned
Out of the box the engine ships 5 built-in themes across 4 storefront formats: two in Catalog (Mini and Modave), and one base theme each in Landing one, Landing multi and Tickets — but with 10-15 ready-made color schemes per theme. For an agency that means two clients in the same niche can already look meaningfully different today without a single line of custom code: landing formats let you change section color and background, block order, the hero, dividers, button style and rounding, and fonts.
NitroCart's own developers build the landing-format themes, and the theme library grows regularly alongside engine updates — it's not a one-time delivery but part of ongoing development, and those updates are already included in the license at no extra cost. Separately in development: an in-engine theme constructor that will let you build your own theme and share it with other NitroCart users, and for the Catalog format (multi-page stores), integrating ready-made third-party HTML templates is planned — that will widen the range of available storefronts without commissioning custom markup. Both of these are still in development and not part of the current build — plan today's launches around the 5 themes and their color schemes already available.
The math on 9 clients: where the year's margin ends up
A year's Enterprise key is $3,590 and covers 15 storefronts. A client launch runs from $300, upkeep from $100/mo, so one client brings in at least $1,500 over a year and three clients cover the license — the remaining twelve slots then run with zero additional fee to the engine vendor. With one client at the start, Start is enough; with two to five clients, Pro.
Revenue by how many clients you're running
The table shows the steady state — every client in the scenario already has a full paid year of upkeep. In year one, while clients sign on gradually rather than all at once, revenue is lower — see the ramp-up case below.
| Scenario | Clients | Upkeep / client per month | Launch, one-time (N × $300) | Upkeep over a year | Total revenue for the year | Minus the $3,590 license | Net margin for the year |
|---|---|---|---|---|---|---|---|
| Minimal | 3 | $100 | $900 | $3,600 | $4,500 | $3,590 | $910 |
| Baseline | 9 | $100 | $2,700 | $10,800 | $13,500 | $3,590 | $9,910 |
| Expanded | 9 | $150 | $2,700 | $16,200 | $18,900 | $3,590 | $15,310 |
| Maximum | 15 | $150 | $4,500 | $27,000 | $31,500 | $3,590 | $27,910 |
Direct costs beyond this are the VDS for each client (usually $5-20/mo per server with most hosts) and the agency's own support time; there's no per-client licensing fee to the engine vendor beyond the annual key in this model.
Year one: clients don't all sign on at once
Take a conservative case: the agency signs 9 clients gradually over the first six months, each on baseline $100/mo upkeep. By year end, total upkeep revenue is nine clients times however many months each has actually been paying (someone signed in January, someone in June), plus a one-time $300 for each of the nine launches. Even without a single upsell to a pricier upkeep tier, the one-time launch fees alone (9 × $300 = $2,700) nearly triple the cost of the annual license, and every month of upkeep after that is pure margin that compounds as each client stays on.
A more realistic case for an agency that knows how to sell: some clients take expanded upkeep — analytics, seasonal campaigns, custom tweaks — at $200-300/mo instead of the $100 baseline. At nine clients averaging $150/mo in upkeep, monthly revenue on a single license is $1,350, against direct costs of nine VDS instances and the agency's own support time — there's no per-client licensing fee to the engine vendor beyond the initial annual key.
Each client also sits on their own VDS and domain, which means separate blast radius: if one client leaves or stops paying, the other eight installations aren't touched technically — the agency just frees up one license slot for the next client. A related breakdown of running several brands on one engine is in multi-brand stores, one engine, and the license math across VPS instances is covered in one license, up to 15 VPS. For the broader agency white-label model itself, see white label online store — that article covers the model in general, this one covers specifically the 9-10 client economics on Enterprise. On launch turnaround per client, see deploy a store in 15-30 minutes.
When NitroCart is not a fit
Turnkey stores as a service on NitroCart doesn't fit if a client needs a marketplace with many independent sellers inside one storefront, ready-made dropshipping automation with supplier product import and margin calculators, or if the agency has literally no one able to handle basic VDS administration, even at the level of "SSH in when needed." The Enterprise license is also capped at 15 IPs — if an agency's first-year pipeline already exceeds 15 simultaneous clients, some of them will need a separate key. For the full honest breakdown of limitations, see when NitroCart is not a fit.
FAQ
Does the client get direct access to their own server and domain? Yes, each installation is a separate VDS and domain owned by the client — the agency doesn't run a single console over every client install.
What happens if a client wants to switch to another agency later? That's up to the agency, not the engine: how much access you open up to the client or their new contractor is up to the situation. You can hand over just admin-panel access scoped to specific sections — the engine has standard roles and permissions (Authentication → Users/Groups) — or hand over the whole server: SSH access to the VDS and domain management. Either way, the license key stays with the agency — it's issued to your account and isn't transferred automatically along with server or admin access.
Does the agency need to hire a backend developer for every client? No, not for the launch itself — installing via the Telegram Mini App doesn't require writing code; customization beyond the built-in themes needs basic HTML/CSS/JS skills.
What's typically included in $100+/mo upkeep? That's up to the agency to define — anything from basic monitoring and content updates to extended analytics and custom work; the engine doesn't dictate the upkeep package.
What happens at a 16th client? The Enterprise license is capped at 15 IPs — a 16th install requires either freeing a slot or a second key.
Pricing: Start — from $99/mo, 1 install. Pro — $539/quarter, up to 5 installs. Enterprise — $3,590/year, up to 15 storefronts. Details on the NitroCart pricing page.
How much it costs
NitroCart is a license, not a subscription with a cut of your sales. Three plans, billed monthly, quarterly (up to −10%) or yearly (−25%):
- Start — from $99/mo ($890/year, ≈$74/mo), 1 store.
- Pro — from $199/mo ($1,790/year, ≈$149/mo), up to 5 concurrent stores.
- Enterprise — from $399/mo ($3,590/year, ≈$299/mo), up to 15 concurrent stores.