Scoped job keys
A job that calls your apps gets a key that can call only the apps you listed. It cannot deploy or manage anything, and it stops working when the job ends.
Surfra starts machines in your accounts, so it holds keys that can spend your money. Here is how they are stored, when they are used, and what nobody can do with them, including you.
When you connect a cloud, Surfra makes a cheap read call to the provider with that key and nothing else. A key the provider rejects is never stored.
Each team has its own encryption key. Your cloud key is sealed with your team's key, and the team key is itself sealed with Surfra's master key. Production and development use separate master keys.
After you save a key, the dashboard and the API only show which provider it is for. There is no View button, not even for the person who added it. To change a key, replace it or delete it.
Surfra decrypts a cloud key only to start, check, and stop your machines. Each machine it starts is named after its Surfra replica id, so you can match it to the dashboard from your own cloud console.
A job that calls your apps gets a key that can call only the apps you listed. It cannot deploy or manage anything, and it stops working when the job ends.
Job and app environment values are encrypted when stored. Pages show each variable's name and where it came from, never its value.
A registered machine runs one workload at a time, and you can take it offline whenever you want.
Email hello@surfra.io and we will answer security questions directly.
Keys are never displayed by the dashboard or the API. They are decrypted only inside the service when it starts, checks, or stops your machines.
The sealed key is removed. Surfra will not delete a cloud account while replicas are still running on it.
Surfra is invite only while we test it. Tell us what you want to run and we will send an invite.
Request access