LOCS / Deployment
Deployment

Customer-controlled, model-neutral, air-gap capable

Locs installs inside your environment and runs on infrastructure you control. It is model-neutral and integrates with your identity, knowledge and operations.

01
Profiles

Locs Core

Hardened container package for a single-environment deployment; installed by your ops team.

Enterprise Kubernetes

Stateless replicas plus a durable worker, suitable for customer clusters.

Azure Local-compatible

Architecture compatible with Azure Local / hybrid environments for Microsoft-heavy operators.

Connected private

Runs in your network with governed, signed update paths.

Air-gapped

No external connectivity required; updates and licences transfer offline as signed, verifiable files.

High availability

Durable PostgreSQL job queue (validated), stateless replicas and a worker entrypoint. Multi-replica physical failover is validated in the customer environment.

02
Data & runtimes
  • PostgreSQL + pgvector for governed knowledge and retrieval, RBAC enforced in-query.
  • Model-neutral runtimes — open-weight defaults or a customer-provided endpoint, behind a model-adapter layer. No lock-in.
  • Customer-managed infrastructure — you own the servers, storage, identity and model runtime.
03
Customer responsibilities

Locs is customer-operated by default. You provide and control the infrastructure, identity tenant, model runtime, knowledge sources and change processes. Onboarding validates identity, connectors, HA and restore in your environment before go-live. A shared-responsibility summary is included in the procurement pack.

Ready when you are

Design your deployment in a readiness assessment.

We produce a customer-specific architecture and deployment recommendation before any pilot commitment.