Choosing a White Label AI App Builder Provider
Four kinds of seller answer to the same search: a monthly reseller plan, a script vendor, a custom agency and a platform you buy once. They separate on a few plain questions. Who keeps the source, whose LLM accounts pay for each prompt, who licenses the in-browser runtime, and what is left on the day you stop paying.
Request a Live Demo →See PricingReseller Plan vs Script Vendor vs Custom Agency vs Miracuves
One label, four business arrangements. Brochures blur them together; the contract, the hosting and the license terms do not.
| What you are comparing | Rented reseller plan | Script vendor or open-source fork | Custom agency or freelancer | Miracuves |
|---|---|---|---|---|
| Typical price | A monthly fee, often charged per seat | Low up front, then the missing layers are yours to build | $25,000 to $60,000 at an agency, $8,000 to $18,000 freelance | $3,699, one time |
| Time until users can build | Days, on the vendor's servers | Unclear, largely do-it-yourself | 3 to 9 months at an agency; freelance timelines vary | 6 days, on your servers |
| Who holds the source | The vendor | Frequently encrypted or restricted | Usually you, once the contract says so | You, the complete codebase |
| Accounts, plans and metering | Set by the vendor's own billing | Often a prompt box and little else | A separate workstream, priced separately | Free, Pro and Enterprise tiers with per-model credits and a ledger |
| Model choice | Whatever the vendor has enabled | Typically one provider | Scoped, often one to begin with | 22 providers behind one picker, plus the OpenRouter catalog |
| Where generated code runs | Often a remote sandbox per session | Rarely addressed | Often a server sandbox you then operate | In each user's browser tab |
| Runtime and model licenses | Often folded into the monthly fee | Seldom mentioned | Depends on the stack chosen | Yours: your LLM accounts and a StackBlitz license for WebContainers |
| The day you stop paying | The workspace, and usually its users, stay with the vendor | The script keeps running, updates may not | The retainer ends and the code stays | Nothing changes, because no recurring fee is owed to us |
A reseller plan is a fair way to test demand before you run any servers, and a custom build is the right call when your edge is something no AI app builder does yet. Fully custom work is a separate service, our generative AI development team, and we will say so if that is the better fit. This page is about the middle route: a finished platform you buy and own.
What You Arrange Before Day One
Four items sit with the operator under any provider, ours included. Starting them early is what keeps the six days at six.
Open your LLM provider accounts
Generation runs on provider accounts you open and pay for, under each provider's own terms. Miracuves has no model of its own, so pick which of the 22 you will offer at launch and have the keys ready.
License the in-browser runtime
Projects run inside StackBlitz WebContainers. Using them in production for a for-profit product needs a commercial license from StackBlitz, which you obtain directly. StackBlitz sets that price, not us.
Choose hosting and grant access
Any cloud you prefer. Docker Compose files and Kubernetes manifests ship in the package, and 2 vCPU with 4 GB of memory is a comfortable starting point.
Pick a payment provider
The platform meters credits but takes no payments itself. Stripe or a similar gateway is wired in during deployment, so the account should exist before that step comes round.
Questions Worth Asking Any Provider
Put the same nine questions to every bidder, in the same order, and compare the wording of the replies. Vague answers are an answer too.
Most of these can be checked on the demo rather than taken on trust. Four logins, one per tier plus the operator console, show plans, credits, keys and flags working.
The Six-Step Delivery Process
The six days are our side of the work. Two of the steps are about money rather than code, and on a metered product they deserve the most care.
A scope call, not a discovery phase
Which providers you will offer, how your plans are shaped and what you plan to charge per credit, checked against what ships. You leave with a fixed price and a written list of anything that would change it.
Your brand, then your servers
Product name, logo, colors, theme and domain applied across the workspace and desktop builds, then deployment to your cloud. Execution happens in the browser, so the server footprint stays modest.
Hardening against your domains
CSP and HSTS headers and CORS allow-listing set for your real hostnames, demo accounts switched off and a strong admin password in place. Encryption at rest, two-factor sign-in and audit logging are documented steps we scope with you.
Keys and the model catalog
Your provider keys added on the server, the model list populated, and input and output credit rates set per model on every plan against what your providers actually bill you.
Plans, credits and the gateway
Free, Pro and Enterprise priced with their allowances and model access, the free tier capped on purpose, and your payment provider connected with webhook signature checks.
Handover, then support
Source, schema, migrations, documentation and credentials, with a walkthrough of the console and the credit ledger. After that come 60 days of platform guidance, 6 months of priority bug fixes and 1 year of updates.
Red Flags That Mean Walk Away
Use this list on us as well. With a metered AI product, most of the expensive surprises are commercial, not technical.
- A reseller seat sold as ownershipIf the workspace lives on the vendor's servers and ends with the subscription, you are renting it, whatever the brochure calls it.
- Runtime licensing nobody raisesAn in-browser runtime has license terms of its own. A provider who never mentions them is leaving you to discover them after launch.
- One credit price for every modelWhen a cheap open model and a frontier model cost the same in credits, one quietly subsidizes the other until the provider bill lands.
- Usage estimated, not measuredCredits should come off real input and output token counts. The gap between a projection and the bill is where your margin goes.
- No ledger behind the balanceDisputes are routine on metered products. Without a recorded reason for every grant and spend, each one tends to end in a refund.
- Locked to a single providerIf routing speaks to one vendor, that vendor's price change becomes yours. Several providers behind one interface is a commercial safeguard.
- Source "after final payment", with conditionsAsk whether the metering and the provider layer are included, whether anything is obfuscated, and whether a license server phones home.
- Hardening claimed as a shipped defaultCSP, HSTS and encryption at rest should be named as deployment steps set for your domains, not promised as already on and not skipped.
What a White Label AI App Builder Has to Get Right
Six things separate a business you can run from a chat window with a code pane attached. A provider who has not solved them has not operated one.
Custody, Licenses and Limits
A buyer's security review asks where the code goes and who can see it. A buyer's lawyer asks whose licenses cover what. Both answers belong in front of you before the purchase.
Self-Hosted, Browser-Executed
The platform runs on servers you control, and generated projects execute inside each user's browser rather than in a shared remote sandbox. No third-party SaaS that you do not choose sits between your users and their work.
Keys Held by the Operator
Provider keys are kept by you and added to requests on the server by the Express auth proxy, never returned to the browser. Rotating or revoking a key is one console action, shown as a masked preview.
The Licenses Are Yours
We supply software, not rights to a model or a runtime. LLM usage runs on accounts you open under each provider's terms, the commercial StackBlitz license for WebContainers is obtained by you, and payments run through your own gateway.
Stated Limits
No mobile app ships, only the browser product and Electron desktop builds. CSP, HSTS, two-factor sign-in and encryption at rest are configuration before launch. The VAPT report maps control objectives; no certificate is held.
Each capability carries one of three labels, Included, Supported or Configuration required, so what you hold after purchase matches what you were shown before it.
A Real Deployment
An enterprise platform team that wanted AI-assisted coding on its own terms, live on this platform. The client's identity is withheld under NDA.
Challenges
- Offering AI coding help to engineers while keeping proprietary code away from outside SaaS tools
- Keeping API credentials central so no team ever held a raw provider key
- Turning unpredictable AI bills into a per-team credit budget
Goal
- Launch an internal AI builder without writing login, metering and controls from scratch
- Let the platform team decide which models run, what they cost and who can use them
- Trace every credit spent back to a team and a model
Solution by Miracuves
- Projects executed in the browser, with no sandbox servers
- Plan tiers, credit budgets & centrally held provider keys
- Models, prices and feature flags set by the operator
- One workspace to generate, edit, preview, ship & export
- An Express auth proxy in front of a Cloudflare workerd runtime
"The admin panel is what got this past our security review. Central keys, per-plan models, and nothing leaving our network."
Frequently Asked Questions
Is a platform provider the same as a custom AI development agency?
What do I own after handover?
Who licenses the in-browser runtime and the models?
Are there recurring costs after launch?
Does any of our code reach Miracuves?
What is not included in the base platform?
Explore the White Label AI App Builder
Bring the checklist to every bidder
Open the demo, sign in as the operator and work through the nine questions above, starting with who licenses the runtime. We would rather answer them before you sign than after.
Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Bolt.new, StackBlitz or any other AI app builder or code generation service.
“White label AI app builder” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
We supply software, not rights to any AI model or runtime. Opening and paying for LLM provider accounts and staying within their terms, obtaining the commercial license StackBlitz requires for production use of WebContainers, your terms of service for the code your users generate, privacy notices and payment processing are your responsibility. We do not advise on any of it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party AI app builder website or application. All third-party names and marks belong to their respective owners.
