What it is not

This page is copied from docs/product/claims.md, the normative wording authority for everything said about Hyphae Cloud. If a property is not stated elsewhere in these docs, assume it is not provided; if it is listed here, it is explicitly not provided.

Non-claims

The Cloud does not claim, and its APIs and documentation must not imply:

• high availability, failover, replication, clustering, or geographic redundancy — one project is one process on one host;
• serializable isolation, or any isolation stronger than what Native states;
• PostgreSQL wire compatibility, Prisma compatibility, ORM compatibility, “full SQL”, or “drop-in replacement” for any database;
• compatibility with or imitation of Supabase, Firebase, Amplify, Cognito, GoTrue, or any other hosted backend’s API or client library;
• a multi-tenant engine kernel, per-tenant quotas inside the engine, or shared-process isolation;
• durability beyond Native’s own durability classes for a given commit;
• TLS termination — cloudd has no certificate, no ACME client, and no https:// listener; a front terminates TLS and proxies to loopback;
• encryption at rest for project data (function secrets are the one exception, under the process key, not a KMS);
• multi-host realtime or an HA control store — one host, one daemon, one control file; the Compose file is unverified as Compose; the AWS deploy is one instance and one volume;
• tenant safety on a shared, noisy host beyond the rows above — a hostile or runaway project’s functions and engine compete for the same CPU, disk, and network as everyone else’s on that instance;
• control-plane backup, or the backup kit, as anything but file copies and per-tenant Native backups taken in sequence — no point-in-time consistency across control files, tenant volumes, and blob bytes; no scheduling; no off-host transport; no one-button restore; not a Native proof of anything beyond each tenant’s own NATIVE_BACKUP.json;
• snapshot retention, deletion, scheduling, or off-host storage — snapshots are directories under the daemon’s snapshot root, kept until an operator removes them; replaced data directories likewise;
• point-in-time recovery or branching — a snapshot is the state at the moment backup create ran on a sleeping tenant, and restore overwrites the single data directory with it;
• realtime durability, ordering across channels, exactly-once or at-least-once delivery, replay beyond the in-memory ring, WebSocket transport, or Native change feeds — system events are emitted by Cloud routes after they act, not derived from Native’s WAL;
• function sandboxing — no container, VM, seccomp, cgroup, or network isolation is claimed for functions; under Node there is no network restriction at all; a function is the owner’s own trusted code;
• function durability, scheduling, cron, logs retention, a KMS or HSM for secrets, secret versions being retrievable, per-function secret scoping, custom domains, or anonymous invocation;
• Native-proved blobs — object storage has no Native proof, snapshot, or lineage; a Cloud snapshot of a tenant does not include its objects, and restoring a tenant does not touch storage;
• storage durability beyond the backend’s — the filesystem backend is one directory on one host; the S3 backend inherits the store’s guarantees and speaks plain HTTP on loopback only;
• storage for data-plane keys, presigned URLs, bucket deletion, multipart or streaming uploads, pending-upload cleanup, or listing pagination;
• a user-management product — Cloud accounts have Argon2id password verifiers, 24-hour session tokens, and GET /v0/me, and nothing else: no magic link, no OAuth, no session refresh or revocation, no application-user identity;
• key rotation — a key is live or revoked; issuing a replacement and revoking the old one are two explicit calls with no overlap window managed by the Cloud;
• a durable control plane — control-plane state is a file-backed stand-in for the control Native instance;
• a lineage position of a running tenant — head reports visible_csn and root_digest only while asleep, from hyphae status --data-dir, which needs the directory lock; a running tenant’s head is a live probe;
• any latency, throughput, or cost figure. Performance statements require Native’s environment class and receipt rules; the Cloud has produced none;
• an SLA, uptime figure, or support commitment.

Third-party conduct

Named third-party platforms are prior art and scope boundaries, never adversaries. Cloud documentation states what the Cloud is and is not; it does not compare, rank, or characterize other products’ weaknesses.