Use the HTTP API
Let Fenders handle tenant quotas, scoped keys, component uploads and scheduling. Your product calls the REST API to deploy apps and collect run output.
You run Control plane, PostgreSQL 17 and nodes
Read the API guideOpen-source infrastructure
Run each component in its own kernel-free KVM virtual machine. Use the Fenders API to manage tenants and runs, or connect the nodes to your own scheduler.
Introducing the Fenders
Deploy a Wasm component and watch its output from your terminal. The same binary lets operators manage tenants, keys and nodes on a self-hosted Fenders control plane.
fenders profile use acme✓ Now using profile acmefenders deploy job.wasm --name report✓ Deploy report — donefenders run report --logs✓ Run report — doneIntegration guides
Let Fenders handle tenant quotas, scoped keys, component uploads and scheduling. Your product calls the REST API to deploy apps and collect run output.
You run Control plane, PostgreSQL 17 and nodes
Read the API guideKeep your scheduler and storage. Assign work to a node through a control peer and receive output from each run through your own HTTPS endpoint.
You run Nodes and a shim for each run
Read the node guideBuild from source
On a Linux x86-64 host with KVM, build the node and run the two-tenant verification script. It starts the stack, deploys and runs components for both tenants, then cleans up.
Check build prerequisitesgit clone https://github.com/runtarahq/fenders.git
cd fenders
make build-node
bash scripts/verify_embedding_live.sh Requires the Rust toolchain, Docker and passwordless sudo. See the prerequisites for targets and kernel features.