v4.2 — Lattice expansion · 12 new regions live
Operating since 2023
SOC 2 · ISO 27001 · HIPAA

A computing
substrate for what comes next.

Pyroxa is a continental fabric for software that thinks — deterministic by design, observable to the millisecond, and built to be reasoned about before it ships.

Request access Read the manifesto private beta · cohort 04
Edge resolve38ms
Throughput1.42M/s
Coherence / 90d99.998%
Live regions42
Quietly underneath the work of 1,400+ teams
/ 01 — Runtime
primitive: signal()
The runtime

One surface, every signal, every shore.

A small, ruthless API. Intent goes in, behaviour comes out, the path between is yours to shape. The runtime adapts to the load before the load adapts to you.

  • Soft fall-through. When a path goes dark, the next one is already warm. Continuity in single-digit milliseconds, not seconds.
  • Memory that compresses. Recurring intent collapses into a single resolved shape — the lattice remembers, the bill doesn't grow.
  • Reversible by default. Every decision the system made is replayable, diffable, and refusable. Nothing is final until you say so.
  • Shape-checked surface. Inputs and outputs hold their shape; drift surfaces as a warning, not an outage at 03:00.
~/lattice/cohort-04 · pyroxa.live
stream trace replay drift
/ 02 — Topology
42 regions · perpetually warm
The mesh

A continent
of warm silicon.

Routing happens beneath the network, not on top of it. The map below is live — every pulse is a request that resolved in the last 600 milliseconds. Nothing here is rendered for the demo.

signals / sec
edge resolve
memory hit
primary warm replica edge cache
/ 03 — Platform
23 primitives
The platform

Every primitive your agent needs.

A small, considered surface. Each piece earns its place. Built by people who got tired of stapling six SaaS together and calling it architecture.

/ drift

Continuous truth-checks against the live world.

A candidate behaviour runs in the shadow of production. The system scores it against reality, on your rubric, and tells you when it's better — not when it's loud.

DRIFT.HARNESSv2.1 →
/ policy

Rules that compile.

Write what's allowed in plain types. The lattice lifts it to something that runs in 1.2ms at the edge of the world.

POLICY.WASM
/ memory

Federated recall.

Many memory stores, one shape. Hybrid rerank lives at the edge, not in your hot path.

RECALL.UNION
/ traces

Observability, finally honest.

Every decision is a span. Every span is replayable. The dashboard answers questions — it doesn't ask them.

OTEL.NATIVE
/ vault

Sealed keys.

Your secrets, our hardware. Rotate without redeploying. Every decryption leaves a paper trail.

VAULT.HSM
/ replay

Time-travel, plainly.

Take any moment from production. Run it through a different shape of the system. Compare. Choose. Ship the one that won.

REPLAY.SDK
/ scheduler

Demand-shaped capacity.

The lattice learns the rhythm of your traffic and schedules itself against the cheapest substrate that still keeps its word. Up to 64% less, asked or not.

SCHED.AUTOPILOT
/ 04 — Manifesto
written 2023, still true
A position

Software is becoming a signal,
not a stack.

For four decades we shipped pages, then services, then containers. The next decade ships behaviour. Behaviour is harder — it drifts, it argues with itself, it forgets. Pyroxa is the substrate underneath: a continent-scale fabric where intent travels at the speed of light, decisions are reversible, and observability is not an afterthought stapled to the side.

/ 05 — Questions
Frequently asked

The fine print.

Couldn't find what you need? Email a human →

What, exactly, is Pyroxa?
A substrate. Where most platforms hand you a tool, Pyroxa hands you a fabric — a continent of warm capacity that resolves intent into behaviour, deterministically, with the receipts to prove it. Think of it as the layer between your idea and the world.
Who is it for?
Teams shipping software that has to be right when no one is looking. Builders who'd rather understand their system than apologise for it. People allergic to dashboards that lie.
Where does my data live?
Wherever you tell it to. Pyroxa pins behaviour to a region, encrypts in flight, and forgets on schedule. Independently audited, the report is one click from your console.
Can I run Pyroxa in my own cloud?
Yes — partner customers get a Helm chart that brings the data plane into their VPC while the control plane stays managed. Common pattern for regulated workloads.
What does access look like today?
Private beta, cohort-based. We onboard a small group every six weeks so we can sit beside the work, not behind a ticket queue. Apply for the next cohort and we'll be in touch within a week.
What happens when a region goes dark?
The next one is already warm. The hand-off is measured in milliseconds. Your application doesn't know it happened — only the post-mortem does.
lattice online · 42 regions

Build the thinking part.
We'll hold the rest.

Request access Read the manifesto
cohort 04 opens may 2026 · 12 spots