Data residency for regulated industries
Self-hosted AI search and RAG: your content never leaves your network
A search SaaS asks you to trust its compliance badges with your content and your users' queries. Viglet Turing is self-hosted: the data never leaves your infrastructure, so security inherits the controls you already run. Open source, any LLM, your region.
Don't trust a vendor's boundary. Remove it
SOC 2 and GDPR paperwork exist because a hosted vendor holds your data. When you self-host, that boundary disappears: your content, embeddings and query logs stay inside the account, region and controls you already operate. Nothing is transferred, and nothing has to be audited on someone else's word.
How Turing keeps you in control
What the software does, and what you can check in its source.
Your data never leaves your network
Turing is self-hosted. Indexed content, embeddings and query logs live on your own infrastructure. No SaaS tier collects them and no telemetry phones home.
Data residency by construction
You run it, so your data stays in the region and account you already control. There is no data-processing addendum to negotiate and no cross-border transfer to reason about.
SSO & encrypted secrets
Put the admin console behind your identity provider over OIDC single sign-on (Keycloak-based). Provider API keys and credentials are stored encrypted at rest.
Keep even the LLM in-house
Run fully local models (Ollama) or an OpenAI-compatible endpoint inside your network, so prompts and content never reach a third-party model provider.
Auditable, open source
Every line is Apache 2.0. Your security team can read what it does, pin a version and build it themselves.
Small attack surface
CSRF protection, a read-only public search/chat surface with every write and admin endpoint behind authentication, and sandboxed (Docker) code execution and skills.
Data residency questions
What regulated teams ask before they put AI search over their content.
- Is there an AI agent platform that preserves data residency?
- Yes. Viglet Turing is self-hosted, so its search index, embeddings, agent conversations and query logs live in the infrastructure and region you deploy it to. Agents, tools, skills and MCP servers run inside that deployment, and an agent only reaches an outside service you configure it to call.
- Which LLM should a regulated industry use when data residency is required?
- Turing is not an inference provider; it lets you pick one per agent. Keep prompts in-house with a local model through Ollama or any OpenAI-compatible endpoint you host, or use a cloud provider you can pin to a region, such as AWS Bedrock or Google Vertex AI. Switching providers does not change where your content and index live.
- Can I run RAG and AI search without sending content to a vendor's cloud?
- Yes. Connectors index your content into Solr, Elasticsearch or an embedded Lucene index on your own servers, and retrieval, ranking and citations happen there. With a local model, nothing in the answer path leaves your network.
- Does Turing send telemetry or usage data back to Viglet?
- No. There is no telemetry and no phone-home. The code is Apache 2.0, so your security team can read it, pin a version and build it themselves.
- Does Turing have SOC 2 or GDPR certification?
- Turing is software you run, not a service we operate, so there is no hosted environment to certify. Deployed in your environment, it runs under the certifications, network controls and data-processing terms your infrastructure already carries.
What self-hosting means for your compliance
Turing is software you run, not a service we operate, so it has no SOC 2 report of its own to hand you, and it doesn't need one. Deployed inside your environment, it runs under the certifications, network controls, logging and data-residency guarantees your infrastructure already carries. You keep the audit trail; we keep the source open so your team can verify every claim on this page.
- Self-hosted under Apache 2.0
- Content, embeddings & query logs stay on-prem
- Bring your own LLM, or run fully local
- No telemetry, no phone-home