Configure each environment, and keep secrets secret
Variables for production, previews and development, sensitive values kept as secrets, crons declared in your repository, and sign-in on preview addresses.
Environment variables
Set each variable for production, preview, development or any of them, for one app or shared across the organisation. Import a .env file in one go.
Secrets
Sensitive variables are secrets: hidden in Cloud, with versions, rules for who can read them back and rotation reminders. Every read is in the audit log.
Crons
Declare scheduled routes in si.json. When a deployment becomes production, its crons replace the schedules, so they always match the code that's serving.
Deployment protection
Require a sign-in on each deployment's own address, previews included, and give tests and monitors a bypass secret.
Kept safe along the way
Encrypted with your keys
Values are encrypted with your organisation's keys, and each build receives them sealed, so they never appear in its record.
Development secrets
Mark a development secret readable by developers, and the command line brings it to their machine.
Cron calls you can check
Every cron call carries your app's cron secret for the route to check, since the route is public like the rest of the app.
Deploy your next app on Cloud
Complete and Enterprise include it, with Git, Pipelines and the rest of your workplace.