Separate instances
One service per website. The strongest isolation; more to operate. Recommended where websites belong to different legal entities or carry different risk.
Secure Channel · deployment
Self-hosted, site by site.
Two documented installation choices, never silently mixed: separate site-isolated instances, or one hardened multi-tenant installation owned by the customer with separate namespaces and keys.
Multi-tenant, customer-owned
One installation for many websites of one organisation, with tenant boundaries in storage, APIs, keys, credentials, backups and restores. One compromised site must not expose another.
Installation
What a deployment consists of
- Reverse proxy with TLSOn the customer's own domain.
- Service and storageVisitor API, operator API, encrypted storage, audit log, maintenance jobs.
- Local widget bundleScript, styles, fonts and the attribution mark served from the customer's site. No iframe, script or stylesheet from the vendor domain.
- Staff accountsPhishing-resistant multi-factor authentication where feasible, roles, site-level permissions, session expiry, audit.
- Restore drillBackup restored and verified before the first visitor message.
Updates are signed packages the customer's administrator downloads and installs. Each release carries migration notes and a rollback procedure.
SOVEREIGN BY DESIGN.
Discuss a Secure Channel pilot
Tell us what you need to protect. A briefing is an engineering conversation; it never needs your credentials, network inventories or logs.