Introduction

Organizations are re-evaluating how and where critical systems run. Increased regulatory pressure, supply chain risk, and dependency on shared infrastructure have exposed weaknesses in traditional cloud models.

There is a broad shift toward greater control, clearer trust boundaries, and infrastructure that can be operated and validated end-to-end. This applies equally to public sector programs, regulated enterprises, and organizations handling sensitive or high-impact workloads.

ACRA is Valarian’s answer to these emerging challenges.

What Valarian Does

Valarian designs and builds secure, virtual infrastructure for organizations that need strong containment, auditability, and operational resilience.

Valarian’s platform, ACRA, provides a compartmentalised and tightly permissioned environment for running AI systems, communications, and custom applications. It is designed to support both regulated enterprise use cases and higher-assurance operational environments using the same underlying architecture. ACRA was hardened by first building and operating sensitive Valarian systems on the platform itself, using the same core components and subsystems made available to customers:

• AI execution and orchestration subsystem: Containerised LLM workloads running entirely within the enclave. Model execution, prompt handling, retrieval, and outputs remain contained, auditable, and under explicit policy control. No external calls and no vendor retraining.
• Isolated execution and resilience subsystems: Compartmentalised environments designed to preserve availability during incidents or infrastructure disruption. Enclaves can be suspended, relocated, or resumed without loss of data or security guarantees.
• Secure communications and collaboration subsystems: In-enclave chat, video, and file-sharing services built for sensitive coordination, with enforced access controls, encryption, and full auditability.

This approach ensured the platform was proven under real operational constraints before being exposed as a general execution environment.

Secure by Design Philosophy

Valarian systems are designed around failure scenarios rather than ideal operating conditions.

ACRA’s design reflects repeated exposure to infrastructure breakdowns where isolation weakens, auditing becomes unreliable, and access controls fail under pressure. Thus, all platform capabilities are designed to function in degraded, disconnected, or constrained environments.

Valarian’s design principles are consistent across the platform:

• Isolation first, not layered on
• Explicit permissions, default deny
• Containment over connectivity
• Auditability and visibility as a system property
• Operation without assumed connectivity

Every capability is built to function under degraded, disconnected, or hostile conditions.

Who the ACRA platform is for

• Defence and national security programmes
• Government and sovereign operators
• Regulated industries handling sensitive data
• Forward-deployed and mobile teams
• Organisations operating under cyber, physical, or geopolitical threat

If loss of control, availability, or auditability is unacceptable, the platform is designed for you.

What problems ACRA solves

Valarian addresses structural failures in modern infrastructure:

• Uncontrolled data egress from AI systems or malicious software
• Inability to enforce true workload isolation
• Dependency on external cloud services that lack built-in security
• Poor auditability and visibility
• Loss of availability during outages or attacks

These are systemic problems. ACRA is designed to remove them, not mitigate them after the fact.

What is ACRA

ACRA is Valarian’s secure execution platform for mission-critical workloads.

It provides a controlled environment where AI systems, communications, and custom applications can run with enforced isolation, explicit permissions, and full operational authority retained by the operator.

Secure Virtual Enclaves

ACRA is built around secure virtual enclaves as a first-class primitive.

An enclave is a complete application environment with:

• Controlled ingress and egress
• Strong identity and access boundaries
• Enforced separation between workloads
• Integrated auditing and observability

Enclaves are designed to be portable, reproducible, and disposable when required

Control Over Data, Execution, and Availability

Operators retain full control over:

• Where data is stored and processed
• Which models and services are allowed to run
• Who can access systems and under what conditions
• When and how systems operate, including offline

ACRA does not require external connectivity, vendor-managed services, or calls home. All critical capabilities operate within the defined trust boundary.

ACRA takes the opposite approach.

• Isolation is the default, not optional
• Communication is explicitly permitted, not assumed
• Auditability is built in, not bolted on
• Availability is preserved even when disconnected

Unlike hardware-only secure enclaves, ACRA extends these guarantees across full application environments, AI workflows, and operational systems.

The result is a sovereign, controllable platform designed for real-world risk, not ideal conditions.