Subscription required
1–15 compute hours are included each month, depending on your plan. Choose it for regular agent work and a predictable baseline.
Velqa Sandbox
Give your AI agents a place to work.
Run Python or Node.js tasks in isolated environments. A subscription is required; compute beyond its included allowance is pay-as-you-go.
Pay-as-you-go compute
After the included allowance, compute is billed at 0.30 USD per hour from your Boost balance, measured by the minute from the moment a sandbox starts until it is released. You pay for the extra capacity you use.
Built for agent work
Create an agent profile, choose Python or Node.js, then keep the execution and its artifacts in your Velqa dashboard.
The Sandbox Agent is in beta. Use it when you need the AI to do something, not only talk about it; for a plain question or text generation, the chat stays faster and cheaper.
Open SandboxHow a Sandbox turn works
1. Create an agent
Give it a name, pick the Python or Node.js runtime, choose the model that drives it and write its instructions. The agent is saved in your dashboard and reusable for every conversation.
2. Run a turn
Each message starts a fresh Docker sandbox. The agent writes and reads files, runs shell commands, executes code and keeps Python state between its own calls, while you follow every step as it streams.
3. Collect the result
When the work is done, the agent publishes the file you need as a downloadable artifact. The sandbox is then released and disappears: nothing carries over to the next turn unless it was published.
What teams use it for
- Run and check code instead of reading a model's guess: execute a script, run the tests, read the real error.
- Process a file you upload to the workspace — a CSV to clean, a log to analyse, a document to convert.
- Chain several tool steps into one deliverable: compute, transform, then publish a report or a dataset to download.
- Prototype a data or automation task in Python or Node.js without installing anything on your machine.
Limits that protect your budget
Isolated and ephemeral
Every turn runs in its own Docker sandbox. Uploaded files and artifacts stay in their context and never leak to another agent or conversation.
One sandbox at a time
Each account runs a single sandbox at once, whatever the plan, so a runaway loop cannot multiply your compute.
A daily spending cap
Each plan has a daily ceiling. A turn whose estimated maximum cost would cross it is refused before it starts, not after.
Shared fleet, clear errors
When every platform slot is busy, creation answers 429. It is neither your rate limit nor your balance: try again a few minutes later.