Surfaces & tiers

The tiers are not three separate products. Starter, Business, and Pro are three depths over one product: how many surfaces and gateways you have unlocked over the same folders and the same captured IP. You start on the web, add your channels and tools in the middle, and graduate to the direct surface at Pro, never changing products and never moving your data.

Three depths, one product#

Every account works the same folders in the same cell. What a tier changes is reach: how many gateways connect your employee to your channels and tools, and which surfaces you can open over your data. Progression is unlocking depth, not switching to a different app.

Three surfaces over the same folders#

The cell filesystem is your data. Every surface is a view or an editor over the same folders, never a second database. Jetsyn ships three surfaces, and each renders those same folders at a different depth of reach.

The line between the surfaces is mediation. A conversational surface is employee-mediated and async: you tell it what you want, it does the work, it reports back. A direct surface (the CLI) is synchronous: you are in the files yourself, live. Same files, different depth of reach.

The CLI makes the distinction concrete. The command you run in the cell decides the mediation, over the same transport and the same cell.

# Direct: you are in the folders yourself, live (the Pro depth)
jetsyn connect

# Conversational: talk to your employee; it works the folders and reports back
jetsyn agent

How access is gated#

Access is decided server-side, never in the browser. One endpoint reflects your plan and whether the product is unlocked.

GET /api/me returns your {plan, status, entitled}. The entitled flag is the gate: it is true when your subscription status is active or trialing, and false for a free or lapsed account. A new subscription starts with a short trial that counts as entitled, so the product is unlocked from the first day; the card is collected up front and the first charge lands after the trial.

When a locked account hits a protected action, the server returns HTTP 402 with billing_required. That response is the client's cue to open checkout. Gate your own actions the same way: read entitlement server-side and return 402 when it is false, never trusting a plan label read in the browser.

Moving between depths#

Changing tier reprices your live subscription in place. Your cell, your folders, and your captured IP never move. Going from Starter to Pro unlocks the direct surfaces over the exact data you already built; there is no re-onboarding and no migration.

POST /api/billing/change-plan reprices the subscription to another tier, prorated on the next invoice and applied as soon as the change is confirmed. POST /api/billing/cancel defaults to end of period, so a canceled account keeps access until it is paid through.

Where to go next#