The platform is a set of independent services, each doing one job. One failing does not stop the rest, each can be upgraded or scaled on its own, and a whole server can be built from another in one run, with or without internet.
Around 70 containers in the shipped configuration (a few optional): call engine, AI services, speech and voice models, SMS platform, fraud engine, billing, network management and more. Each has its own health check where it matters.
A watchdog restarts any container that turns unhealthy. After an update the platform tests itself and rolls back automatically if something critical fails.
An optional mode for a primary and a standby node. A small agent on each exchanges heartbeats and moves a virtual address on failure or on demand, so callers keep dialling the same address. Ask us to walk through it for your site.
Encrypted nightly database and knowledge-base backups, sent off the server, with scheduled restore drills that prove a backup works and point-in-time recovery for the AI database.
Written procedures for a database down, storage down, all AI providers down, a lost host and a lost site, with alarms when one has not been rehearsed lately.
Versioned database changes that can be undone, and upgrades that touch only what changed.
| Mode | How it works | The new server needs |
|---|---|---|
| Online | The platform is copied from a server you already run; images are downloaded and built on the new one. | Internet access |
| Offline | The images the source already runs are sent over SSH and loaded as they are; every start runs without pulling or building anything. | Docker only; no internet for the install |
| Offline bundle | A folder you carry on a disk: images, code, and secrets and data encrypted with a passphrase. A checker verifies every file before installing. | Docker only; no network path at all |
Upgrades use the same modes and send only the images that changed. Some features still need the internet while running (outside AI providers, SMS and email delivery); a fully isolated site uses the on-server models instead.
An offline bundle of about 74 images and 14 GB took roughly 26 minutes to write, 3 minutes to verify and about 40 minutes to install on a virtual machine with the internet blocked.
In the offline mode test, the new server's DNS and web ports were blocked and no download or build happened there.
Tell us whether the site can reach the internet. We will walk through the right mode and what to switch off for an isolated site.
Book a demo