Security
Projects, team roles, scoped tokens and two-factor sign-in
Odinex organises resources in projects inside an organization. Invite your team with the role each person needs, give each tool its own API token limited to one project and to read or read-write access, and protect accounts with two-factor authentication.
At a glance
- Organization roles
- Owner, admin, billing, member
- Project roles
- Admin, member, read-only
- Token scopes
- Read or read-write, per project
- Sign-in
- Password + 2FA, or Google
- Price
- No extra charge
Key features
Projects
Keep production and staging apart, each with its own resources, members and tokens.
Organization roles
Owner, admin, billing and member, so finance can pay invoices without touching servers.
Project roles
Admin, member or read-only access per project.
Scoped API tokens
Tokens see one project, can be read-only, can expire, and show when they were last used.
Two-factor sign-in
Authenticator apps with recovery codes, and sign-in with Google.
SSH keys, not passwords
Servers are created with your SSH keys, so there are no SSH passwords to leak.
What it is used for
Agencies
One project per client, with access only for the people working on it.
Separate environments
Production tokens that CI cannot reach, and a read-only token for monitoring.
Finance without root
Give the billing role to whoever pays, without access to any server.
Documentation
Teams and access: questions and answers
Clear answers about location, infrastructure and billing.
Can I give someone read-only access?
Can an API token access several projects?
Is two-factor authentication supported?
What happens when I revoke a token?
Build it in Frankfurt today
Create an account, top up from €5 and pay by the hour, never more than the monthly price.