Account
Plans and billing
You should know exactly what you are paying for and exactly what happens if you stop. Datadef has one free surface, the anonymous scratch canvas, and paid plans for everything that lives server-side; every account starts with a 7-day trial of the full product, no credit card asked. And when a plan ends, nothing you made is deleted. Current prices are on your dashboard.
How it works
- 1Sign up and the trial starts on its own: 7 days of the full product, no card, once per email address.
- 2Pick Pro for one person, or Team for up to 5 people on one flat subscription.
- 3If you stop, your account enters museum mode: everything stays viewable, and resubscribing turns writing back on with nothing to restore.
The plans
| Plan | Who it is for |
|---|---|
| Trial | Every new account, automatically: 7 days of the full product, no credit card, once per email address. |
| Pro | One person. Cloud projects, generation, sharing, embeds, MCP, repository sync. |
| Team | Up to 5 people in one shared workspace, one subscription. See Teams and folders. |
There is no free account tier: an account without an active plan can view everything it made but not create more. The free way to try Datadef is the scratch canvas, with 3 generations a day and browser-side storage.
Prices, upgrades, and billing management live on your dashboard.
Museum mode: when a plan ends
Nothing is deleted, ever
An expired trial and a lapsed subscription land in the same place: every project, version, and diagram stays intact and viewable. What stops is writing: editing, generating, creating projects, widening sharing, API access, and background repository syncs. Resubscribing turns it all back on; there is nothing to restore.
The precise consequences:
- Every write attempt gets the same refusal, in the app and over the API, naming the reason: editing needs an active plan.
- A lapsed owner may still make a public project private. Reducing exposure is always allowed.
- Collaborators on your projects whose own plan lapsed become viewers in practice; their roles resume when their plan does. See Sharing and permissions.
- Existing public links and embeds keep rendering the last state of the diagram; daily repository syncs pause until the plan is active again.
What needs a paid plan
- Cloud projects and unmetered generation.
- Inviting collaborators as editors or admins, and being one.
- Public links and embeds.
- MCP API keys and agent access.
- Repository connections and daily sync.