Platform

What runs. What we picked. What you can see.

The architecture in three views — the runtime capability map, the vendor map with alternatives, and the architect-facing surfaces that exist in the build today.

Engine Room

The runtime capability map.

Six layers, each doing one thing well. Operator on top, foundation on the bottom. Every layer ships with the platform · every layer is inherited by every solution.

A

Operator Experience

Cockpits, decision drawers, replay viewers, embedded chat.

B

Reasoning Core

Multi-provider LLMs with RAG. OpenAI, Anthropic, Mistral · switchable per call.

C

Orchestration

LangGraph TS. Typed graph state, checkpointing, replay.

D

Governance

Policies, approval gates, Decision Lineage, eval scorecards.

E

Tools & Connectors

MCP server. ERP / TMS adapters. Action catalog. Write-back hooks.

F

Identity & State

Auth, multi-tenancy, Postgres, sovereign deploy. Rebuildable from event log.

Tech Choices

What we picked. What else exists. Why.

Every layer is replaceable. The architecture bets on no single vendor — on the pattern, not the brand.

Reasoning models

OpenAIAnthropicMistral

Alternatives: Llama, Gemini, DeepSeek, Cohere

Multi-provider · switchable per-call · sovereign-LLM ready

Orchestration

LangGraph TS

Alternatives: CrewAI, AutoGen, raw tool loops

Typed graph state · checkpointing · TS-native

Retrieval

Pinecone

Alternatives: Weaviate, Qdrant, pgvector

Managed scale · one-adapter swap to self-hosted

Observability

LangSmith

Alternatives: Langfuse, Arize, OpenLLMetry

Trace + eval + dataset replay in one pane

Protocol

MCP

Alternatives: Custom tool registries, plain REST

Open standard · vendor-neutral · client-agnostic

Storage

Postgres

Alternatives: Snowflake, MongoDB, S3 + Parquet

Boring, durable, rebuildable from event log

Deploy

HPE GreenLakeNVIDIAAWS/Azure/GCP

Alternatives: Bare metal, K8s anywhere

Sovereign, hybrid, or public · customer's call

Frontend

Next.js + React + TS

Alternatives: Remix, SvelteKit

Boring on purpose · mature · server-rendered when it matters

Every layer is replaceable. We bet on the pattern, not the vendor.

Building Blocks Visible

The architect-facing surfaces that exist.

Not slides. Real screens, in the build, with real data flowing through them.

Live

Architect Hub

Agents, connectors, policies, RAG corpus, traces · the platform control surface.

Live

Decision Lineage

Click into the reasoning chain behind any decision · per-contract drill · trace · token cost.

Live

MCP Console

Live MCP tool surface · bearer auth · works with Claude Desktop, ChatGPT, Cursor.

Live

RAG Corpus

Browse embeddings · retrieval scores · source docs · re-index in one click.

Live

Traces

Every LangGraph run · every LLM call · every tool invocation · LangSmith integrated.

Live

Platform Health

Provider latency · error rates · eval scorecards · RAG hit ratios.

Two prongs

Co-build with us. Or adopt a live solution.

The platform consumes two ways. Both shipped on the same foundation. Both audited the same way.

Prong 01

Co-build

You bring the domain · the data · the policies. We bring the Engine Room, the MCP layer, the Decision Lineage scaffold. We ship the first solution together in 12 weeks. Same compounding reuse on the next.

  • Spec + data · week 0
  • First agent · weeks 1–3
  • Multi-agent flow · weeks 4–7
  • Operator cockpit · weeks 8–12
Prong 02

Pre-built solutions

Three live solutions to start. Each is operator-ready, MCP-wired, Decision Lineage instrumented. Configure for your data shape and policy registry. Production-grade in weeks, not quarters.

  • Commodity Desk · farm-to-port + ESG
  • Radix Treasury · cash · liquidity · hedge · recon
  • Exposure Management · counterparty + breach resolution
See live solutions