Varolio DocsDeployment Scenarios
How Varolio's components are arranged for each supported deployment model
Deployment scenarios
Varolio runs the same software in every deployment — the same services, the same data layer, the same AI surface. What changes between deployment models is how the components are arranged: what is multi-tenant versus dedicated, whose cloud account they live in, where the data stores run, and how the public surface is exposed.
The following scenarios are supported.
Cloud SaaS
Multi-tenant, operated entirely by Varolio, hosted on AWS in eu-central-1 (Frankfurt) — EU data
residency by default. Public surface: app.varolio.io.
Dedicated Cloud
Single-tenant, fully managed. A dedicated AWS account with no other tenants and no shared
services, in a region you choose (Canada validated in production). Public surface:
app.{region}.varolio.io.
BYO Data Store
Your data, your infrastructure. You host the data plane — Elasticsearch/OpenSearch, an LLM endpoint, S3-compatible object storage — and Varolio connects to it. Composes with Cloud SaaS or Dedicated Cloud.
Cloud-Prem
The full platform inside your own cloud account — AWS, GCP, or Azure — operated through a revocable identity you create. Data never leaves your account except HTTPS calls to AI providers.
At a glance
| Cloud SaaS | Dedicated Cloud | BYO Data Store | Cloud-Prem | |
|---|---|---|---|---|
| Tenancy | Multi-tenant | Single-tenant, dedicated | Follows base model (SaaS or Dedicated) | Single-tenant, dedicated |
| Cloud account | Varolio (shared) | Varolio (dedicated per customer) | Varolio app + customer-hosted data stores | Customer's own |
| Region | EU (Frankfurt) default | Customer's choice | Data stores: wherever the customer hosts them | Customer's choice |
| Cloud vendor | AWS + GCP | AWS + GCP | Any (ES-compatible / LLM endpoint / S3-compatible) | AWS, GCP, or Azure |
| Data stores | Varolio-managed | Varolio-managed, dedicated | Customer-hosted | Customer's account |
| Operated by | Varolio | Varolio | Varolio (app) / customer (data stores) | Varolio, via revocable identity |
| Cloud bill | Included in subscription | Included in subscription | Data-store costs direct to customer | Direct to customer |
| Best for | Fast onboarding, EU residency | Isolation + residency requirements | Data-sovereignty over content and search | Strictest sovereignty, own-cloud policies |
The component-level description that all scenarios share lives on the Application Architecture page. What data enters and leaves the platform is documented on the Data Flow page, and the controls applied at every layer on the Security page.