Account
Workspace & Projects
Structure of workspaces and projects, API keys, and plan limits.
Workspace
A workspace is your top-level account. It maps to an organization or an individual. All billing, projects, and settings live within one workspace.
One login = one workspace. Multi-workspace support is not available in MVP.
Projects
A project typically maps to one application or environment. Use separate projects for production vs staging, or for distinct products.
Each project is independent:
| Resource | Scoped to |
|---|---|
| API keys | Project |
| Event stream | Project |
| Event schema | Project |
| Saved tables | Project |
| Destination connections | Project |
Creating a project
- From the workspace dashboard, click New Project
- Enter a name
- The project is created with a default API key
Project limits
| Plan | Max projects |
|---|---|
| Free | 1 |
| Starter | 5 |
| Pro | Unlimited |
API keys
Each project has one or more write keys. Write keys are used to authenticate SDK and REST API calls. See the SDK Quickstart to use your key.
- Keys are project-scoped — a key from Project A cannot write to Project B
- Rotate a key from Settings → API Keys → Regenerate
- Old keys stop working immediately after rotation
Team members
In MVP, each workspace has a single owner. Team member invitations and role-based access control are planned for post-MVP.