Authentication
Ghaymah has two ways to authenticate: the dashboard (browser session) and the REST API (bearer tokens). Both use the same account.
Sign in to the dashboard
Section titled “Sign in to the dashboard”Open deploy.ghaymah.systems. If you’re not signed in, you’ll see the login page:

New here? Click Create an account, fill in your details, and you’re in:

Creating an account takes less than a minute and gives you a free server to start with (see Billing).
Authenticate API requests
Section titled “Authenticate API requests”The REST API uses a bearer token on every request:
Authorization: Bearer <token>Tokens are scoped to one or more projects via an OPA policy, so a token can only touch the resources it’s allowed to.
Getting a token
Section titled “Getting a token”# 1. Create a project (admin scope) — returns an id and an initial tokencurl -X POST https://api.cumin.dev/projects \ -H "Authorization: Bearer $ADMIN_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "my-project" }'# { "id": "…", "token": "…" }
# 2. (Optional) mint an additional scoped token for a projectcurl -X POST https://api.cumin.dev/tokens \ -H "Authorization: Bearer $ADMIN_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "ci-token", "policy": "<opa-policy>" }'# { "bearer_token": "…", "token": { "id": "…", … } }Use the returned token for all subsequent requests. See the REST API overview for the full token model.
Next steps
Section titled “Next steps”- Deploy your first app
- REST API overview — token and project scoping in detail
- Dashboard tour — what you can do once signed in