Security
Private by construction.
Isolation comes from how workspaces are built, not from file permissions on a shared machine.
How workspaces are isolated
Your own workspace
Every user gets a separate container and storage volume. Other users' files do not exist in yours.
Closed off by the network
Only the sign-in gateway can reach a workspace. A workspace can reach DNS and the internet, and no other workspace or internal service.
Locked-down containers
Workspaces run as a non-root user with no capabilities, a read-only system disk and no Kubernetes credentials.
Stopped when idle
A workspace stops after 3 hours without a connection. Sessions last 12 hours, and repeated failed sign-ins are throttled.
You stay in control
You approve the changes
In manual mode, nothing the agent proposes is written or run until you approve it.
Your cloud keys stay with you
Cloud and Jenkins credentials are saved on your own workspace volume, out of reach of other users.
Read-only log access
The agent can read your build and cloud logs. It cannot start or change a pipeline.
Where the AI runs
Devloom-Agent's model runs on Devloom's own servers. When the agent searches the web, its search goes through a search provider.
Found a security issue? Email support@devloom.ai.
Start building with Devloom.
Request an account and start as soon as it is approved.