01
Resume, don’t restart
Reconnect to durable terminal state and replay ordered output after a network or device transition.
Secure terminal continuity · PreviewYour terminal,
Your terminal,
uninterrupted.
Move between your desk and mobile without moving the shell. Continuum is building one encrypted, resumable terminal timeline across your trusted devices.
Endpoint-held keysOpen protocolsNo analytics trackers
continuum / workspaces / api-server
❯ cargo test --workspace
Compiling continuum-crypto v0.1.0
Compiling terminal-agent v0.1.0
test result: ok. 48 passed
# session resumed on mobile · 12ms
❯ git status --short
M packages/protocol/src/lib.rs
❯
❯ cargo test --workspace
Compiling continuum-crypto v0.1.0
Compiling terminal-agent v0.1.0
test result: ok. 48 passed
# session resumed on mobile · 12ms
❯ git status --short
M packages/protocol/src/lib.rs
❯
One shell. Every screen.
Continuity without surrendering control.
The host remains authoritative. Clients render and control an authenticated session instead of cloning a shell.
02
Designed for opaque relay
The cloud routes bounded encrypted records. The architecture keeps plaintext and session content keys at trusted endpoints.
03
Explicit device trust
New devices generate their identity locally and require approval with a human-verifiable fingerprint.
The continuity loop
From laptop to pocket in three deliberate steps.
- Run at the source.
A Rust host agent owns the PTY and durable transcript. - Synchronize encrypted state.
Authenticated records move through a content-blind control plane. - Resume on a trusted client.
A paired endpoint validates, decrypts and renders in order.
Built for operational realityNetworks fail.
Networks fail.
Your context shouldn’t.
Durable checkpoints, idempotent encrypted record uploads and replay windows are foundations—not marketing patches.
Current status: local Linux terminal and cryptographic/cloud foundations exist. End-to-end remote control and cross-client interoperability are not production-approved yet.
Platform
Native where identity matters.
Client keys live in the native app boundary. The website never asks you to downgrade that model.
Linux
Build available · preview
Build available · preview
Android
Build available · preview
Build available · preview
macOS & iOS
Runner foundation · not released
Runner foundation · not released
Windows
Runner foundation · not released
Runner foundation · not released
Trust by construction
The relay should not need your terminal content.
Continuum composes established primitives: X25519, Ed25519, HKDF-SHA-256 and XChaCha20-Poly1305. Private device keys and plaintext are excluded from the cloud contract.
Read the security posture✓ Public-key device packages
Signed package metadata binds device identities and versions.
✓ Short-lived authorization
Rotating refresh families, device revocation and explicit pairing approval.
△ Review still required
Not independently audited. Rotation, revocation and complete client interoperability remain release blockers.
Draft pricing
Start free. Scale when the product is ready.
These USD prices are planning figures, not a live offer. Checkout is intentionally disabled until billing and release terms are approved.
No card is collected. Account creation hands off to the native app. Taxes and regional pricing are not yet defined.
FAQ
Clear answers, including the caveats.
Is Continuum generally available?
No. It is a pre-release project. Local Linux PTY functionality and major cloud/crypto foundations exist, but remote viewing/input demonstrations have not passed.
Can the cloud read my terminal?
The intended and implemented cloud storage/relay contracts accept opaque encrypted records, not plaintext. This claim still needs complete cross-client integration and independent review.
Why can’t I finish signup in the browser?
The account’s first device must create a compatible Ed25519/X25519 identity package. Browser keystores do not portably provide the required production-grade, non-exportable key identity, so the native client owns that step.
Is pricing final?
No. Displayed tiers are centrally configured draft USD planning values. There is no checkout and no billing credential in this site.
Which platforms work today?
Linux and Android build evidence exists. Other native runner foundations exist, but public signed downloads and full remote interoperability are pending.
Where can I report a security issue?
Email the private security contact listed on the security page. Please do not include secrets or terminal content.
Begin deliberately
Keep your flow across devices.
Start the account handoff now, then let the native app establish your first trusted device.