Onboarding is the assistant that appears once, right after the account is created.
It has 5 steps — when you finish, you land on the
overview dashboard (/overview) and the wizard doesn't
show up again.
What it is#
A guided flow (/onboarding) that provisions everything a workspace needs
to work: company registration, plan choice, required MFA, and the actual
creation of the medallion datasets in the datalake. Progress is saved at each step — if
you close the tab, you pick up where you left off.
What it's for#
- Going from zero to a provisioned datalake without touching cloud infrastructure.
- Guaranteeing, right at the start, the two non-negotiables: MFA on and isolation per workspace (dedicated dataset).
Who does it and when#
- Whoever creates the account and completes onboarding becomes the workspace owner.
- It runs only once per workspace. Once completed (
onboardingCompletedAt), accessing/onboardingredirects straight to/overview. - In a demo environment (no billing/cloud configured), provisioning and billing are simulated — no real charge is generated.
The 5 steps#
| # | Step | What happens |
|---|---|---|
| 1 | Company | Name, segment, and CPF/CNPJ (validated in real time). If you already filled in a simulator or order form, the fields come pre-filled based on your email. |
| 2 | Plan | Choice of plan and payment method (Pix, Boleto (bank slip), or Credit card). Without billing configured, it enters demo mode. |
| 3 | Security (MFA) | Scan the QR code with your authenticator app (Google Authenticator, Authy, 1Password…) and confirm the 6-digit code. Required step — there's a manual key next to the QR code as an alternative. |
| 4 | Datalake | The platform creates, in real time, the medallion datasets (prd_aurora_bronze, prd_aurora_silver, prd_aurora_gold) in the datalake. You follow each change step by step. |
| 5 | Finish | Summary (company, plan, MFA: Enabled, datasets created) and required acceptance of the Terms of Use and the Privacy Policy, recorded with date and version. |
In steps 2 (Plan) and 3 (MFA) there's a Back button to correct data (for example, a CPF/CNPJ). The provisioning and finish steps can't go back.
Prerequisites#
- An authenticated account (Google, email/password, or corporate SSO, when enabled for your organization).
- A TOTP authenticator app for MFA.
Expected result#
- Step 5 shows company, plan, MFA: Enabled, and the datasets
created (e.g.,
prd_aurora_bronze, prd_aurora_silver, prd_aurora_gold). - On the dashboard, the workspace appears with the company name and the dataset prefix.
- Operators check deep health via
GET /api/health?deep=1.
Example#
The owner Maria creates the account for Comércio Aurora Ltda, chooses the
Growth plan, turns on MFA, and provisions the workspace Aurora Varejo (prefix
aurora). When she accepts the terms, the three medallion datasets are created and she sees
the empty dashboard, ready to connect the first source.
Limits and costs#
- Creating an account, organization, and workspace: R$ 0.
- Provisioning datasets consumes cloud resources; the amount shown before billing is an estimate — the amount charged is the one on the invoice.
- Provisioning creates your workspace's datasets in the datalake; in the demo environment it's simulated.
Security#
- MFA required on every account (security policy).
- Isolation per workspace from creation: each workspace has a dedicated dataset.
- Acceptance of terms recorded with date and version (audit trail).
Common errors#
| Symptom | Likely cause | What to do |
|---|---|---|
| CPF/CNPJ rejected in step 1 | invalid digits | check the document; the field validates in real time |
| "Demo mode" in step 2 | billing not configured in the environment | expected in the demo environment — no real charge |
| MFA QR code doesn't appear | temporary failure generating it | use the manual key shown next to the QR code |
| Provisioning doesn't finish | cloud infrastructure unavailable | try again; in demo it's simulated |
Related#
Last reviewed: 2026-09-08.