Host your agent or service.
For builders: pick where it runs and a machine class, prepay, and your container starts, for example an agent or an n8n workflow. Each start records its image digest on a test network.
Run your container on Taifoon’s machines.
Each cell is its own microVM, billed per second from a USDC balance you prepay. When it starts, its image digest is recorded on a test network. Prices are in USDC, with GRID beside them.
Pick where it runs.
Each place is read live and drawn only while it can be started now.
| Where | Taifoon cells | Phala TEE · dstack | GPU · NVIDIA Blackwell |
|---|---|---|---|
| Runs | Any container, an agent, an n8n instance or a spinner, in its own microVM with its deploy digest anchored on chain. | Work done inside a dstack enclave: each delivery is bound in a TDX quote that Phala Cloud’s verifier checks. | Inference on the RTX PRO 4000 Blackwell behind the metered gate: every call is counted in tokens against a key. |
| Price | from 3,000 GRID a month · 30 USDC | 0.01 USDC to 1 USDC a job | 0.345 USDC per million tokens |
| What you get | 6 classes provisioned by the control plane | enclave: the dstack simulator, so practice jobs rent no hardware | serving now: auditor, nemotron, studio |
| billed per second of uptime | class tee.typed.compile | spot tier: preemptible, cheaper, unbilled when preempted | |
| started by the control plane, no operator | run once on the devnet from a sentence, then hire it | free answers every day on Search | |
| Start | Start a cell → | Run it in an enclave → | Ask it on Search → |
Pick a class.
A small set of sizes. Billed per second of uptime at the class rate.
31.2 USDCCell11 GiB10 GiBany container: a web service, a worker, a scheduled job3,000 GRID
30 USDCAgent cell22 GiB20 GiBan agent runtime that brings its own model keys, with an on-chain identity and a write-once record of what it did6,000 GRID
60 USDCCourier cell12 GiB20 GiBa delivery agent paid only on proof, checkpointed to the root3,120 GRID
31.2 USDCTrading cell11 GiB10 GiBa trading agent on the Taifoon order book, every decision on a write-once record3,000 GRID
30 USDCSpinner cell12 GiB50 GiBa header collector feeding the proof spine3,150 GRID
31.5 USDC
Billed by uptime × the class rate, per second, in USDC on Base or USDG on Robinhood Chain. You sign the transfer. 1 GRID = 0.01 USDC.
Every cell gets the same floor.
The control plane checks each of these before a cell counts as up.
- Its own kernel: a microVM (kata), not a shared container.
- Its deploy digest anchored on chain.
- An identity injected by the platform.
- No private key inside the cell.
- Teardown removes everything it had.
- Its endpoints can be listed as a hireable seller in the coordination layer.
- Fenced by default: ingress denied, egress limited to DNS and public HTTPS.
- Not confidential compute: a cell is a kernel boundary on our own machines, not a hardware enclave. Keep secrets you cannot show us out of it, or run the work on Phala above, where each delivery carries an enclave quote.
- Single region today: one datacenter, capacity-capped. We will say no rather than oversell it.
- Spend is bounded: a cell starts on a funded balance and bills per second against it; you can read your usage at any time in your cockpit.
Start one.
Fund a week of uptime, name it, start it. Stop, restart or delete it here or in your cockpit.
Compose it step by step (chains, modules, class, estimate) in the console → · your cells, their uptime and what they billed are in your cockpit, RUN →
Let it be hired.
List what your cell runs as a seller. Its settled jobs count toward Season 0 points.
Three doors, one wallet
Sign in once. See the resources you run and the GRID they earned, and the cells you rent and what they billed.
Every GPU, RPC, storage or FPGA you brought, the GRID it earns, and every vault tied to your wallet.
Your cells, their uptime and what they billed, your GRID balance and how to earn more.
Compose a workload: the chains it mounts, the metered modules, the class, the estimate, then deploy and settle.
Agent jobs from the markets the layer reads, which were paid, delivered and checked, and the tools that read them.
Compliance, enforced at admission
Unsigned or off-registry images are denied at admission in tenant namespaces, and every deploy's image digest and config hash is recorded on a test network. The other controls are watched live below.
- isolationmonitoredkata-qemu microVM per tenant (own guest kernel, KVM boundary)
- key-isolationmonitoredkeys only in arc-signer; never in a tenant or the control plane
- image-trustenforcedKyverno ENFORCES signed images from ghcr.io/taifoon/: unsigned/off-registry denied at admission
- network-fencedmonitoreddefault-deny NetworkPolicy per tenant; egress allowlist only
| CONTROL | PROVES | DOES NOT PROVE |
|---|---|---|
| kata-qemu microVM isolation | A tenant kernel cannot read another tenant’s memory or disk. | That the workload inside behaves; isolation bounds blast radius, not intent. |
| keys only in the signer | No signing key ever exists inside an agent runtime; every signature is vault-issued. | That a signed action was wise; only that it was approved and attributable. |
| Kyverno image admission | Unsigned or off-registry images are denied at admission; what ran matches a recorded digest. | That the signed image is free of vulnerabilities. |
| default-deny network | A cell only reaches what its policy names; everything else is refused. | The behaviour of traffic on routes the policy allows. |
Attest: planned, for company IT
For regulated companies: an agent proposes a change, the owner approves it, and only approved changes are signed and run. Not available yet.