Sealed machine
Each agent runs alone on its own microVM. Nothing is shared, not even the kernel.
Median boot 2 min 51 s
Give every agent a machine of its own.
Claude Code, Codex, Hermes and 30 other agents, running in the cloud day and night. Each one boots into a sealed microVM that keeps its files and never lets your keys out.
Launch an agent ↗
First 7 days free
Your agents
Bring the agent you
already run locally.
Claude CodeBoots in 2:38 · ProPick ↗
Codex CLIBoots in 2:44 · ProPick ↗
Gemini CLIBoots in 2:41 · SoloPick ↗
AiderBoots in 2:22 · SoloPick ↗
OpenHandsBoots in 3:05 · MaxPick ↗
GooseBoots in 2:31 · SoloPick ↗
Hermes AgentBoots in 2:51 · ProPick ↗
OpenClawBoots in 2:47 · ProPick ↗
LettaBoots in 2:36 · SoloPick ↗
CrewAIBoots in 2:58 · ProPick ↗
MastraBoots in 2:40 · SoloPick ↗
browser-useBoots in 3:12 · MaxPick ↗
Also on Kiln: Amp, Cline, Continue, Crush, Kilo Code, OpenCode, Plandex and Roo Code. See all 14 ↗
Also on Kiln: AutoGen, LangGraph, Agno, Smolagents, Eliza, PydanticAI, Haystack, n8n agents and 5 more. See all 19 ↗
Features
Everything an agent needs
to keep going without you.
Keys that stay put
Your API keys are sealed to the machine. Only your agent can read them, never our staff.
Storage that persists
/persist survives every restart, so the agent picks up exactly where it stopped.
- SchedulesCron, webhooks, or always on. Missed runs replay after maintenance.
- Live terminalStream stdout from any machine and open a shell when you need one.
- Outbound allowlistPick the hosts an agent may call. Everything else is dropped.
- Its own addressEvery machine gets an HTTPS address. Custom domains from Pro.
How it works
Live in about three minutes.
Pick your agent
Run the agent you already use.
33 agents · 140 templates · one click
- Coding
- Claude Code, Codex, Gemini CLI
- Autonomous
- Hermes, OpenClaw, Letta
- Bring your own
- any CLI with a Dockerfile
- Your machine
- boots on its own, private to you
Choose a template
Start from a job that already works.
Or start blank and write the instructions yourself.
- SEO rank loop
- daily at 06:00
- PR review
- on every push
- Outbound research
- weekdays at 07:30
- Changelog
- Fridays at 16:00
Add your keys
Keys go in. They don't come out.
Sealed to one machine at boot, readable by one process.
- Stored
- encrypted to this machine
- Readable by
- your agent process
- Kiln staff
- no access, every attempt logged
- Rotation
- one click, no redeploy
Boot
It boots, then keeps running.
Median of the last 30 days, all regions.
- Allocate microVM
- 14 s
- Mount /persist
- 3 s
- Install agent
- 1 min 52 s
- Health check
- 42 s
- Live
- 2 min 51 s
The machine
Watch it work,
or read what it did later.
Every machine streams its terminal, keeps a trace of each run and shows the files it remembers. This is run #212 of the SEO agent at Ostrom Labs, at 06:00 this morning.
seo-rank-loop
kn-4f9a21 · Pro · Frankfurt
06:00:04
Open in Kiln ↗
- /persist
- memory/
- seo/2026-10-22.md 2.1 KB
- seo/2026-10-21.md 1.9 KB
- site-map.json 48 KB
- skills/
- fix-title.md 3 KB
- schema-faq.md 4 KB
- files/
- rankings.csv 212 KB
memory/seo/2026-10-22.md · written 06:02:44
Run 212
Search Console reported 11 pages that dropped since yesterday. Fixed 3 of them.
/pricingtitle cut from 71 to 58 characters, FAQ schema added. Rank 14 → 6./blog/agentsfour internal links added from older posts./docs/clicanonical tag restored after the docs redeploy.
Next: check whether /pricing holds position 6 for three days before touching it again.
Trigger
0 6 * * * Every day at 06:00, Europe/Berlin
Next runs
- Fri 23 Oct06:00
- Sat 24 Oct06:00
- Sun 25 Oct06:00
- Mon 26 Oct06:00
Last 30 runs
30 of 30 finished · median 2 min 38 s
Use cases
Put your agents on
all the work you
repeat every day.
Pages fixed and resubmitted every morning, without anyone opening Search Console.
Twelve accounts researched and first drafts waiting in your outbox by 07:30.
Every pull request reviewed within four minutes of the push, with comments on the lines that matter.
Overnight tickets triaged, tagged and drafted before the team logs in.
A Monday brief on competitors' pricing and releases, with every source linked.
One agent per customer, region or repo. Same template, separate machines, separate data.
Why a microVM
A container shares a kernel.
A microVM doesn't.
Agents run code they wrote a minute ago, with your keys loaded. Where that happens matters more than how fast it starts.
| Question | Kiln microVM | Shared container host | Your laptop |
|---|---|---|---|
| Kernel | Its own, isolated by hardware | Shared with other customers | Shared with everything you run |
| Where keys live | Sealed to the machine | Env vars on a shared host | Dotfiles on your disk |
| Runs with the lid closed | Yes | Yes | No |
| Files between runs | /persist, snapshotted | Lost on redeploy | Until you clean up |
| Cold start | 2 min 51 s, then always on | About 40 s per run | Already on |
| Price | Flat, from $24 a month | Per second, plus egress | Your electricity |
In production
Agents that have been
running for months.
- OstromLabs
- parcel/nine
- Fernhill
- BRIGHTWATER
- quillmate
- TESSERA
2 min 51 s
Median boot, last 30 days
99.97%
Machine uptime, last 90 days
One incident: 14 min, Ashburn, 2 Sep
1.4M
Runs finished in September
“Our SEO agent stopped every time a laptop went to sleep. On Kiln it has run 212 mornings in a row.”
Lucía FerrerOps lead, Ostrom Labs“We run one research agent per customer. Fifty machines, one template, and no customer's data ever sits next to another's.”
Kofi MensahFounder, parcel/nine“Security signed off in a day. The keys never touch a shared host, and the access log proves it.”
Margit OlsenCTO, BrightwaterPricing
A real machine for
every agent.
Every agent gets its own sealed machine at one flat monthly price. No usage billed on top, and no markup on your model tokens.
Solo
One agent, always on.
$24/ month
Billed monthly
Launch an agent ↗- CPU
- 1 vCPU
- Memory
- 2 GiB
- Storage
- 10 GiB
- Bandwidth
- 100 Mbit/s
- Web address
- Auto-assigned
- Daily snapshots
- No
Pro
RecommendedRoom for heavier agents.
$48/ month
Billed monthly
Launch an agent ↗- CPU
- 2 vCPU
- Memory
- 6 GiB
- Storage
- 50 GiB
- Bandwidth
- 200 Mbit/s
- Web address
- Custom domain
- Daily snapshots
- No
Max
For agents you can't lose.
$96/ month
Billed monthly
Launch an agent ↗- CPU
- 4 vCPU
- Memory
- 12 GiB
- Storage
- 100 GiB
- Bandwidth
- 500 Mbit/s
- Web address
- Custom domain
- Daily snapshots
- Included
Running 50 agents or more? Volume pricing and dedicated hosts in your region. Talk to us ↗
Why a microVM instead of a Docker container?
Containers share one kernel across every customer on the host, so a kernel bug in someone else's workload can reach yours. Each Kiln agent gets its own Firecracker microVM with its own kernel, isolated at the hardware level.
Can Kiln see my API keys?
No. Keys are encrypted to your machine when it boots, and only the agent process can read them. Staff access to machines is off by default, and every attempt shows up in your access log.
Is there a free trial?
The first 7 days are free on any plan. We ask for a card on day 7, not before.
Can I run more than one agent?
Yes. Every agent gets its own machine and its own line on the bill. Teams on Kiln run anywhere from 1 to 300.
Can I pay by the hour instead?
Not yet. A flat monthly price is what lets an agent stay on all night without anyone watching a meter.
Where do my agents run?
Frankfurt, Ashburn or Oregon. You pick the region when you launch, and the machine, its storage and its snapshots stay there.
What happens when I cancel?
Machines stop at the end of the billing period. You can download /persist and every snapshot for 30 days after that.