Mobile Origin Transaction Router
Sold once. One buyer acquires the complete IP outright — every line of source, every test, every audit artefact — and it is then denied to every other party. No licence, no recurring, no second buyer.
Acquire — begin due diligence →Technical Ledger
| SKU | VLA-GEN-MOB-V1.0 |
|---|---|
| Vendor | Vlaander LTD |
| Classification | Engineering Asset |
| Variant | Default Title |
| Availability | ProvisionedPASSING |
Provenance & integrity.
| Language | Elixir 1.16 · Rust · C++ |
|---|---|
| Runtime | BEAM · OTP supervision tree |
| Build | mix · Credo · Dialyzer · sanitizers in CI |
| Formal verification | 3 machine-checked TLA+ specs (ingest · routing · hedging)PASSING |
| Concurrency | lock-free MPSC ring · property-proven treasuryPASSING |
| Memory safety | Rust NIF · constant-time HMACPASSING |
| Durability | group-commit WAL · no-drop provenPASSING |
| Signing scheme | ed25519 signed releases |
| Signing key | Publishing 2026-Q3 |
| SHA-256 | Publishing 2026-Q3 |
| Release | Publishing 2026-Q3 |
| External audit | Publishing 2026-Q3 |
Value, in your metrics.
| Metric you track | Magnitude |
|---|---|
| Last-mile margin | Five lines of bps — interchange, FX, crypto spread, float, payout — captured per settled intent instead of ceded to a third-party PSP. |
| Dropped-intent rate under burst | Zero by construction: once acknowledged, every intent is WAL-durable and replayable (TLA+-proven no-drop). |
| Webhook ACK latency | p99 under 50ms; ~210K verify+parse+hash operations/sec per core, scaling linearly with schedulers. |
| Cross-rail double-settle risk | Structurally refused — a timed-out settlement cannot reroute (TLA+-proven at-most-one-success). |
| Treasury hedging discipline | Net-position epoch hedging: one order per currency per flush, not per intent — the execution-desk standard. |
Build-vs-buy basis.
Reproducing this in-house: approximately 36–66 engineer-months for a senior team familiar with high-concurrency BEAM payments systems, native NIF hot paths, and TLA+-verified settlement routing. At a loaded cost of $25,000 per engineer-month, that is $900,000–$1,650,000, or $2,227,500 after a 35% risk premium for scope overrun. Purchasing the source: $850,000 plus approximately 6 weeks of integration effort. Stated biases: we compare against the high end of the build estimate, apply a 35% risk premium for scope overrun, and exclude opportunity cost. Editable assumptions: engineer-months (36–66), loaded cost per month ($25,000), risk premium (35%). Flip any of these and the comparison adjusts accordingly — the model is yours to defend, not ours to dictate.
Risk allocation.
| Risk | Borne by | Basis | Buyer’s recourse |
|---|---|---|---|
| IP cleanliness | Vlaander LTD | Source warranted as original work, clean of third-party IP at point of sale. | Indemnification capped at the purchase price paid. |
| Benchmark performance | Vlaander LTD | Published numbers must reproduce on the documented hardware. 30-day inspection window from delivery. | Refund of the purchase price within the inspection window. |
| Integration into buyer’s stack | Buyer | Integration footprint published on every product page. No warranty extends to bespoke environments outside the documented targets. | Use the published footprint as the integration spec; engage Vlaander engineering at sales@vlaander.com for paid support. |
| Regulatory compliance in buyer’s jurisdiction | Buyer | Export classified EAR99. Buyer self-screens against restricted jurisdictions and parties under their own legal counsel. | Request a pre-sale export review at sales@vlaander.com — provided at no charge. |
| Vendor continuity | Buyer | No vendor can warrant its own continuation. Source delivered without licence server, kill-switch, or expiry — risk transferred to buyer by the outright-sale model. | Self-maintain in perpetuity using the delivered source; fork freely under the Sale terms. |
| Source-code escrow | Joint | Source is delivered to the buyer at sale, so escrow is structurally unnecessary. Available on request when buyer counsel mandates a third-party deposit. | Request escrow at sales@vlaander.com — buyer-funded; Vlaander participates without charge. |
| Security disclosure post-sale | Joint | Vlaander acknowledges security reports within 24 hours and honours coordinated disclosure indefinitely on shipped versions. Buyer applies remediation in their environment. | Report to sales@vlaander.com — disclosure policy published at /security. |
Scope & maturity.
- The router and margin-capture core: ingest, multi-rail routing, per-currency treasury, net-position hedging, pre-dispatch compliance, and five-line bps attribution.
- Three independent TLA+ specifications — ingest, routing, hedging — TLC model-checked.
- The native hot path: a Rust NIF (HMAC + simd-json + BLAKE3) and a lock-free C++ MPSC ring buffer.
- The operational surface: 24 telemetry metrics, twelve SLOs with burn-rate alerts, and supervision-tree self-healing.
- Venue-specific endpoints — settlement adapters, quote sources, hedge venues, compliance screens — are wired by the operator behind well-scoped behaviours.
- v1.2 is the router and margin core; adapters ship with mock and reference implementations for tests and benchmarks.
- WAL-persisted margin records, a custodian reconciler for settlement-uncertain intents, and real fuzzy OFAC matching (v1.3).
- IVMS 101 Travel Rule protocol, NIBSS name-enquiry pre-step, speculative parallel rail dispatch, and hedge cancellation (v1.3).
System Abstract
A high-concurrency stablecoin payments rail engineered never to drop an intent. As stablecoins scale into retail, payment aggregators face tens of thousands of simultaneous webhook calls from chat-bots and dynamic QR scanners in unpredictable bursts — a workload standard Node and Python stacks choke on, silently dropping payment intents. MOTR's TLA+-proven ingest core guarantees that once an intent is acknowledged, it is durable on disk and replayable.
Above ingest, MOTR turns the router from a passthrough into a principal counterparty: every settled intent emits a five-line bps margin record — interchange, FX spread, crypto spread, float value, and payout FX — so the operator captures the margin a third-party PSP would otherwise take at the last mile. Multi-rail settlement routing with per-currency treasury, net-position epoch hedging, and a pre-dispatch compliance gate sit behind well-scoped behaviours the operator wires to venue-specific endpoints.
The stack is chosen deliberately: BEAM (Elixir/OTP) where concurrency matters, native Rust and C++ hot paths where cycles matter, pure functions where decisions matter, TLA+ where correctness matters — three independent specifications cover ingest, routing, and hedging. Delivered as source: the v1.2 router and margin-capture core.