Pricing

Private alpha now. Simple app-based pricing later.

There is no public price yet. We are testing a model based on active apps and measured usage, with internal viewers included.

Private alpha

Custom pilot agreement

Agreed before onboarding

One relationship, the complete small cloud:

UsageMeasured and capped by app

Compute, model calls, storage, and outbound traffic are visible separately. The pilot states which usage is included, billed, or capped.

Pricing principles

Inviting a teammate should not turn a useful internal app into a seat-cost debate.

Active apps, workers, agent runs, storage, and model usage are the things that create cost.

The built-in cloud products belong together instead of becoming seven vendor bills.

Teams can understand which small app uses what before deciding whether it is worth keeping.

Questions

Is the private alpha free?

Not necessarily. Each design partner uses a written pilot agreement that states any fees, included usage, caps, and support before onboarding.

Can we set spending limits?

That is the target. Usage is visible by app and operational-agent run, with pilot caps agreed before deployment.

Do teammates need paid seats?

Ordinary internal viewers are included during alpha, subject to the limits in the pilot agreement.

What happens after alpha?

The planned model is based on active apps and measured usage. Pilot partners will receive notice and export options before any pricing transition.

Can we export and delete our data?

The alpha target includes database and file export plus verified workspace deletion on request.

Can I self-serve today?

Not yet. We are onboarding a small set of design partners while the runtime contract is still changing.

Private alpha