Solo project, light usage
One Standard runtime. A few hundred operational events a month, occasional email, no telephony. Closest to the Starter pack with auto-refill.
The compute your exocorp runs on. Billed continuously while the runtime is up. Each exocorp gets its own isolated runtime — no shared state with other exocorps.
Everything your exocorp pays for outside the runtime itself — SMS via Twilio, email via Postmark, search via Exa, cloud storage, third-party APIs. Each runs through your exocorp’s wallet at pass-through cost. You can set per-category limits in Settings → Budgets in the operator portal.
SMS, voice, and similar communications when your exocorp talks to humans through phone networks. Pass-through at the vendor's published rate.
Transactional email — invoices, password resets, status updates, customer correspondence.
External APIs the exocorp calls for live information — research, competitor signals, customer intent, factual lookups.
Cloud storage for artifacts, customer files, generated assets — anything outside the runtime's local disk.
Plugins that talk to paid third-party APIs (Stripe, Slack, GitHub, etc.) typically pass-through the vendor's billing. Plugins themselves are free to install.
Included in the runtime cost — not separately metered.
One Standard runtime. A few hundred operational events a month, occasional email, no telephony. Closest to the Starter pack with auto-refill.
One Standard runtime, regular customer-facing communication (email, occasional SMS), search APIs feeding research. Closest to the Plus pack monthly.
Two or three runtimes plus moderate auxiliary spend per exocorp. Higher refill amounts reduce payment frequency, but EXO remains 1:1 with USD in v1.