Subscription and licensing
The plan, its entitlements, and which of them have been activated.
Demonstration project - no figure here describes a real facilityChanges are not saved
Why
Seats and projects are counted from the organisation's own records. No subscription exists: nothing has been purchased.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Plan
No subscription
Seats in use
10
Projects
3
Entitlements activated
0
No subscription exists
Nothing has been purchased and no paid service has been activated. The plan shown is the reference project’s own record, and the entitlements below describe what a plan would carry rather than what anybody is paying for.
Entitlements
| Entitlement | Included | Used | |
|---|---|---|---|
| Seats | no plan purchased | 10 | Not activated |
| Projects | no plan purchased | 3 | Not activated |
| OCR pages | 0 | 0 | Service never activated |
| AI tokens | 0 | 0 | No provider chosen |
| Storage | no bucket exists | 0 | No store provisioned |
A quota that does not exist, not a quota nobody used. Why
Deployment profile
| Component | Approved profile | |
|---|---|---|
| Application hosting | Vercel Cloud | In use |
| Database | Supabase Cloud PostgreSQL | Not provisioned |
| Object store | Supabase Cloud Storage | Not provisioned |
| Identity | Clerk Cloud | Not configured |
| Secrets | External secrets manager | Implemented |