Deploy

You clone or fork, we open

Opplet Enclave is open-source — every tool, every configuration, every decision is public. Deploying means taking those blueprints and standing up your own enclave. There are two ways to do it, and the difference matters.

Clone — track opplet

Cloning stands up your own instance while staying in opplet’s lineage. You run the same stack and pull updates from upstream as the project evolves. Choose this if you want sovereignty over your data without taking on the burden of charting your own technical direction — you’re running opplet, on your own metal.

Fork — make it yours

Forking takes the blueprint and diverges. You start from opplet and then go your own way: different software, different zones, your own direction. Updates no longer flow to you automatically, because you’re no longer running opplet — you’re running the thing you built from it. Choose this if you want full independence, including from opplet itself.

Start here

Review the existing technology first — the enclave lays out what runs and how the zones connect. Then take those blueprints to build your own private cloud, at home or on your organization’s servers. Practice on opplet first; deploy your own second.

Has anything clicked?

If reading this made you want to argue with it, extend it, or notice what's missing, that's the signal to show up.

You're invited to:

commit register to step into opplet partner advance or support the development sync chat or stay without committing deploy clone or fork opplet as your enclave
:/back-to-top