How Spark works

Spark turns a business you can describe into apps your customers pay for. You explain what you want in plain language. An agent builds the apps — a chat app, an online store, a marketing site. You publish them at your project URL, and customers pay you directly through your connected Stripe account. Spark hosts and runs all of it.

The loop

Everything on Spark happens through one loop, whether you’re building your first page or fixing a typo three months in:

You ask. Tell the agent what you want — a new page, a warmer tone, a bug you spotted — in the chat that opens from the app’s Edit button.
The agent works. It makes the change and tells you what it did. The Edit button pulses while it’s busy.
The preview updates. Every app has a private preview that only you (and anyone you send the link to) can see. The agent’s work lands there first. Your live app is untouched.
You publish. The Publish button in the app’s header takes exactly what you previewed live. A dot on that button — and an “Unpublished changes” note on the app’s row in the sidebar — means new work is waiting for your decision.

Each publish is recorded as a version. History, the clock icon in the app’s header, lists every version, and Restore brings an earlier one back instantly. Preview and publish covers versions, History, and Restore in detail.

What a project contains

A project is one business. Its sidebar shows three kinds of things:

Public apps — what your customers see. The chat app is the default; you can add an online store, a marketing site, or anything else in the catalog. Each app has its own preview, its own Publish button, and its own agent.
Internal tools — pages only you see, inside Spark: Users, Analytics, Marketing, plus any custom tool you ask the agent to build for running your business.
Project settings — Spark-managed configuration: your project’s name, the business profile and brand, and your domain. You change these on settings pages rather than through the agent.

Payments sits pinned at the foot of the sidebar, above Project settings. That page is about money your customers pay you — see get paid. What you pay Spark lives somewhere else entirely, under Account settings › Billing & usage — see plans and credits.

Who’s who

You run the business. You describe what to build, review the preview, and decide when to publish. The Stripe account the money lands in is yours.
Your customers use your public apps at your project URL (it looks like yourname.spark.site until you connect a custom domain). They sign in by entering the code we send to their email (customer accounts), and they never see the Spark workspace.
The agent does the technical work. Each app and internal tool has its own agent chat that knows that app’s content and history.

What you never have to do

Spark runs the machinery a software business normally needs:

Code. You work in plain language; the agent handles the rest.
Hosting. Spark builds and serves every app, preview and live.
Sign-in. Customer accounts with email-code sign-in are built in.
Email. Your apps send email through Spark.
Payments. Connect Stripe once, and checkout, subscriptions, and one-time purchases work from there.

For the things Spark deliberately leaves out, see what Spark doesn’t do.

Two ideas, end to end

A parenting advice app. A parenting expert describes a research-backed assistant for parents. The agent builds a chat app; the expert uploads their articles and newsletters to its knowledge library and sets ground rules, like pointing anyone describing a medical emergency to professional help. They preview a few conversations, tighten the tone, connect Stripe, set a subscription, and publish. From then on, internal tools show what parents ask most and what the app earns.

An interview prep app. A builder describes a mock-interview coach for consulting and trading roles, then adds question banks, scoring rubrics, and examples of strong answers. They preview a full mock session, price it two ways — pay per interview, or subscribe for ongoing practice — and publish. After launch, analytics show which roles customers prepare for and where they struggle, and the builder adjusts materials and pricing from there.