Your own Hub. Privacy by design.
Saiph Hosted is being built to connect your devices without a server for you to manage. The target is a dedicated Hub that relays content encrypted on your devices. This is a design preview, not an available service or a verified security guarantee.
GitHub access is currently limited to invited collaborators.
Your devices hold the content keys.
Signing in identifies your account. Adding a device that can decrypt content is a separate approval step. Paying for hosting must never approve a device or change its keys.
Encryption before relay
The design seals content separately for approved devices and signs messages with device keys. Hosted runtime and cryptography checks do not establish that every shipping app feature uses this path.
Dedicated deployment
Each customer is intended to have a separate Hub and database. Isolation, recovery and lifecycle operations must be verified before accepting customers.
Account metadata remains visible
Account identifiers, device public keys, subscription status and delivery metadata are needed to operate a relay. Encryption does not hide connection times or message sizes.
Device approval stays separate
An Auth0 account session or Stripe payment alone grants no access to content keys. A trusted device must approve additional devices.
Preparation is underway.
- Everyday app integration, real-device acceptance and independent security review remain required.
- Self-hosted features currently process readable content at your own Hub. Hosted encryption must not be inferred from those features.
- Public downloads, release verification, recovery and migration instructions remain release work.
- Price, supported regions, retention, cancellation and privacy terms will be published before launch.
- Company, payment-provider and legal readiness remain separate launch gates.