TaubyteOne node binary. One compiler. One artifact that's the same thing everywhere.
A node runs the services its config names: register, worker, gateway, stats, auth, secrets, and the build backend, all from one binary. A cloud is a set of these nodes joined into one swarm.
Services per Node
7
One binary
Compiler Checks
Every push
Line-accurate errors
Content-Addressed Objects
1
Per compiled project
Swarm Nodes
N
Closed by default
Push → Compile → Run
Per push
1 artifact
Compared
Content-addressed
Requests Routed
96,850
Last 7 days +12%
Infrastructure as code you already trust
Every other platform asks you to trust a dashboard, an API, or a vendor's control plane. Taubyte v2 asks you to trust git. Because you already do.
Code review for infrastructure
The same PR flow your team already uses.
Rollback is git revert
Not a support ticket.
Branches map to environments
main to production, release/* to staging, anything to a preview.
Full audit trail for free
Every infra change is a commit, with an author and a diff.
Zero surprise
Everything in a project, a function, a database, a queue, a gateway route, an AI agent, is one of 23 typed kinds. A resource can't accidentally be two things.
The access block is the whole permission model.
A workload declares exactly what it reaches and which verbs it wants. Checked before anything is touched.
Verbs belong to the target, not the caller.
Asking a cache to exec a query is a compile-time error.
Multi-instance resources get admission control.
Addressed as label/instance; the first open runs a validator function you write.
A cloud is a closed swarm.
Nodes join with a swarm key; outbound egress is denied by default.
The path from push to response
Build
A git push reaches the build service, which compiles and publishes the project by name to the register.
Route
A client request hits the gateway, routes by host and path; placement picks a warm worker.
Run
The worker resolves the target, turns its access block into grants, and runs it.
What runs on your laptop is what runs in production
WebAssembly components
function, worker, component: Component Model with WASI 0.2, no filesystem or sockets, a hard memory ceiling.
Containers
application, sandbox, worker: Docker or containerd, egress firewall and memory limit.
Static sites
website: build output served directly from the content-addressed asset store.
One compiler, three surfaces.
dream starts several full nodes in one process. Same routing, same services, same deployment flow as production. One compiler runs in the CLI, the build service, and the browser (compiled to WebAssembly). What validates your config locally is byte-for-byte the same logic that validates it on push.
JSON Schema & TypeScript types: Emitted for your editor and tooling.
Decompile: A built object can be turned back into source files.
See how it connects to what you already run.
Composable Capabilities covers your existing data layer, messaging, and storage.