Security
2.0 organises access around teams. Members get roles. Deploy tokens are minted per role and expire.
nimbus team invite alex@acme.dev --role deployer
nimbus token mint --remote edge --scope deploy --ttl 1h
| Role | Can deploy | Can manage keys | Can invite |
|---|---|---|---|
viewer |
✗ | ✗ | ✗ |
deployer |
✓ | ✗ | ✗ |
admin |
✓ | ✓ | ✓ |
Edge functions run in a sandbox with no ambient credentials. Secrets are injected explicitly:
nimbus secret set STRIPE_KEY --remote edge
Never commit keys
Keep NIMBUS_KEY and any function secrets in a secret manager or the environment. nimbus.toml is meant to be committed and must stay free of credentials.For the full history of security-relevant changes, see the release changelog (PDF).