Accounts and organizations
One login at platform.ciresk.com, and the organization that holds people, keys, policy and budgets.
Sign in
You sign in once at platform.ciresk.com; every product uses that identity. Command-line tools log in with a device flow (ciresk ci auth login opens the browser) and keep the token in the OS keychain, never in a file; MCP clients sign in with OAuth from the client. There is no key to copy for a person.
Create an organization
The sign-in page at platform.ciresk.com also creates an account. Signed in without an organization, select Start your own organization: it is created in the EU region with you as its owner, and the console opens on it. Products are turned on per organization by Ciresk; to use Ciresk CI, write to [email protected] with your organization's name.
Organizations
An organization is the unit that owns everything across products:
| Held by the organization | Detail |
|---|---|
| People | Members and their roles; a key cannot be created with more than its owner's role allows, and it stops working when the owner leaves. |
| API keys | Created under API tokens (or My profile › API tokens for one that acts as you). See API keys. |
| Region | The organization's jurisdiction pins it to one region; Ciresk runs in the EU only today. See Regions. |
| Policy | Per-product policy, for example which refs Ciresk CI treats as untrusted and whether full builds are allowed. |
| Audit | Key changes, and in Ciresk CI job submissions, policy changes and token exchanges, are audit rows the organization reads through the API. |
| Budgets | Budgets and usage are per organization and product, under Billing. |
A person can belong to several organizations; a credential belongs to exactly one.
Where identity lives
Identity is hosted by Ciresk's identity provider, WorkOS, which stores identity data in the US; it holds no product content. See Data residency for what Ciresk CI keeps where.