Some of our workloads can never leave our tenancy. Can you deploy in our VPC or on-premises?

The full executive answer

Straight answer: no — today Vouli IQ is multi-tenant SaaS only, and I will not pretend a self-hosted edition exists. But let me lay out the actual spectrum, because the architecture supports more of it than the headline suggests. The deployment isolation path that exists by design is the cell model: a dedicated single-tenant cell — your own database instance, your own region — is a provisioning act on the existing codebase, not a fork. That gets you data isolation at the infrastructure level while we operate the software; it is the pattern most enterprise SaaS has converged on in place of on-prem.

For a true in-your-tenancy requirement, the honest technical assessment: the stack is unusually portable for a SaaS — standard Next.js compute, standard Postgres, standards-based auth — so a customer-tenancy deployment is not architecturally absurd. What makes it a roadmap decision rather than a promise is the operational reality every solutions architect knows: a self-hosted edition is a second product — release channels, upgrade paths, support tooling — and committing to it prematurely, pre-launch, would be exactly the kind of claim this platform is built to refuse. It is demand-priced: a signed enterprise commitment could fund it.

One more honest wrinkle for your data-flow diagram: even in a dedicated cell, AI processing calls Anthropic and OpenAI as subprocessors — with PII redacted from text before any model call. A fully air-gapped deployment would additionally require a self-hosted model strategy, which is a materially different product tier. I would rather scope that with your architects openly than wave at it in a demo.