Provision your instance

Shipped

Provisioning is a console-only flow: you sign up, create an organization, create an instance, and watch it provision to Ready. Everything happens in the console at console.turbobase.io — there is nothing to install.

Signup is invite-gated. If you don’t have an invite yet, request one at console.turbobase.io/early-access; we’ll send you an invite link when we’re ready for you.

1. Sign up

1. Open your invite link, or go to console.turbobase.io/signup.
2. Enter your first and last name, email, and a password (at least 12 characters). The invite code travels with the link, so you usually don’t type it.
3. Verify your email when prompted, then you’re signed in to the console.

The console is the customer realm of Turbobase — a sign-in distinct from your live Turbobase app. See Open your app for why they’re separate.

2. Create an organization

An organization (org) is the billing and ownership boundary that owns your instances. On first sign-in the console walks you into creating one:

1. Go to Orgs → New (/orgs/new).
2. Enter the org name. The console auto-suggests a URL-safe slug from the name; you can edit it.
3. Provide a contact email, and optionally a website and a phone number. Your role is shown as Admin and can’t be changed — the first member of a new org is always its admin.
4. Submit. You’re now an admin of the org.

One human can belong to multiple orgs and switch between them; see Orgs and instances.

3. Create an instance

An instance is your own Turbobase — its own database and app at <slug>.turbobase.app.

1. Go to Instances → New (/instances/new). The form is scoped to your active org (set by the org switcher in the nav).
2. Enter the instance name; the console auto-derives an instance slug you can edit. This slug becomes your subdomain, so choose it carefully.
3. The region is shown read-only: every instance runs in our US East (Ashburn) region today. The plan picker stays visible so you can see the tiers, but it’s locked while pricing is finalized: every new instance is created on the entry plan, Ignition.
4. Submit. The console redirects you to /instances/<slug>/provisioning, where you watch the status live.

Note

Creating an instance requires Manage instances on the org. If you can’t see the form, ask an org admin to tick it for you. A newly self-signed-up org also needs staff approval before it can provision — if your org isn’t enabled yet, the page adds a You’re on the waitlist banner above the form with a sales address to write to. The form still works: your instance keeps its slug and plan and waits with a New (no access) badge until the org is enabled.

4. Watch it provision to Ready

Provisioning runs through a small state machine. The console shows each stage as a friendly status label; you don’t have to do anything but wait (it takes a couple of minutes):

What you see	What’s happening
Provisioning…	The instance record is created and work begins
Provisioning… (database)	Your dedicated Postgres schema is built
Provisioning… (services)	The instance’s app and sync services are deployed
Provisioning… (waiting for health checks)	We wait for everything to report healthy
Ready	Your instance is live

If something goes wrong the status flips to Failed — reach out to support. (You may also see New (no access) or Pending while the org waits on approval, as above.)

The full status vocabulary, including the upgrade and pause states, is documented in Orgs and instances.

Next step

A Ready instance has no data yet. Continue to Connect your first source to start the setup wizard and connect Oracle NetSuite.