CodingDocumented overviewLast checked Oct 1, 2026

epho: Pricing, Features & Best Use Cases

HTTP API that runs Claude Code, Codex or OpenCode coding agents in cloud sandboxes with your repos, files and MCP servers attached.

Who epho fits

Use epho if you want to start Claude Code, Codex or OpenCode agents in cloud sandboxes with a single HTTP request and pay only for sandbox seconds, with model tokens billed to your own key. Based on the vendor's documentation, not on a hands-on test.

Best for: Developers automating coding-agent workflows over HTTP

Also a good fit for

  • Teams that want cloud-hosted Claude Code/Codex runs without managing sandboxes
  • CI and bot builders

Consider another tool if requires your own OpenAI/Anthropic/OpenCode Zen key for non-free models; tokens billed separately

Or if

  • Teams start capped at five concurrent active turns; excess requests queue
  • Only one live turn per chat at a time

epho pricing and usage limits

Prices checked Oct 1, 2026 on the official US pricing page. Official pricing ↗ Prices and limits change often.

Free access and trial conditions

OpenCode Zen models ending in -free run without a provider key; sandbox time is still billed

$10 starting credit on signup (about 60 hours of the default instance)

Paid plans: what changes as you upgrade

Usage-based sandbox API

Usage-based source (opens in a new tab)

Unknown, annual commitment

Default 2 vCPU / 2 GiB / 10 GiB instance is about $0.0000438 per second, roughly $0.0026 per one-minute run

For: Developers running coding agents from scripts and CI

Limits

  • Five concurrent active turns to start; extra requests queue
  • One live turn per chat
1 more
  • HTTP 402 when credit balance is zero

Includes

  • Claude Code, Codex or OpenCode harness
  • Repos, input files, MCP servers and env vars attached
2 more
  • Streaming SSE or async with webhook
  • cost_usd reported on every run

API included

Usage caps, credits and extra costs

Model tokens are billed by your own OpenAI, Anthropic or OpenCode Zen account

Not stated

What is epho, and how does it work?

epho exposes coding-agent harnesses (Claude Code, Codex, OpenCode) as a single HTTP endpoint. You POST a prompt with a harness, model, your provider API key and optional repos, input files, MCP servers and environment variables; epho boots an isolated cloud sandbox, runs the agent and streams tool calls, edits and the final answer back over SSE, or accepts the job asynchronously with webhook delivery. Runs are grouped into durable chats that resume the same sandbox and agent session across turns. Billing is usage-based per second of sandbox CPU, memory and disk; model tokens are billed by your own provider, not by epho. The service is operated by Bruin Data Limited.

epho homepage — screenshot of the coding AI tool, Oct 1, 2026
epho's official site: how the product presents itself. epho.io, captured Oct 1, 2026

What you provide and what you get back

How epho works: what you provide, where it runs and what you get backYOU PROVIDEYour inputPrompt with harness and model cho…Your provider API keyGit repos (up to 32) with tokensInput files, MCP servers, environ…CODINGephoWeb, APIfree tier, paid price not publish…free tier availableaccount requiredchecked Oct 1, 2026YOU GET BACKThe resultSSE stream of tool calls, edits a…Done event with presigned artifac…Async job IDs plus webhook delive…input → epho → output · from the vendor's own pages, no hands-on test unless stated
What you give epho and what comes back, from its documentation

You provide

  • Prompt with harness and model choice
  • Your provider API key
  • Git repos (up to 32) with tokens
  • Input files, MCP servers, environment variables

You get back

  • SSE stream of tool calls, edits and final answer
  • Done event with presigned artifacts
  • Async job IDs plus webhook delivery

Where you can use it

Platforms
Web, API
Account
Required

Best use cases for epho

Scenarios are worked out by our editors from the documentation; the actual result depends on your input and plan.

Automating pull-request reviews or issue-to-PR pipelines from CI, cron or GitHub Actions

Who
DevOps and platform engineers
You provide
Repo URL and review prompt triggered from CI, cron or GitHub Actions
Expected result
Agent run with diff and answer streamed back
Plan needed
Usage-based
Limitation
Capped at five concurrent turns initially source (opens in a new tab)

Running many coding agents in parallel on private GitHub, GitLab or Bitbucket repos

Who
Engineering teams
You provide
Several private GitHub, GitLab or Bitbucket repos
Expected result
Parallel agent runs in isolated sandboxes
Plan needed
Usage-based
Limitation
Each chat allows one live turn at a time source (opens in a new tab)

Building bots (Slack, Discord) that hand coding tasks to a cloud agent and stream results

Who
Bot builders
You provide
Slack or Discord message turned into a coding task
Expected result
Agent result streamed back into the chat
Plan needed
Usage-based
Limitation
You must handle your own key and bot wiring source (opens in a new tab)

What epho does, and where it stops

epho homepage — screenshot of the coding AI tool, Oct 1, 2026
Feature overview on the official site. epho.io, captured Oct 1, 2026

One POST /api/v1/chat endpoint; streaming (SSE) or async mode with webhook_url

Exposes the whole service as one POST /api/v1/chat endpoint with SSE or async mode and webhook_url Lets any script start an agent without SDKs

Access: All usageLimit: Streaming needs a client that handles text/event-stream source (opens in a new tab)

Choice of harness: Claude Code, Codex or OpenCode, switched by one field

Switches between Claude Code, Codex and OpenCode by changing one field Compare agents on the same request shape

Access: All usageLimit: Non-free models need a matching provider key source (opens in a new tab)

Bring-your-own provider key; OpenCode Zen '-free' models run without a provider key

Sends your provider key per request; OpenCode Zen -free models need none Keeps model billing on your own account

Access: All usageLimit: Tokens are billed separately from epho source (opens in a new tab)

Durable multi-turn chats that resume the same sandbox filesystem and session

Keeps durable chats that resume the same sandbox filesystem and agent session Supports follow-up tasks without losing context

Access: All usageLimit: Replacement sandbox restores a session snapshot if the box is gone source (opens in a new tab)

epho: strengths and limits

Where epho is strong

  • Per-second usage billing with a reported cost_usd on every run You can see the cost of every run documented source (opens in a new tab)
  • $10 starting credit on signup (about 60 hours of the default 2 vCPU / 2 GiB instance) You can test the service before adding funds documented source (opens in a new tab)
  • No SDK or local daemon required; plain HTTP/curl works You can integrate from any language documented source (opens in a new tab)
  • Public docs with quickstart and API reference You can find endpoint details before committing documented source (opens in a new tab)

Limitations to check before paying

  • Requires your own OpenAI/Anthropic/OpenCode Zen key for non-free models; tokens billed separately You manage two bills: sandbox time and model tokens documented source (opens in a new tab)
  • Teams start capped at five concurrent active turns; excess requests queue Large fleets must request higher concurrency documented source (opens in a new tab)
  • Only one live turn per chat at a time Follow-ups on the same chat cannot overlap documented source (opens in a new tab)
  • Requests are refused (HTTP 402) once credit balance reaches zero Unattended jobs can stop when credit runs out documented source (opens in a new tab)

How to use epho for running a coding agent in a cloud sandbox over HTTP

epho documentation — screenshot of the coding AI tool, Oct 1, 2026
epho documentation: where the steps below come from. epho.io, captured Oct 1, 2026

Set up epho

  1. Sign up at app.epho.io and copy your epho API key
  2. Pick a harness (claude, codex or opencode) and a model
  3. Prepare a repo URL with an access token if the repo is private

Example: running a coding agent in a cloud sandbox over HTTP

  1. POST to /api/v1/chat with harness, model, prompt, provider_api_key and repos
  2. Read the SSE stream for tool calls and the done event
  3. Reuse the returned chat_id for a follow-up turn
  4. For long jobs, call /chat/async with a webhook_url

Review and export the result

  1. Check the cost_usd field in the done event against your credit
  2. Open the returned artifacts or diff before merging anything
Example prompt suggested by our editors (not a recorded output of the product)
Add a /health endpoint to the API that returns 200 with the current git commit, and write a test for it.

epho integrations and API

epho documentation — screenshot of the coding AI tool, Oct 1, 2026
epho documentation (continued). epho.io, captured Oct 1, 2026

Native integrations and export formats

Export: SSE event stream, Presigned artifacts

API access and separate billing

epho has no public API in its official documentation. Single POST /api/v1/chat endpoint plus /chat/async API documentation ↗

Privacy, data use and commercial rights

Summarized from the vendor's current policies; this is not legal advice and a vendor's badge is not an independent audit.

How your inputs and outputs are handled

Prompts, repos and files are sent into an isolated sandbox

unknown

unknown

Commercial use and plan restrictions

unknown

unknown

Controls for business users

  • Provider key sent per request and torn down with the run
  • Isolated cloud sandbox per chat

Other tools to consider instead of epho

"Better suited" is based on documented features and pricing, not on a head-to-head test.

Cursor: better suited to

GitHub Copilot: better suited to

Replit: better suited to

Devin Desktop (formerly Windsurf): better suited to

Alternatives
AlternativeWhen to choose itPricingLimitation
Cursor——Compare
GitHub Copilot——Compare
Replit——Compare
Devin Desktop (formerly Windsurf)——Compare

Explore epho further

If you are looking at epho

epho user reviews

No user reviews yet.

Used epho? Be the first to share your experience.

Write a review

Reviews are checked by a moderator before they appear. Your email is never published. Plain text only.

Your rating (required)

Show what you made or what went wrong. Images are published only if the review is approved; location data is removed.

    epho FAQ

    How is epho priced?

    It is billed per second for sandbox CPU ($0.0000164 per vCPU-second), memory ($0.0000053 per GiB-second) and disk, about $0.0026 per one-minute run on the default instance. source (opens in a new tab)

    Do I need my own model key?

    Yes for non-free models: your OpenAI, Anthropic or OpenCode Zen key rides along with each request; OpenCode Zen models ending in -free need no key. source (opens in a new tab)

    How much free credit is there?

    New accounts get a $10 starting credit, about 60 hours of the default 2 vCPU / 2 GiB instance. source (opens in a new tab)

    Which agents does it run?

    Claude Code, Codex and OpenCode, selected with the harness field. source (opens in a new tab)

    Can I continue a previous task?

    Yes, pass the chat_id to resume the same sandbox filesystem and agent session, though only one live turn per chat is allowed. source (opens in a new tab)

    Sources and review methodology

    Official sources and verification dates

    Not verified: Data retention and training terms (privacy page 404); Tax handling; Higher concurrency tiers.

    How we documented and maintain this page

    Every fact about epho above comes from the 3 official pages listed here, last compared on Oct 1, 2026; we have not run epho ourselves, so it has no editorial score. How we check and re-check pages.

    Article updated Oct 10, 2026; prices checked Oct 1, 2026. Outbound links to vendors are plain links; we do not earn commissions. How we review · Report an error