One engine per project
Each project is one hyphae serve process with its own data directory. Native is the only durable authority for its data. How it works →
Hyphae Cloud
A hosted backend where every project is its own Hyphae Native engine. The Cloud puts authentication, routing, limits and lifecycle in front of it — and stores no project data itself.
Two credentials
Your session manages a project; a project key (hyp1_…) lets an application use its data plane. Credentials →
Storage, realtime, functions
Object storage with a Cloud catalog, an ephemeral realtime fanout, and trusted-code functions with encrypted secrets. Guides →
Snapshots are Native backups
hyphae backup create on a sleeping project, verified by Native; restore replaces the directory. Snapshots →
What this is, in one paragraph
Section titled “What this is, in one paragraph”Hyphae Cloud runs one Hyphae Native process per project, each owning one data directory, and puts authentication, routing, limits, and lifecycle control in front of it. The Cloud stores no project data itself: Native is the only durable authority for a project’s data. Everything the Studio, the hcloud CLI and the JavaScript client show or do is a public HTTP route you can call yourself.
Read what it is not before relying on any property this page does not state.