Pricing

Studio is an app. Cloud is a plan.

TameChaos Studio is software you install — local-first, offline, no account required. TameChaos Cloud is a plan per account, scaled on the seats in it and the storage its fleet uses, with edges free to connect. Integrators pay per seat. We are pre-release, so nothing here carries a price yet.
Nothing on this page has a price yet
Studio has no announced price, Cloud plans are priced at GA, and there is no integrator seat price. The structure is real — it is how each product is bought — but every figure is deliberately blank rather than guessed at, and no quota or limit is stated. Request beta access free in the meantime.
How it's bought

Three ways in

Studio and Field are apps you install. Cloud is a plan on the account that owns your fleet, and an edge server connects to that fleet at no charge. Integrator access is a seat. They are priced separately because they are bought separately.
Studio is an app
You install it, and it works on its own — local-first authoring, fully offline, no TameChaos account and no Cloud subscription needed. It is a store download, not a plan.
No price announced
Cloud is a plan per account
An account is the tenancy and billing boundary and owns one fleet. Plans are expected to scale on the seats in the account and the storage its fleet uses — and edges are free to connect.
Free while in beta
Integrators pay per seat
Systems integrators get a different kind of account — no fleet, no telemetry, billed per seat, admitted by application and our review. There is no self-serve signup.
On the roadmap
Studio

Install it, and it works on its own

Studio's acquisition path is a store download, not a fleet plan. Here is the channel for each platform, and what a Cloud plan does and doesn't add on top.
Apple platforms — the App Store
Every TameChaos Apple application is distributed through the App Store, and the macOS build through the Mac App Store. There is no direct download and no notarized installer. TestFlight is pre-release testing of that same App Store build, not a second way to get it.
Windows — its own channel, not announced
The Windows build is a WPF application on .NET 10, in the same first release as the Apple build. Its distribution channel has not been announced, and we would rather say so than put a store badge next to a guess.
No account, no network, no plan
Studio authors a project on the device and needs nothing from us to do it. Its working backup destinations today are your own disk, Files, and an iCloud Drive location you choose — the Cloud destination is one more optional one being built, and Studio never requires it to work at all.
What a Cloud plan adds to Studio
Two optional things, and both are plan dimensions rather than Studio products: encrypted project backup, which will count against your plan’s storage allowance; and the entitled procurement data below.

Studio is pre-release, and we will not put a placeholder number on it.

There is no price, no tier list, and no trial length to quote for Studio yet — when there is, it will be on the store listing and on this page. TameChaos Field, the Android platform surface of the same Studio core, is earlier still and has no store listing at all; it is early access by waitlist. Where Studio is has the honest staging and the one date we are willing to give.

Cloud plans

From a single edge to a full fleet

Three tiers on two axes — the seats in your account, and the storage your fleet uses. Edges are free to connect either way. Every figure here is a pre-GA blank pending a pricing decision.
Lab
Beta
For an individual and early experiments — one account, one fleet. Free while we are in beta.
Free
in beta
  • An individual account with its own fleet
  • Edges are free to connect — no per-edge charge
  • Run & measurement ingestion
  • Time-series query + cross-run comparison
  • A modest storage and retention allowance
No card required during the beta.
Request beta access
Fleet
Pre-GA
For a team whose fleet of edges learns from its own operation. Pricing lands at GA.
TBD
priced at GA
  • Several people in one account, sharing one fleet
  • Edges still free to connect — the meter is storage, not devices
  • A larger storage and retention allowance
  • Process-class template registry + identity
  • Fleet oversight + like-process aggregation
  • Model improvement and distribution (on the roadmap)
Final price is being decided ahead of GA.
Request beta access
Enterprise
For larger fleets with custom seat, storage, and support needs.
Let's talk
custom
  • Custom seats, storage, and retention
  • Per-fleet tenancy — no cross-tenant data or model sharing
  • Priority support
  • Help bringing your edges and processes onboard
We will scope allowances and pricing with you.
Contact us
Plan entitlements

Some things are a plan dimension, not a line on the bill

Component pricing data is gated by plan rather than metered, which makes it a feature-availability axis rather than a number. Which tier carries it is part of the packaging decision that hasn't landed.
Component pricing is an entitled field
Budgetary pricing and availability ride the catalog as plan-entitled fields, and are stripped for a surface without the entitlement. That surface still gets full specifications, taxonomy, datasheets, and alternates — it just gets no price.
Plan dimension — tier not decided
Budgetary, and stamped with its date
Planning numbers, never a quote. Every price carries the date it was priced, and past a staleness threshold it renders as stale rather than as a figure you might act on. There is no live distributor feed and no ordering rail anywhere in this.
In the first release
Detailed supplier offers are their own artifact
Vendor-identified offers — price breaks, availability, lead time, minimum order — are designed as a separate entitled feed, queried on demand and kept out of the vendor-neutral catalog. It is not a settled decision yet; until it is, Sourcing shows the budgetary projection and says so.
On the roadmap
Studio backup counts as storage, by size
When the Cloud backup destination opens, an encrypted project snapshot will count against your plan’s storage allowance and nothing more — it is not a separate tier or an add-on product. We hold ciphertext we have no way to decrypt, so there is no content in it for us to price by.
In the first release
Integrators

Per seat — and we take no cut of the work

Systems integrators are a different kind of account with a different bill. This is on the roadmap: the request-for-quote workflow is decided but is not open today.
On the roadmap — not open today
A different kind of account
An integrator account owns no fleet and no edges, and never sees a customer’s fleet, telemetry, runs, or templates. It exists to review a bill of materials it was granted and to bid on that.
Billed per seat
Integrator accounts are billed per seat, and a seat is what gets you into the request-for-quote workflow. There is no seat price to quote yet.
Vetted by us, not self-serve
You apply, a TameChaos operator reviews it, and an approval mints your invite. There is no open signup, no directory of customers, and no feed of opportunities to browse.
Access is one grant at a time
A customer shares one published version of one package with you — explicitly, revocably, and optionally with an expiry. Without a grant, nothing of that customer exists to you.
Broker-only, so neutrality is structural
We host the request for quote and are not a party to the deal: no commission, no listing fee, no escrow, no payment rail. The money moves off-platform. We never rank, score, or recommend a bid — and because we earn seats rather than a cut, that is how the business is built rather than a policy we ask you to trust.

A private request for quote, not an open market.

A request for quote is never openly listed and there is no directory of opportunities to browse. An integrator sees only what you granted it, bids are sealed to everyone but you, no integrator can see who else you invited, and nothing is ranked for you. You choose per request how much of the design travels with the line items — the bill of materials always does; the topology, control narrative, and the I/O, network and power summaries are yours to include or withhold.

Billing

How billing works

The short version while we are pre-GA — honest about what is decided and what is not.

Start in the beta

Request beta access free today, or talk to us about a larger fleet. Pricing will firm up as we move toward GA — this is the marketing front door; your account and your fleet live in the app.