Node owners
Donate idle Linux capacity. Keep control of your machine while helping services find a home.
Community-powered infrastructure
Put spare Linux capacity to useful work.
Kikapu connects people who can donate Linux capacity with people who need a small, isolated place to run a service.
In alpha. Join community updates, early testing, and working sessions on Discord.
Built around people
Three ways to help shape Kikapu.
Tenants
Describe a service in a manifest. Kikapu finds eligible capacity and runs it with strong tenant isolation.
Contributors
Test rough edges, improve docs, question trade-offs, and help build an infrastructure commons in public.
Short path, clear boundaries
Capacity becomes a deployed service.
-
1
Donate Linux capacity
Node owner installs Kikapu agent on a supported Linux machine and chooses to contribute available resources.
-
2
Connect out, run rootless
Agent opens outbound authenticated tunnel. Workloads run under per-tenant Linux identities with rootless Podman restrictions.
-
3
Deploy a service
Tenant applies a manifest. Control plane selects eligible capacity and routes public traffic through tunnel.
Trust boundary
Isolation is not concealment from host root.
Kikapu isolates tenants from each other. It does not hide workload data from a malicious node owner with root access.
Environment values and workload state can be visible to node-owner root and Podman inspection. Use Kikapu only with capacity providers you are prepared to trust for this boundary.
Read runtime security detailsAlpha community
Bring spare capacity, deployment needs, or sharp questions.
Discord is home for alpha release notes, working sessions, and community updates.
Join Discord