Your first contact with the platform: create the account, understand the Organization → Workspace hierarchy, turn on MFA, and provision your datalake.
Concepts#
- Account (user): your login identity (Google, email/password, or corporate SSO, when enabled). One person can belong to several workspaces.
- Organization: a purely administrative layer that groups N workspaces
(useful for agencies, BPOs, and groups with multiple CNPJs). The organization does NOT grant
access to data — whoever administers the org structure (role
org_admin) does not automatically see the data of any workspace. - Workspace: the real unit of isolation. Each workspace has its own datalake (dedicated dataset), its people, its plan, and its billing. Access to data always requires membership in the specific workspace.
Availability#
- Plans: all of them (Starter → Enterprise). The Organization layer and the workspace model are core — no plan is "capped" on these features.
- Region: Brazil (São Paulo).
Permissions#
- Whoever creates the account and completes onboarding becomes the workspace owner.
- Workspace roles (5 levels) and the organization role (
org_admin) are detailed in Roles (RBAC). - MFA is required for every account (security policy) — it's not optional.
Setup (step by step)#
Onboarding has 5 steps:
- Company — name, segment, and CPF/CNPJ (validated). If you already filled in a simulator or order form before, the fields come pre-filled.
- Plan — choose the plan and the payment method (Pix, Boleto, or Card). Without billing configured, the environment enters demo mode (no real charge is generated).
- MFA (required) — scan the QR code with your authenticator app (Google Authenticator, Authy, 1Password…) and confirm the 6-digit code.
- Provision datalake — the platform creates, in real time, the medallion
datasets (
prd_aurora_bronze,prd_aurora_silver,prd_aurora_gold) in the datalake. - Finish — review of what was configured and acceptance of the Terms of Use and the Privacy Policy (recorded with date and version).
After finishing, you land on the dashboard (/overview).
Validation (how to confirm it worked)#
- Step 5 shows a summary: 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.
- Platform operators check deep health via
GET /api/health?deep=1(covers the provisioned infrastructure).
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 with prefix
aurora. At the end, the three medallion datasets are created and she sees the empty
dashboard, ready to connect the first source.
Cost#
- Creating an account, organization, and workspace: R$ 0.
- Provisioning datasets in the datalake consumes cloud resources; the amount shown before billing is an estimate — the amount charged is the one on the invoice. See Usage and quotas.
Security#
- MFA required on every account.
- Isolation per workspace: each workspace has a dedicated dataset; queries are
scoped per workspace (
<prefixo>_bronze/silver/gold). - Encryption in transit and at rest; least-privilege IAM.
- The organization does not leak data between workspaces:
org_adminmanages the structure, never the data.
Limits#
- One workspace = one isolated datalake. Datasets are not shared between workspaces.
- The number of connections, creators, and viewers is set by the plan (see Plans).
- Isolation between customers is fail-closed: without the workspace scope, the query is refused.
Troubleshooting#
| 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, provisioning is simulated |
Next steps: Connect your first source.