Use cases
Where the boundary earns its keep.
Velone is not interesting for an agent that summarises documents. It is interesting the moment an agent can spend money, change a record, or run code you did not read.
01 / four starting points
01 · Coding agents
Untrusted code that cannot reach production
The agent clones a repository, installs dependencies, and runs whatever the tests run. Every one of those steps is arbitrary code execution on your behalf.
Dependency confusion · credential theft · accidental force-push
02 · Customer operations
Refunds and emails behind a human gate
Support agents resolve tickets end to end, which means they issue refunds, change entitlements, and send messages under your brand.
Wrong customer · duplicate refund · tone incident at scale
03 · Financial operations
Money movement with a provable trail
Reconciliation, invoice matching, and payment runs are exactly the work agents are good at and exactly the work auditors ask about.
Unauthorised payment · segregation of duties · unprovable approval
04 · Data engineering
Warehouse access scoped per session
An agent writing SQL against production data needs read access to a lot and write access to almost nothing.
Full-table scan · PII egress · silent schema change
02 / the common shape
Every one of these is the same problem wearing a different hat.
An agent needs real access to be useful, and real access is exactly what makes it dangerous. The answer is never less access — it is access that is scoped, gated, and recorded.
Ring 0
Start with the workload that scares you.
Not the safe pilot. The one your security team already asked questions about.