Which model runs my workflow?

You pick the model for each workflow. Models are routed through LiteLLM, so you can switch vendors at any time.

How do I cap what this costs?

Set a monthly spending limit for the organization. When credits run out, triggers stop starting runs. Auto refill is optional.

What happens when a run fails?

The run is marked failed and the full transcript stays in run history, with each tool call and error. There are no failure alerts yet.

Where does my data go?

Each run gets its own sandbox that is discarded afterwards. Secrets are envelope encrypted and attached to requests at the network layer, so the sandbox never sees them.

Do you support SSO and SCIM?

Yes. SAML and OIDC single sign-on and SCIM provisioning come through WarpBuild auth, which Helios shares.

Can I stop a run that is going wrong?

Yes. Cancel a run from the run page or stop a chat while it is working. The transcript up to that point is kept.

Agents with real computers

Your team has
better things to do.

Give Helios the support roundup, the CRM cleanup, or the report that eats your Monday. Agents get a cloud computer, your tools, and the context to get to work.

Get started free

Book a demo

5,000 free credits. Invite your whole team.

Get me ready for my call with Acme. Pull together the latest emails, account details, and meeting notes.

Read the account history
Catch up on recent conversations
Find the notes from last time

Meeting brief

Acme · ready for your call

Renewal is next month. The team is expanding to two new regions and asked about SSO in the last call.

3 sources, one briefing Ready to review

An example of a task, from ask to done.Meet Helios

Right at home
with your tools.

See all

One less Monday chore

The roundup’s ready.
You haven’t opened a tab.

Ask Helios to read the week’s support threads, find the recurring problems, and send your team a digest. Use the same prompt in a workflow to do it every Monday.

Explore workflows

Example workflow Mon, 09:00 UTC

Support · weekly digest

142 threads.
Here’s what came up.

31
Invoice confusion
4 enterprise accounts affected
12
Slow CSV exports
Most reports involve large files
09
SSO login loop
Reports point to Safari

Digest posted to #support-leads

GitHub issue #1187 opened for invoice confusion

Every run gets its own machine.

Helios can write a script, run it, and use the result. Each task starts in a fresh sandbox with its own shell and files.

Bun, Node, git, and jq are preinstalled. The agent writes a script, runs it, and reads the result.
It can search the web and read a page when the task needs facts that are not in your tools.

See how runs work →

support-digest

environment

v4 · Dockerfile

CPU: 2 vCPU
Memory: 4 GB
Disk: 10 GB

files

~/context
org/ project/ personal/
~/workspace
app/ threads.json themes.md
/tmp

installed

bash
git
bun
node
python
jq

Created
09:00:02 UTC
Running
4m 12s
Stops
at 30 min

Your tools, without the copy-paste.

Agents get the complete API of each connected tool. They find the right endpoint for the task and call it.

Helios indexes each tool's API. The agent finds the endpoint it needs and makes the request.
The egress proxy attaches your credential on the way out. The sandbox never holds the token.

See integrations →

GitHub

integration · full API indexed

find-relevant-apis

“open an issue for the top support bug”

POST/repos/{owner}/{repo}/issues

parameter	in	value
owner	path	acme
repo	path	app
title	body	Invoice confusion: 31 threads this week
labels	body	["bug", "support"]

201 Createdissue #1187credential added by the egress proxy

Shared knowledge. Reviewed changes.

Agents write to a shared Library. A person reviews the diff and approves each file before it becomes the team's context.

Organization, project, and personal files mount at ~/context in every run.
Edits are staged for review. A person approves or discards each file. Agents cannot approve their own.

See the Library →

org/support/themes.md

Proposed by run 8f3c · Modified · waiting for review

 ## Recurring themes -1. Invoice confusion (24 threads)+1. Invoice confusion (31 threads, 4 enterprise accounts)+   Tracked in acme/app#1187 2. Slow CSV export (12 threads)+3. SSO login loop on Safari (9 threads)

Getting started

Start with the task you keep putting off.

An engineer connects tools, environments, and access. After that, anyone on the team can hand work to an agent.

01
Describe the task
Write what you want done in plain words. Name the tools it should use and the output you want back. Start it in chat and watch each tool call.
02
Attach a trigger
Reuse the same prompt as a workflow. Run it by hand, on a schedule, from a signed webhook, or on a GitHub, Slack, or Plain event.
03
Review the run
Open the run. Every command, tool call, and result is in the transcript. Changes to shared files wait for a person to approve them.

Integrations