PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Feature scope - proposed scope

White Label AI App Builder Features: Prompt, Preview, Deploy

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Feature Set by Role

The Builder

  • Someone with an idea and a browser. They write a description and get software they can run on the spot.
  • One plain-English brief becomes a full multi-file project: frontend, routes, config and manifests
  • A real Node.js environment boots inside their tab in three to five seconds
  • Saved files reach the preview in under half a second

Paying Teams on Pro and Enterprise

  • What a subscription buys, and how the platform counts what each account uses.
  • Four providers on Free, all twenty-two on Pro and Enterprise
  • Prompt enhancement, custom system prompts and MCP tools on paid plans
  • Operator keys added by the Express proxy, never sent to the browser

You, the Operator

  • A separate admin console where the business is configured live, with no developer and no redeploy.
  • Add, rotate or disable the keys for any of the 22 providers
  • Place any model on any plan with its own input and output rate
  • Cap tokens per request by plan and model

The Technology Behind the Features

The workspace is a server-rendered Remix 2.15 app on React (version confirmed in writing) with UnoCSS, beside an xterm.js terminal. Anything that touches the database goes through an Express 5.2 proxy that holds sessions, rate limits, credit metering and your provider keys; anything that touches the AI pipeline runs on a Cloudflare workerd runtime using the Vercel AI SDK, with a 45-second stream timeout and two retries. PostgreSQL holds six tables, reached only through parameterized queries with no ORM. StackBlitz WebContainers give each user a full Node.js environment in the browser, which is why previews cost your servers nothing. One licensing point to plan for: StackBlitz licenses WebContainers commercially, so production use in a for-profit product needs a license from StackBlitz, which you obtain directly. Generation itself runs through LLM provider accounts you open and pay for, under each provider's terms; Omnistu has no model of its own.

Identity, generation, execution and metering happen in a fixed order. The part most buyers do not expect is where the heavy work lands: in the user's browser rather than on your cloud bill.

An account with a balance from day one

  • Email, username and password are validated at the API boundary, the password is stored as a bcrypt hash, and a 256-bit session token is saved only as its SHA-256 hash. The free tier and a welcome credit balance are applied before the workbench even loads.

A template that already runs

  • The user starts blank or picks one of 30+ starters across eight categories, each with its own generation prompt. The chosen template fills the browser runtime with a complete project tree, so the first session opens on something that works.

The prompt reaches the model

  • Chat history, file state and model settings travel together. On qualifying plans the proxy adds your provider key on the server, and workerd calls the selected model, streaming text and action commands back.

The browser does the running

  • File writes, shell commands and package installs execute inside the WebContainer. The preview refreshes as files arrive, so the infrastructure you pay for does not grow with the amount of code your users run.

Out the door

  • The finished app goes to Vercel, Netlify, GitHub, GitLab or Cloudflare Pages, with the framework detected across ten options and the live URL shown in the workbench, or it downloads as a ZIP at any time.

Every Feature Earns Its Place

Below, each capability is paired with the reason an operator needs it, which is a more useful test than whether it appears on a checklist.

Boundaries we state in writing for your build

Deciding who should supply your AI app builder?

  • The questions to put to any vendor, including who licenses the in-browser runtime, plus our delivery steps and a real enterprise deployment, are on the Provider page.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com