IN SHORT
- One system = one database + one web address + one studio conversation.
- Starting one asks four things: a starting point, a name, the country it is for, and the language it speaks.
- The region a system runs in is fixed when it is created and cannot be moved afterwards.
- Credits are shared across every system on the account; the plan does not cap how many you have.
What counts as one system
A system is a self-contained piece of software: its own database, its own web address, its own screens and its own studio conversation. Two systems on the same account do not share data. If the bookings system needs to know about the stock system, that is a link you have to ask for, not something that happens because they sit under one login.
Most businesses start with one and stay there for a long time. A second system is worth starting when the two things genuinely have different users and different data — a customer-facing booking site and an internal accounts tool, say — rather than when one system has grown a second screen.
The four questions when you start one
Close is close enough on the trade. The starting point is a head start, not a straitjacket: everything in it is rewritten as soon as you start describing your own business.
| Question | What it actually sets |
|---|---|
| A starting point | Search your trade for a ready template, or start from scratch. The template hands a real specification to the studio so the first build is not a guess. |
| A name | What the system is called in your account. Cosmetic; change it later if you like. |
| Which country it is for | Currency, VAT treatment and the invoicing rules the built system follows. Worth getting right. |
| Which language it speaks | The language of the finished system’s screens — separate from the language you talk to the studio in. |
Where it runs, and why that is permanent
If the platform offers more than one region you are asked where the system should run; if it offers one, the question does not appear and the default applies. Today the default is the European Union, in Frankfurt.
The region is fixed at creation. The cloud resources behind a system are created in that region and cannot be moved, so a system built in one region stays there for its whole life. Moving means building a new system and carrying the data across.
How many systems you can have
The plan you are on governs how much building you do per month, not how many systems exist. Start is described as one business system and the plans above it as several, because that is what the monthly credit allowance realistically supports — not because a counter stops you.
There is a ceiling above that, set by the platform’s own capacity rather than by your plan. If you hit it, the message says so plainly.
Deleting one
A system can be deleted from your account. Before it goes, the platform checks what would be lost and tells you — this is the point at which to take the export you meant to take. Deletion removes the system and its database; it is not a pause. Pausing your plan is the thing that stops building without removing anything.
RELATED
The twenty templates — the starting points, by sector
Where your data lives — the region question, in more detail
Tutorial: start your first system — the four questions, walked through