AI Ingestion
The Gateway Model
The Parallel Ledger is a deterministic state machine, not a general-purpose API. It is designed to operate behind a Partner Gateway. This boundary separates the immutable ledger protocol from your specific business logic and external requirements.
The Functional Boundary
While the Ledger maintains data integrity and cryptographic proofs, the Gateway is where you implement Domain Logic. To ensure the Gateway can match the Ledger's native throughput and concurrency, we require this layer to be built in Elixir/OTP.
Partner Gateway (Elixir)
- • Request Validation & Normalization
- • Identity (OIDC) & mTLS Termination
- • OTP Supervision & Fault Recovery
- • Rate Limiting & gRPC Client Logic
Parallel Ledger (Core)
- • Deterministic State Transitions
- • Cryptographic Hashing & Witnessing
- • Immutable Event Sequencing
- • Concurrent Persistence
Implementation Support
We recognize the requirement for Elixir may represent a shift in your standard stack. To assist with implementation and optimization, we provide weekly on-site engineering sessions in Vancouver.
Downstream Integration
The Elixir requirement applies only to the Gateway (the direct relay to the Ledger). Downstream Extraction Layers—such as analytics engines, reporting tools, or legacy APIs—can be built in any language (Go, Rust, Java, etc.) that supports gRPC or REST.
Performance: Mechanical Sympathy
Using Elixir provides native compatibility with the Ledger's concurrency model. By using gRPC and Protobuf, the Gateway utilizes binary serialization to minimize CPU overhead and latency during high-velocity state updates.
Architectural Continuity
By keeping the Ledger's surface area minimal and standardizing the Gateway on a performant, concurrent runtime, we ensure long-term compatibility. This architecture allows your business logic to evolve within the Gateway while the underlying record remains stable.
The Gateway Model
The Parallel Ledger is a deterministic state machine, not a general-purpose API. It is designed to operate behind a Partner Gateway. This boundary separates the immutable ledger protocol from your specific business logic and external requirements.
The Functional Boundary
While the Ledger maintains data integrity and cryptographic proofs, the Gateway is where you implement Domain Logic. To ensure the Gateway can match the Ledger's native throughput and concurrency, we require this layer to be built in Elixir/OTP.
Partner Gateway (Elixir)
- • Request Validation & Normalization
- • Identity (OIDC) & mTLS Termination
- • OTP Supervision & Fault Recovery
- • Rate Limiting & gRPC Client Logic
Parallel Ledger (Core)
- • Deterministic State Transitions
- • Cryptographic Hashing & Witnessing
- • Immutable Event Sequencing
- • Concurrent Persistence
Implementation Support
We recognize the requirement for Elixir may represent a shift in your standard stack. To assist with implementation and optimization, we provide weekly on-site engineering sessions in Vancouver.
Downstream Integration
The Elixir requirement applies only to the Gateway (the direct relay to the Ledger). Downstream Extraction Layers—such as analytics engines, reporting tools, or legacy APIs—can be built in any language (Go, Rust, Java, etc.) that supports gRPC or REST.
Performance: Mechanical Sympathy
Using Elixir provides native compatibility with the Ledger's concurrency model. By using gRPC and Protobuf, the Gateway utilizes binary serialization to minimize CPU overhead and latency during high-velocity state updates.
Architectural Continuity
By keeping the Ledger's surface area minimal and standardizing the Gateway on a performant, concurrent runtime, we ensure long-term compatibility. This architecture allows your business logic to evolve within the Gateway while the underlying record remains stable.