Cloud switching
Switch between hosted and self-hosted Cloud without guessing what moves.
Contextify connects each Mac to one cloud target at a time: hosted Contextify Cloud or a Contextify Cloud Self-Hosted server.
Switching the target changes where this Mac syncs next. It is not a server-to-server import.
Key point: switching targets does not delete your old hosted account, self-hosted account, self-hosted server, or data already stored on the old service.
From Self-Hosted to Contextify Cloud
When this Mac switches from a self-hosted server to hosted Contextify Cloud, Contextify starts the hosted Cloud sign-in handoff.
Use the email address you want for Contextify Cloud. It does not need to match the email address used on your self-hosted server.
If the hosted service does not already have an account or workspace for that email, Contextify Cloud may create one during authentication and email verification. After the Mac is connected, normal cloud sync can upload this Mac's eligible local Contextify history to the hosted service.
From Contextify Cloud to Self-Hosted
When this Mac switches from hosted Contextify Cloud to a self-hosted server, Contextify validates the self-hosted server URL and API key before replacing the saved hosted connection on this Mac.
After the Mac is connected, normal cloud sync can upload this Mac's eligible local Contextify history to the self-hosted service.
The self-hosted server controls its own users, roles, workspaces, API keys, network access, billing, and service settings. Those records do not come from hosted Contextify Cloud.
What carries over
Through this Mac's local sync
- Local Contextify history on this Mac that is eligible for cloud sync.
- Local projects, conversations, transcript entries, and associated synced metadata according to the normal sync settings and service limits for the target service.
- The device name you choose for this Mac is sent to the new target when the new connection is saved.
What does not carry over
Account and workspace state
- Account email identity.
- Workspace membership.
- Roles and permissions.
- Billing and subscription state.
- Other users on the old service.
Server and credential state
- Remote server configuration.
- Remote server-side records that are not present locally on this Mac.
- API keys and device authorizations.
- Service-specific settings, including self-hosted network and DNS configuration.
Switching back
The old service remains separate. If you switch back before saving, Contextify restores the current saved connection in the settings sheet.
After a new connection is saved, you may need to re-enter credentials for the previous service. The previous remote account or server data is still governed by that service.
Self-hosted DNS and TLS
For self-hosted servers, use the same hostname that the server's TLS certificate covers. If the server is reached through Tailscale MagicDNS or another VPN DNS system, macOS must be able to resolve that hostname for Contextify to connect.
If the browser can reach the public internet but Contextify cannot reach the self-hosted server, the internet connection itself is probably fine. Check the configured hostname, VPN status, DNS resolver state, port, and certificate name first.
Last updated: May 30, 2026