Compute That Exists Only For The Instant

Isolated compute that materializes the moment work arrives, executes with precise timing, then vanishes. Nothing idle, nothing retained.

smallest.ai
neuroform.ai
SYNTRIX
Composio
calsoft
Kiln
Tsuki Labs
smallest.ai
neuroform.ai
SYNTRIX
Composio
calsoft
Kiln
Tsuki Labs
//  Request → verified ready  //
Faster than you can blink. (Seriously)
0000ms
0
50
100
150
200
250
300
t = 0 · request
Setsuna
True cold boot · 2 vCPU · 16 GiB
0
MACHINES READY
E2B
Firecracker · snapshot resume
0
MACHINES READY
Vercel Sandbox
Snapshot resume
0
MACHINES READY
Fly Machines
Initial machine
0
MACHINES READY
Modal
gVisor
0
MACHINES READY
0 true-cold microVMs
before Modal returns its first sandbox.
Setsuna cold launches 2 vCPU / 16 GiB microVMs in 59 ms from request to verified ready. Then again. And again.
$12M Raised
Kenji Arai|Sky9 Capital|Engineers from Cloudflare and Fastly|and more
38ms
Median time to first instruction
100%
Stateless after every run
0
Idle seconds billed
4.2B
Instances materialized to date

State Of The Art On Every Latency Benchmark

Setsuna outperforms warm-pool serverless and reserved capacity on five of six BurstBench categories, including a −412ms lead on cold start and a 94% reduction in idle spend versus reserved VMs.

p50 cold start
38ms
p99 cold start
61ms
Idle spend / month
$0.00
Category Setsuna Warm pool Reserved VM Containers
Burst readiness
100.00
38.71
92.90
81.40
Isolation guarantee
100.00
8.93
80.40
94.60
Idle efficiency
96.67
40.00
56.70
20.00
Cleanup completeness
97.43
52.56
83.30
78.20
Timing precision
90.97
25.56
62.40
45.10
Multi-region burst
76.69
20.30
57.90
44.30
Overall score
93.62
29.07
71.20
60.20

Always-On Isn't Precision. Give Your Work The Exact Moment.

Persistent servers optimize for being ready, not for being right on time.

Setsuna materializes isolated compute for each unit of work, executes with deterministic timing, and destroys everything on exit. Burst-first, state-free, precisely timed.

Persistent Servers How Setsuna Works
Runs idle, waiting for work Materializes only when work arrives
Accumulates state, drift and exposure Vanishes completely after every run
Scales by planning capacity in advance Scales to the exact shape of the moment
Juggling autoscalers + queues + warm pools + cleanup jobs One primitive: appear, execute, disappear
//  特徴  Features  //

Everything You Need To
Compute In The Instant

Instant
Materialization

Isolated compute exists 38ms after the request arrives. No warm pools, no pre-provisioning, no waiting.

38ms
To first instruction
Isolated
By Nature

Every run is its own universe. Designed for zero shared state and zero neighbours.

One Instance
Spawn
Execute
Vanish
Leaves
No Trace

Memory, disk and network identity are destroyed on exit. Nothing to leak, patch, or audit later.

Input
Result
Nothing left
Precise
Timing
Always
< 40ms
Parallel
Bursts

Ten thousand instances in one instant. Everything materializes at once, so bursts never queue behind each other.

Deterministic
Handoff

Input, compute, and signed result arrive as one clean payload, so your systems know exactly what ran and when.

Result Pipeline
Input
Compute
Vanish
//  用途  Use Cases  //

Built For Work That
Should Not Linger

agent · 38ms
With Setsuna

Each tool call materializes its own sealed instance, runs with a deterministic clock, and vanishes with a signed result.

Without Setsuna

Tool calls share a long-lived sandbox where leftover state, files, and credentials bleed between runs.

//  Pricing  //

Pricing That Exists Only
For The Instant

Nothing idle, nothing retained. Placeholder plans while packaging is finalized.

Standard
$49/ mo

Per workspace, placeholder.

Get Started
  • 1,000 burst-hours per month
  • Shared readiness pool
  • Email and chat support
Premium
$199/ mo

Per workspace, placeholder.

Get Started
Everything in Standard, plus:
  • Unlimited burst-hours
  • Dedicated readiness pool
  • Priority execution lanes
  • Signed result delivery
  • 99.99% execution SLA
  • Priority support with 1h response

Frequently Asked
Questions

A single isolated unit of compute that materializes for one piece of work. It has its own memory, disk, and network identity for the duration of the run, and none of it survives the exit. Most instances live for a few hundred milliseconds. You are billed only for the instant it exists, never for readiness.