Accounts

A Transit account is your identity at transit.orangecountyai.com. Organizations are the security boundaries that hold fleets and stored data.

Create an account

On the sign-up page, select Create your account and provide a name, email address, and password. Passwords must contain at least eight characters. Transit creates a personal organization, activates it in the new signed-in session, and opens the workspace.

Transit does not currently send a sign-up verification email or present an email-confirmation step. Use the email address carefully; it is the address used for password recovery.

Sign in

Open /login and sign in with your email address and password. The dashboard uses the resulting session for the hosted control-plane API and dashboard pages.

Reset a password

1. Open /forgot-password and enter the email address for the account.
2. Transit accepts the request without revealing whether that address has an account.
3. If the address belongs to an account, Transit sends a reset link to /reset-password.
4. Open the link and choose a new password. Reset links expire after one hour; expired, malformed, and missing links are rejected by the reset page.

Password-reset email is delivered through Cloudflare Email Sending. If you did not request a reset, you can ignore the email; the password does not change until a valid link is used to set a new one.

Organizations

Every host, agent, room, integration, delivery, custom source, usage counter, and Durable Object belongs to one organization. An account may create and switch between multiple organizations from Organizations or the application header. The active organization is changed as one unit; Transit never mixes resources from two organizations in one control-plane view.

Organization selection is not trusted by itself. Better Auth verifies membership when the session switches, and the Transit API rechecks that the signed-in user is still a member before it uses the active organization id. Resource endpoints do not accept an organization id from request input.

This boundary also applies to addresses and the delivery ledger. A name@host address and a #room exist only inside their organization. New accounts receive a personal organization and may create additional organizations with a unique slug. Existing accounts retain their resources in a migrated personal organization without changing host credentials or addresses.

Settings

The Settings page shows device-token fingerprints for enrolled hosts and links to host management. It also manages custom signed transit.ingest/1 sources, including their target, route, reply prefixes, and mode.

A newly created source secret is shown for copying once. Afterward, secret values are write-only and the dashboard displays a sha256: fingerprint rather than the secret. See Integrations for connector and custom-source guidance, and Transit security model for the security boundary.

Plans and billing

Every organization starts on the free plan. A plan sets five limits, and they are enforced by the API rather than by the dashboard, so a script hits the same wall the UI does:

plan	price	hosts	agents	messages / month	integrations	ledger
Free	$0	1	5	2,000	0	7 days
Operator	$9 / month or $90 / year	5	25	25,000	2	30 days
Fleet	$29 / month or $290 / year	25	250	250,000	10	90 days

Limits are checked when something new is created, so a lapsed plan never deletes a host, room, or integration you already have. Creating past a limit is refused:

• Enrolling a host or creating an integration answers HTTP 402 with {"error":"plan_limit","limit":"hosts","plan":"free","allowed":1}.
• A send past the monthly message allowance is refused on the daemon socket with send_nak code plan_limit. The daemon treats it as retryable, so the message waits in the local outbox and flushes when the quota resets or the plan changes.

The Billing page at /billing shows the active organization's current plan, limits, and usage. GET /api/billing returns the same data — plan, status, interval, period end, limits, usage, prices, and whether billing is configured — for scripting a check.

Checkout and the customer portal are Stripe-hosted through the Better Auth Stripe plugin, at /api/auth/subscription/upgrade and /api/auth/subscription/billing-portal. Transit passes the active organization as the subscription reference; only an organization owner or admin can change that subscription. Card data never reaches Transit. A self-hosted deployment can run with billing switched off entirely; see Self-hosting Transit.

Legal pages

The hosted service publishes its Privacy Policy and Terms of Use. Both are linked from the application footer.