Platform Architecture

A layered stack with no single point of failure

Axiom Trade's architecture follows a strict separation of concerns: a thin presentation layer that knows nothing about keys, a session-wallet layer that holds short-lived signing authority delegated by the user, an execution layer that turns intent into signed Solana transactions, and a data layer that turns the chain back into a clean stream of fills, balances, and PnL. Each layer can be replaced or hardened without touching the others, which is why we can ship execution upgrades on a weekly cadence without ever migrating user funds.

The application layer

The web client is a TanStack Start application with server-side rendering, served from a global edge network. Every interactive surface — Pulse, Discover, the trade widget, Portfolio — fetches data through a single typed RPC layer, which means a route change never re-implements an API call and a backend change ripples through the UI with a single contract update. The client is intentionally stateless about money: it knows what to sign, never how to spend.

The Solana base layer

All spot trading and most discovery features run directly on Solana. We submit through a fleet of geographically distributed validators with leader-aware routing — when a known sandwich-prone leader is up next, the router automatically prefers a private path. Block confirmation latency from the user's click to a finalized fill is consistently under one second for standard memecoin trades, and under two seconds for large-slippage routes that require Jupiter aggregation across multiple pools.

Turnkey-backed session wallets

Keys live in Turnkey's MPC infrastructure with hardware-backed enclaves. The user authorizes a session wallet with a clear, time-bound policy — for example, "can sign Solana token swaps up to $X per transaction for the next 8 hours" — and Axiom can submit signed transactions inside that envelope without ever seeing the key material. Revoking a session is a single click; it propagates in under a second. If our infrastructure is fully compromised, the attacker still cannot move funds outside the policy the user already signed.

Hyperliquid for perpetuals

Perpetual futures clear on Hyperliquid, a high-performance on-chain order book with sub-second matching and deep liquidity in the markets memecoin traders care about. Axiom acts as the front end: order intent is signed locally, routed to the venue, and the resulting position is streamed back into a unified portfolio view that fuses spot, perps, and farming positions into one PnL number with proper cost basis.

Jito bundles and private mempool routing

Three execution paths are available on every trade: public submission for speed, Jito bundle routing for sandwich resistance with a small tip, and private mempool routing for size-sensitive trades. The router picks a sensible default per market and per size; the user can override at any time. Every fill carries metadata about which path was used and what tip was paid, so the cost of protection is never invisible.

Data plane: the unified event store

Every signed transaction, every fill, every funding payment, every airdrop, and every fee is captured into a single append-only event store keyed by the user's wallet. PnL, position state, and the entire Portfolio view are derived from this store with strict cost-basis accounting. The same store powers our webhook system, our CSV exports for tax purposes, and the Trader Scan analytics that surface profitable wallets to follow.

Observability and safety nets

Every layer publishes structured metrics: signing latency, bundle inclusion rate, RPC error rate per leader, route-mix per market. The team is paged on anomalies that affect execution quality, not just uptime — a 200ms regression in median fill latency is treated as an incident. Circuit breakers automatically degrade non-critical features (notifications, deep analytics) under load so that signing and submission stay healthy.

What this means for you

You get the responsiveness of a centralized exchange, the custody guarantees of self-hosted keys, and a level of execution transparency that's almost unheard of in retail trading. The architecture is the product — and the next time someone tells you "non-custodial is slow," you can show them the fill timestamps.