Give devboxes access and keep your company safe
Your data stays on servers in Germany, and your company decides what devboxes can use.
Your passwords and keys never reach the agent
devboxes keeps your passwords and access keys in its vault, and the agent works with a placeholder. The real key goes in only as a request leaves for a service you allowed. If someone tricks the agent into sending its keys somewhere, all they get is the placeholder.
Vault
GitHub token ••••••••
Upgrade the logging library
github.com placeholder
devboxes swaps the key
github.com Receives the real key
Your company decides which services a task may reach
Tasks read web pages that anyone can write, and an agent can make mistakes on its own. A task reaches only the services your company allows, so your code and data can't end up anywhere else.
Upgrade the logging library
Services your company allows
github.com
registry.npmjs.org
Your model provider
unlisted-host.net
Connect your own tools with only the permissions they need
When a tool inside your company, such as your support portal, should hand work to devboxes, give it an access key and choose what it may do. devboxes refuses everything else. Each key has fine-grained permissions, within what your own role allows.
Support portal
- Start tasks
- Follow a task
- Read results
- Change secrets
- Remove members
- Create more tokens
Hosted in Germany and running on your own model subscription
We store your company's data encrypted on European-owned servers in Germany. devboxes uses the AI model subscription your company already has, and your provider bills you directly.
Our servers in Germany
Get started for free SOn-premises
We set up the whole devboxes platform in your own data center or cloud account and maintain it for you under a contract.
Ask about On-premisesTasks can also run on your own machines. There, your own network rules decide what a task may reach.
Send us your security questions
For questions about personal data, write to privacy@devboxes.ai.