Limits, roles and permissions

Fargone ships with a fleshed-out roles & permissions system. Everyone starts with a generous default quota; higher limits are granted on request.

Roles

Role	Can do
`MEMBER`	Create apps & databases, deploy, manage own apps
`OPERATOR`	Higher limits (20 apps, 2 cores, 2GiB per app)
`ADMIN`	Everything, plus member approvals, role changes, and limit grants

The first account to register becomes an admin.

Default quota

5 apps per member
500 millicpu per app
512 MiB memory per app
256 MiB upload size
5 concurrent builds
120 API requests / minute
2 GiB storage
100 MiB CDN storage per member

Requesting more

Settings → Quota → Request more. Pick a limit, state what you need and why. Admins review the request and can grant exactly that limit to your account — or deny it with a note.

How grants work

Approved requests create a quota override scoped to your account. Overrides stack on top of your role's baseline. Admins can also bump any limit directly — no request needed — from Admin → Users → Limits. CDN storage is requestable the same way as any other limit.

Admin approvals

New members start ACTIVE (self-serve). If the instance enables approval-gated onboarding (requireApproval), new members start PENDING until an admin approves them in Admin → Approvals. While pending you can read the docs and browse the dashboard, but you can't create projects.

Per-app control

Each app belongs to a single owner who has full control over it. App-level collaboration is on the roadmap.