Where your data lives
Your engine runs on a dedicated server in its own isolated space — here's what that means.
Your Context Engine runs on a server — a computer in a data centre — that your hosting partner manages. On that server, your engine lives in its own isolated container: a sealed-off space with its own database and its own files, separate from anything else on the machine.
Isolated and single-tenant
If the server happens to host other customers' engines too, that makes no difference to you: each engine is walled off in its own container and can't see any other. Your data sits only inside your engine's space.
A stable address that follows you
Your engine has its own web address with automatic HTTPS encryption. If your partner ever needs to move your engine to a different server — for example, to recover from a hardware problem — that address moves with it, so your bookmark keeps working and you don't have to change anything.
Who controls the server?
The server is run by your hosting partner (or their chosen cloud provider, such as Hetzner or DigitalOcean). You can ask your partner:
- which provider and region your server is in (useful if you care about data residency), and
- where your backups are stored.
The short version
- Your data lives in one place: your engine's isolated container.
- It's not mixed with anyone else's.
- It's reachable at a stable, encrypted address that stays the same even if the engine moves.