Intent · private-deployment

Private Deployment & Security Boundaries

Data staying within your perimeter is default, not an add-on. From single-node PoC to air-gapped data centers, ReadyForAI is engineered natively for private environments.

Data Must Not Leave PerimeterStrict Compliance Audit DemandsDeployment Cost AssessmentMandatory Security Reviews
CONFIDENCE90%
Single-Node PoC1 Day

Docker standalone rollout; 4C / 8G resources run the entire full-stack loop

Production Cluster1–2 Weeks

Kubernetes deployment with independent component autoscaling

Air-Gapped Data CenterSupported

Offline container image import · audited private LLM egress · local verification

Zero Outbound Data

All runtime events, audit logs, and knowledge graphs remain strictly inside your environment

Private LLM Inference

Supports private on-prem models; external LLM gateways are audited and severable on demand

Secret Isolation

Secrets managed via File / Env; never injected into prompt contexts. Vault / HSM / Cloud KMS backends not yet integrated

Local Audit Persistence

Committed records enter Hash Chains, locally verifiable with gap detection

Ingest Gate and Protected Procedures

LarkScout's ingest gate includes archive structural safety and process-isolated YARA (scanner binary required); SOPs and SKILLs may declare protected sections whose declared spans are digest-checked on fork

Runtime EnvironmentDocker / Kubernetes · Offline container image import
Minimum Resources4C / 8G baseline; runs all components on single node
StorageSQLite on the substrate · PostgreSQL 16 for the governance suite
NetworkingFully air-gapped supported · Optional LLM egress
UpgradesRolling image import · local verification
IdentityEnterprise IdP / OIDC · optional local emergency admin
SYSTEM READYintent/private-deployment