Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.suji.fr/llms.txt

Use this file to discover all available pages before exploring further.

Suji has three tiers of grouping. Going from outer to inner: 
You (user)
  └─ Organization              ←  billing entity
        └─ Project              ←  permissions + naming scope
              ├─ VM 1
              │    └─ App install A
              │    └─ App install B
              └─ VM 2
                    └─ App install C

​
Users

A user is a single human identity (email + password, optionally with OAuth and 2FA). Every action in Suji is attributed to a user via the audit log.

​
Organizations

An organization is the billing entity. Credits, invoices, payment methods, and spend caps live on the organization. Every user belongs to at least one organization — a personal organization is created automatically on sign-up. Organizations have members with roles:
  • Owner — full control, including billing and member management.
  • Admin — manage projects, members, settings; no billing access.
  • Member — can act inside projects they’re added to.
Owner is required for billing actions (top up, change payment method, transfer ownership, delete the org).

​
Projects

A project is a permissions + naming scope inside an organization. VMs and app installs live inside projects, not directly under the org. Projects let you:
  • Separate prod from staging without separate billing.
  • Grant a contractor access to one project without exposing the rest.
  • Group resources for an audit-log filter.
Each organization gets a default project on creation; you can add more. Project members can be Admin (manage the project’s resources + members) or Member (use the resources). Org owners and org admins have implicit access to every project in the org.

​
What this means in the URL

URLs in the dashboard reflect this hierarchy: 
https://app.suji.fr/app/<organization-slug>/<project-slug>/instances/<vm-id>
So your bookmarks tell you exactly which org and project you’re looking at.

​
Switching orgs / projects

Sidebar dropdowns let you switch organization and project independently. The selected pair persists per browser session.

​
Audit log

Every meaningful action (instance created, app installed, secret rotated, member added) is recorded in the audit log at the project level, with the actor, the IP, and the user-agent. Org owners can view the audit log across all projects from Settings → Audit log.

​
Next

VMs

The actual machine that runs your apps.

Billing & credits

How charges flow — at the organization level.