Skip to main content

Cloud platform for AI agents

Agents write code. TOSE ships it to production.

Infrastructure for agents, control for humans.

The cloud your agents can ship to. Deploy from GitHub, your terminal or a coding agent, and manage infrastructure, permissions and costs in one place.

  • Billed by the hour
  • No subscription
  • Unreleased items are marked Coming soon
  • Checked against production 

TL;DR

TOSE is a cloud platform for AI agents. Developers, AI agent builders and small teams deploy container apps from GitHub, the TOSE CLI, the API or a coding agent to Kubernetes, with a domain and SSL set up for them. Pricing is hourly from each workspace's prepaid wallet: $0.02 per vCPU-hour and $0.01 per GB of RAM per hour for every workspace, disks $0.15 per GiB-month; each top-up from $100 earns bonus credit, up to +25% from $1000; no subscription and no free tier. Managed Agent Runtime, Browser Engine, Cloud Desktop, CI Harness and automated operations are not released yet (Coming soon).

01 Workflow

From one command to production, with a human at the wheel.

People and agents share one pipeline: command, build, run, control. Scroll through each step.

STEP 01

One command

You or your agent type the same command. --json returns machine-readable output, --wait waits until the deploy finishes, --dry-run checks before anything runs.

  • The API key is read from TOSE_API_KEY (starts with tose_sk_) or --api-key-stdin.
  • tose doctor and tose capabilities let an agent check its environment before it starts.

STEP 02

Build

Connect a repository. With a Dockerfile, TOSE builds from it; without one, TOSE generates it for common runtimes: Node, Bun, Deno, Python, Go, Rust, Java, PHP, .NET or a static site.

  • linux/amd64 builds, 2 GB memory, 45-minute limit. A new deploy is refused (HTTP 402) when the wallet is empty.

STEP 03

Run

The app runs on Kubernetes with a domain and SSL set up for it. Add a custom domain and TOSE issues and renews the certificate. Change vCPU, RAM and replicas when you need to.

  • A new project starts at 1 vCPU, 2 GB RAM and 1 replica.
  • Managed PostgreSQL, MySQL, Redis and MongoDB; persistent disks keep data while a workload is stopped.

STEP 04

Humans stay in control

Agents work within the scope you grant. Each workspace has one prepaid wallet, and it is a hard spending limit: an agent cannot spend more than the balance. If something goes wrong, roll back in one click.

  • Scoped API keys (Beta): The dashboard form and the CLI cannot set scopes yet; a key without scopes keeps full workspace access.
  • Out of balance: compute pauses and disks are kept; top up and the project starts again.
my-app · productionInterface illustration
# the API key is read from the environment
$ export TOSE_API_KEY=tose_sk_...
$ tose deploy --dry-run --json
$ tose deploy --wait --json
{"status":"running","url":"https://my-app.tose.sh"}
--json--non-interactive--dry-run--wait--yes
Terminal illustration: deploying with the TOSE CLI using --wait and --json.
~/my-appDockerfile found → build from the Dockerfile
  • src/
  • package.json
  • Dockerfilefound

No Dockerfile? TOSE generates one for:

  • JSNode
  • BnBun
  • DnDeno
  • PyPython
  • GoGo
  • RsRust
  • JvJava
  • PhPHP
  • .N.NET
  • {}Static

linux/amd64 builds · 2 GB memory · 45-minute limit

Illustration: TOSE detects a Dockerfile or generates one for a common runtime.
https://my-app.tose.shAutomatic SSL

kubernetesproduction

  • my-app1 vCPU · 2 GB · 1 replica
  • api
  • worker

{"status":"running","url":"https://my-app.tose.sh"}

Illustration: the app runs on Kubernetes with an SSL-secured domain.

workspacemy-team1 workspace · 1 prepaid wallet

Prepaid wallethard spending limit

balance hits zero → compute pauses · disks are kept · new deploys: HTTP 402

tose_sk_••••••Betalimited scopes; outside them: insufficient_scope

  • v3 · running
  • v1
Illustration: a workspace, a prepaid wallet as a hard spending limit, a scoped API key and one-click rollback.

02 The big picture

Many ways in, one control plane.

GitHub, the terminal, the API or a coding agent all enter the same workspace, with the same keys and wallet, before build and runtime.

GitHubgit push · repository
TOSE CLItose deploy --wait --json
APIOpenAPI 3.1 · header X-API-Key
Agent--json · --non-interactive
TOSE control planepermissions, keys and wallet in one place
  • Workspaces and permissions Available
  • Scoped API keys Beta
  • Prepaid wallet, hard limit Available
BuildYour Dockerfile or a generated one · linux/amd64
KubernetesvCPU · RAM · replicas · persistent disks · databases
Domain + SSLhttps://my-app.tose.sh · custom domain

Illustration of the flow

03 Three journeys

One platform, three starting points.

One brand, one control plane. Pick your journey; every item carries its real production status.

01 · DEVELOPERS

Developers and indie builders

Deploy apps from GitHub, the CLI, the API or a coding agent. Works in production today.

  • Build from a Dockerfile or a generated one Available
  • Custom domains, automatic SSL Available
  • Resize vCPU, RAM, replicas; rollback Available
  • PostgreSQL, MySQL, Redis, MongoDB Available
02 · AI AGENT

AI agent builders

Run the AI workloads you already have as containers and connect an agent through the TOSE CLI.

  • Container workloads Available
  • CLI --json, public Skills Available
  • Managed Agent Runtime Coming soon
  • Browser Engine Coming soon
  • Cloud Desktop Coming soon
03 · TEAM

Startups and teams

Workspaces, permissions, a prepaid wallet and hourly costs, for the people and the agents on your team.

  • Workspaces and permissions Available
  • Prepaid wallet, top up in VND or USD Available
  • Scoped API keys Beta
  • Automated operations Coming soon

04 Why · Features

Why TOSE

We only write Available when it runs in production.

Agent-native from day one

The CLI has --json, --dry-run, --wait, doctor and capabilities. OpenAPI and the Skills catalogue are public and readable without signing in.

$tose capabilities --json
$tose skills install deploy-nextjs-to-tose

Humans stay in control

Workspaces, scoped API keys (beta) and a prepaid wallet that is a hard spending limit: an agent cannot spend more than you topped up.

WorkspaceScoped keyPrepaid wallet

Public prices

Down to the vCPU-hour. No subscription and no separate bandwidth charge (Fair Use applies).

No vendor lock-in

Standard Docker and Kubernetes. Your Dockerfile stays yours.

Stopped means stopped

When the wallet runs out, compute stops and disk data is kept. Roll back in one click.

Built in Vietnam

Support in Vietnamese and English. Top up in VND by bank transfer.

Honest, with evidence

Status follows production, with a check date and a public release gate. No figure without evidence behind it.

AvailableBetaComing soon

Available: runs in production. Beta: usable, with its limits stated. Coming soon: not open yet, only on the roadmap.

05 Roadmap

Today it runs your apps. Next, infrastructure for the agents themselves.

Today TOSE runs your apps and lets agents deploy through the CLI. Next, agents get their own runtime, browser, desktop and CI. After that, agents operate production within the permissions people grant. Unreleased items carry no date: each opens when it passes its release gate.

  1. TodayAvailableBeta

    TOSE runs your apps; agents deploy through the CLI.

    • Running in production

      linux/amd64 builds, 2 GB memory, 45-minute limit. A new deploy is refused (HTTP 402) when the wallet is empty.

      Read more →
    • Running in production

      Only commands in the published npm package. The API key is read from TOSE_API_KEY.

      Read more →
    • Running in production

      Read-only documents. Calling the API needs an API key in the X-API-Key header, never in a URL.

      Read more →
    • Running in production

      Provisioned size is billed per GiB-month even while the workload is stopped.

      Read more →
    • Running in production

      No signup credit. An empty wallet suspends compute and keeps disks.

      Read more →
    • Beta: current limits

      The dashboard form and the CLI cannot set scopes yet; a key without scopes keeps full workspace access.

      Read more →
    • Running in production

      8 tools: 6 read-only (projects, deployments, logs, incidents) and 2 mutating (deploy_project, rollback_deployment) that need write scopes. Skills are not served to MCP clients.

      Read more →
  2. LaterComing soon

    Agents operate production within the permissions people grant.

    • Release gate

      Backend epic tose-app#101 and durable background loops (tose-app#146).

      Follow the roadmap →

    Agents that will run on TOSE

    • Pi agent (pi.dev)
    • Claude Code
    • Codex
    • Dewee
    • GoClaw
    • OpenClaw
    • Hermes Agent
    • And More

    Infrastructure for agents, control for humans.

Follow the roadmapChangelog →

Statuses checked against production on

06 Cost

Public prices, down to the vCPU-hour.

No subscription, no free tier, no signup credit. You top up the wallet and TOSE deducts by the hour at one rate for every workspace; each top-up from $100 adds bonus credit.

Top-up bonus (one payment)

One rate for every workspace: $0.02 per vCPU-hour, $0.01 per GB RAM-hour.

1 vCPU
1 GB
0 GiB

The sliders are for estimating only. A new project starts at 1 vCPU, 2 GB RAM and 1 replica.

Estimate

$0.03/ hour

≈ $21.90 / month (× 730 hours)

  • vCPU$0.02 / hour
  • RAM$0.01 / hour
  • Disk ($0.15 / GiB-month)$0 / month

A $500 top-up credits $600.00 to the wallet (including non-expiring bonus credit).

VND top-ups use 26,000 VND per USD: about 569,400 VND a month. Disks are billed per GiB-month even while the workload is stopped, on their provisioned size. Bandwidth is not charged separately; Fair Use applies.

07 AX

For agents

Public, machine-readable ways in. OpenAPI and the Skills catalogue are readable without signing in. They are documents, not an MCP server; the MCP server is listed separately below.

Getting started for agents
$ npm i -g @tosesh/tose
$ export TOSE_API_KEY=tose_sk_...   # or: tose login --api-key-stdin
$ tose doctor --json
$ tose capabilities --json
$ tose deploy --dry-run --json
$ tose deploy --wait --json
$ tose status --json
$ tose skills list
  • debug-failed-deployment
  • deploy-go-service-to-tose
  • deploy-nextjs-to-tose
  • optimize-cloud-cost
  • safe-rollback

09 Templates

Dewee and GoClaw on TOSE

Two official templates. The deploy button appears only for a verified version; the others offer docs and a waitlist.

Coming soon

Dewee AI Agent Platform

A Go-based multi-agent gateway, as described by the Dewee project. Deploying this template from TOSE is not available right now.

docs.dewee.shDewee · Multi-Tenant AI Agents

Fees and billing are listed on the pricing page. Pricing

Features as described by the Dewee project at docs.dewee.sh

  • 8-stage agent pipelineContext, history, prompt, think, act, observe, memory, and summarize in one complete agent loop.
  • Knowledge VaultWikilinks, hybrid search, pgvector, filesystem sync, and scoped workspace knowledge.
  • Agent team orchestrationShared task boards, delegation, handoff, and three orchestration modes for multi-agent work.
  • 20+ LLM providersAnthropic, OpenAI, OpenRouter, Groq, DeepSeek, Gemini, Mistral, Codex, and compatible endpoints.
  • 7 messaging channelsTelegram, Discord, Slack, Zalo OA, Zalo Personal, Feishu/Lark, and WhatsApp.
  • Production securityRBAC, encrypted API keys, rate limiting, prompt injection guards, SSRF protection, and tracing.

Coming soon

GoClaw AI agent platform

A Go-based AI agent platform, as described by the GoClaw project. Deploying this template from TOSE is not available right now.

goclaw.shGoClaw · Enterprise AI Agents

Fees and billing are listed on the pricing page. Pricing

Features as described by the GoClaw project at goclaw.sh

  • Multi-tenant by defaultPostgreSQL Row-Level Security isolates every tenant — serve customers safely from day one.
  • 5-layer securityRate limiting, prompt-injection detection, SSRF guards and AES-256-GCM encryption baked in.
  • 20+ LLM providersAnthropic, OpenAI, Google, Groq, Mistral… swap models with a single config change.
  • 40+ built-in toolsWeb search, code execution, database queries and full MCP protocol support out of the box.
  • 7 messaging channelsTelegram, Discord, Slack, WhatsApp… agent teams with shared task boards and handoff.
  • Enterprise observabilityOpenTelemetry tracing, structured logs and audit trails ready for production workloads.

08 FAQ

Frequently asked questions

Anything that runs in a container: Next.js, React, Vue, Nuxt, Svelte, Node.js, Python, Go and other runtimes. With a Dockerfile, TOSE builds from it; without one, TOSE generates it for common runtimes.

A prepaid wallet per workspace. Top up in VND by bank transfer (SePay) or in USD by card (Polar). Compute is billed per hour and disks per GiB-month. No subscription.

No. New accounts start with an empty wallet; a deploy with an empty wallet is refused (HTTP 402). When the balance runs out, apps pause and disks are kept; top up and they run again.

Yes. A persistent disk is billed on its provisioned size, $0.15 per GiB-month, for as long as it exists, whether the workload runs or not. Delete the disk to stop the charge; its data is deleted with it.

Through the MCP server at https://app.tose.sh/mcp: add the URL to your MCP client, sign in to TOSE and approve the scopes (OAuth), no API key needed. Or the TOSE CLI with --json and --non-interactive, an API key in TOSE_API_KEY, plus the public OpenAPI 3.1 description and Skills catalogue.

Because we only mark a feature available when it runs in production. Each item has a release gate and a check date on the Roadmap.

Yes. Add a custom domain and TOSE issues and renews SSL for it.

Email contact@tose.sh, in Vietnamese or English. There is no guaranteed response time (SLA) yet.

Ship your first release today. You stay in control.

The wallet starts empty: top up in VND by bank transfer or in USD by card, then deploy from GitHub, the CLI or an agent.