AI Ingestion
Deployment Environment
The Parallel Ledger is an Independent Build. It is not a cloud service; it is a binary the organization owns and operates within their private perimeter. This ensures that the hardware, data, and cryptographic keys remain under the absolute control of the institution and the oversight of the National Five Partner.
The Standard: Virtualized Isolation (LXC)
We have standardized on LXC (Linux Containers) for primary deployment. This allows the appliance to interface with the host kernel and disk with near-native performance, avoiding the I/O tax of traditional virtualization.
-
01
Host OS Debian 13 (Stable) provides the foundation for long-term security and binary compatibility.
-
02
Isolation LXC (Preferred) or Bare-Metal Debian. We specifically advise against Docker to ensure stateful permanence and direct memory management.
-
03
Storage Architecture Local ZFS or NVMe-backed storage is required for low-latency write-ahead logging and high-frequency signing.
The Core Stack
The appliance is delivered as a singular, pre-compiled release. Implementation teams are not required to manage external dependencies, eliminating "dependency drift" across client environments.
-
01
Persistence Layer PostgreSQL 17. We utilize advanced indexing to support high-speed bitemporal queries and massive data density.
-
02
Runtime Environment Elixir 1.19 / Erlang OTP 27.2. The release is bundled with the runtime to ensure deterministic execution.
-
03
Network Signature Internal VPC restricted. The appliance exposes gRPC and REST endpoints for private ingestion and verification.
The Deployment Workflow
The setup process is designed to be predictable, facilitating a standardized "Golden Image" for an National Five Partner’s global practice.
-
01
Resource Allocation Minimum of 4 vCPUs and 16GB of RAM for standard production nodes to ensure BEAM concurrency.
-
02
Schema & Release The signed tarball is unpacked; the appliance manages its own migrations upon first boot for structure integrity.
-
03
License Activation A cryptographically sealed license key is injected to unlock throughput tiers and Sovereign capability sets.
Architectural Trade-offs
Choosing a private deployment over a managed cloud service involves a fundamental strategic shift toward total data authority.
-
01
Absolute Authority Control over backups and hardware redundancy with no external "backdoor" or vendor access.
-
02
Predictable Performance Hardware-grade signing speeds that do not fluctuate based on the shared load of a public cloud provider.
-
03
Air-Gapped Readiness Designed for restricted environments; the appliance functions without external telemetry to verify facts or execute logic.
Deployment Environment
The Parallel Ledger is an Independent Build. It is not a cloud service; it is a binary the organization owns and operates within their private perimeter. This ensures that the hardware, data, and cryptographic keys remain under the absolute control of the institution and the oversight of the National Five Partner.
The Standard: Virtualized Isolation (LXC)
We have standardized on LXC (Linux Containers) for primary deployment. This allows the appliance to interface with the host kernel and disk with near-native performance, avoiding the I/O tax of traditional virtualization.
-
01
Host OS Debian 13 (Stable) provides the foundation for long-term security and binary compatibility.
-
02
Isolation LXC (Preferred) or Bare-Metal Debian. We specifically advise against Docker to ensure stateful permanence and direct memory management.
-
03
Storage Architecture Local ZFS or NVMe-backed storage is required for low-latency write-ahead logging and high-frequency signing.
The Core Stack
The appliance is delivered as a singular, pre-compiled release. Implementation teams are not required to manage external dependencies, eliminating "dependency drift" across client environments.
-
01
Persistence Layer PostgreSQL 17. We utilize advanced indexing to support high-speed bitemporal queries and massive data density.
-
02
Runtime Environment Elixir 1.19 / Erlang OTP 27.2. The release is bundled with the runtime to ensure deterministic execution.
-
03
Network Signature Internal VPC restricted. The appliance exposes gRPC and REST endpoints for private ingestion and verification.
The Deployment Workflow
The setup process is designed to be predictable, facilitating a standardized "Golden Image" for an National Five Partner’s global practice.
-
01
Resource Allocation Minimum of 4 vCPUs and 16GB of RAM for standard production nodes to ensure BEAM concurrency.
-
02
Schema & Release The signed tarball is unpacked; the appliance manages its own migrations upon first boot for structure integrity.
-
03
License Activation A cryptographically sealed license key is injected to unlock throughput tiers and Sovereign capability sets.
Architectural Trade-offs
Choosing a private deployment over a managed cloud service involves a fundamental strategic shift toward total data authority.
-
01
Absolute Authority Control over backups and hardware redundancy with no external "backdoor" or vendor access.
-
02
Predictable Performance Hardware-grade signing speeds that do not fluctuate based on the shared load of a public cloud provider.
-
03
Air-Gapped Readiness Designed for restricted environments; the appliance functions without external telemetry to verify facts or execute logic.