What is Helios?
Helios runs AI agents in cloud sandboxes. Each agent gets a real computer, the full APIs of your tools, and shared files your team reviews, with SSO, roles, and encrypted secrets around it.
Helios is a platform for always-on AI agents. You describe a task in plain English; an agent picks it up, works it in its own cloud computer, and reports back.
There is one agent runtime, and you reach it two ways:
- Chat - talk to an agent interactively. Attach files, pin the repositories it should work in, share the transcript with a teammate.
- Workflows - put an agent on the task permanently. Save the same instructions as a prompt and attach triggers: a schedule, a webhook, or an event from GitHub, Slack, or Plain.
Same agent, two modes. Anything you can get an agent to do in Chat, you can hand off to a Workflow.
What an agent has
A real computer
Every agent runs in its own isolated cloud sandbox with a filesystem, a shell, and the ability to install packages and execute code. It can read and write files, search and scrape the web, and read the shared files in your Library.
The full API of every tool you connect
Helios does not ship a curated list of actions per service. Each integration has its entire API surface indexed, and agents search that index and call whatever endpoint the task needs. Authentication is applied server-side, so an agent acts on your behalf without ever holding your credentials.
Seventeen services are available: GitHub, Slack, Plain, Discord, Notion, Attio, Apollo, Stripe, Resend, Reddit, Typeform, Apify, WarpBuild, and Google Docs, Drive, Gmail, and Sheets - plus direct access to your Postgres, MySQL, and ClickHouse databases and any external MCP server you attach.
Shared context, reviewed by people
Pin a repository or other integration resource so an agent always knows which one you mean. Keep playbooks and reference files in the Library, where every run reads them. When an agent edits a Library file, a person reviews the diff and approves or discards it. See context for what carries between runs.
Controls your team can live with
Everyone delegates work; IT keeps the controls. Helios supports SAML and OIDC single sign-on with SCIM provisioning, organization roles and per-resource access control, envelope-encrypted secrets, signed webhooks with rotation, and an isolated sandbox for every run.
What a task looks like
A workflow is a prompt plus its triggers. There is nothing to wire up.
Every weekday at 9am, look at every pull request opened in acme/api in the
last 24 hours. For each one, summarize what changed and flag anything that
touches billing or authentication. Post the digest to #eng-standup.Attach a schedule for 0 9 * * 1-5, connect GitHub and Slack, and
the task runs itself. Each execution is recorded as a run with its
full transcript, every tool call, and a structured result.
Compliance and security
For security documentation, see the security page or contact [email protected].
No data passing through Helios is used for training or improving AI models. Helios stores data for managing and running your agents, and for providing the relevant functionality to users, in accordance with our data retention policy.
Where to go next
- Quickstart - connect a tool and hand an agent its first task.
- Key concepts - the vocabulary, in one page.
- Workflows - prompts, triggers, runs, and outputs.
- Integrations - what's connected and how to authenticate it.
- Roles and permissions - who can do what.
Last updated on