Overview
What EnclaveStack is, how it fits together, and where to go next.
What EnclaveStack is
EnclaveStack turns computers you already own — a Mac, a Linux box, a mini PC — into the services you would otherwise rent: apps, databases, caches, file storage, networks, queues, domains with HTTPS, VMs, monitoring and more.
It is one program. You start it, open its console, and create what you need from the console, the enclave command line or OpenTofu. It is open source (Apache-2.0), needs no account and sends nothing home.
How it fits together
- The control plane is the program you start. It keeps what you asked for in one SQLite file and makes it happen: a reconciler creates containers and VMs, retries what fails and puts back what drifts.
- Every resource runs on your machine: as a container on Docker Engine, or as a VM under QEMU.
- The console, the CLI and the OpenTofu provider are three ways to use one API. Anything one can do, the others can.
- Projects keep resources apart; people get viewer, editor or admin roles in each.
- Add a second computer and resources spread across both; private networks span them over an encrypted tunnel.
Where to go next
- Getting startedFrom nothing to your first database and app.
- Try it with sample dataOne command, filled with sample resources.
- Every serviceHow each one works, with diagrams and settings.
- CLI and OpenTofuScript it, or declare it as code.
- Source on GitHubThe code, the README and every design document.
- CommunityQuestions, ideas and what others host.
Something unclear or out of date? Tell us in the community, or improve these docs on GitHub.