Roadmap

Where Axiru is going. And how fast.

Money-path infrastructure deserves a visible trajectory. This is the public-safe view of the internal plan: the 90-day cross-rail governance plan (twelve milestones, target completion August 11, 2026 (day 90)) plus the new stablecoin-controls phase committed in July. Last reviewed July 5, 2026.

See how it works →
Status snapshot

9 shipped. 2 in flight. 4 next.

Updated as PRs merge. The internal plan is in the repo; this is the customer-facing summary.

9 shipped

Foundation, Decision Engine v2, DAA shadow adapter, JWKS, x402 pre-authorization (live, signed allow tokens, fail closed) + conformance, marketing surfaces, the rotation-rehearsal driver, and the new financial ontology + governed actions registry are all live in production or staging.

2 in flight

Cross-rail dashboard surfaces (M9) and stablecoin reconciliation persistence + policy packs (S2) are the active workstreams.

4 next

Design-partner review, Privy round-trip, first customer flipped to enforcing on DAA, Phase-1 success criteria, and stablecoin policy packs with examiner evidence.

Milestones

The 12-milestone plan

Each milestone has a definition-of-done. We update status here when the corresponding PRs merge.

M1

OVT type system + v2 policy schema

Rail-agnostic Outbound Value Transfer types ship; v2 policies compile alongside v1 with no breaking changes. Golden tests green.

Week 2

Shipped
M2

DB migration v1 → v2

Four new columns, three concurrent indexes, idempotent backfill. Migration deployed to staging without downtime.

Week 2

Shipped
M3

Decision Engine v2: pure-function rewrite

`evaluate(ovt, policies, context)` replaces six legacy event-specific evaluators behind a flag. Replay golden tests green across all six rails.

Week 4

Shipped
M4

Stripe DAA adapter (shadow mode)

DAA webhook ingress live, events normalized into OVT shape, surfacing in the decision ledger with `rail='stripe_daa'`. No enforcement yet.

Week 5

Shipped
M5

Design-partner technical review

Hard gate. Slide deck + live walk-through with design partners; feedback log triaged before enforcement-facing features ship. The original June window moved while the stablecoin-controls scope (below) was locked in; the review now covers both phases.

Rescheduled · new window being set with design partners

Next
M6

Ed25519 token issuance + JWKS

Tokens minted on Allow, JWKS endpoint cacheable, verifier passes 100% of conformance suite. Real JWKS + rotation tooling live.

Week 7

Shipped
M7

@axiru/x402-policy-middleware

TS + Go verifiers landed with shared conformance suite. Demo against Stripe-documented USDC-on-Base flow exercises five scenarios end-to-end including fail-closed engine/signer paths plus downstream token verification (T-040/T-041 merged).

Week 8

Shipped
M8

Privy Pre-Authorization integration

One x402 round-trip through Privy in a sandbox tenant; fail-closed verified end-to-end. Adapter is scaffolded and fail-closed today; awaiting partner credentials.

Week 9

Next
M9

Cross-rail dashboard surfaces

Ops dashboard already surfaces the v1-vs-v2 shadow agreement rate (with the explicit M11 cutover gate) and the quarantine queue. Remaining: ledger view filter by rail, approval-queue rail badge, three Stripe DAA policy templates installable from the dashboard.

Week 10 · partially landed

In flight
M10

/agentic-payments + pricing copy live in prod

Marketing surfaces for cross-rail governance are live. Demo embeds work on mobile + desktop. Pricing copy reflects rail-agnostic pricing model.

Week 11 (ahead of schedule)

Shipped
M11

First customer flipped to enforcing on DAA

Real Stripe DAA traffic running through the engine in enforcing mode. Seven days without rollback before declaring success.

Week 12

Next
M12

Phase-1 success criteria

Spec §1 acceptance bullets all green; security review signed off; key-rotation rehearsal complete (rehearsal driver landed Week 11).

Week 13

Next
New scope · July 2026

Stablecoin controls + the financial ontology

Committed July 1: Axiru extends to enterprise stablecoin operations (Solana-first) as a second rail, built on a governed action layer where humans and AI agents propose, policy evaluates, and every decision seals into the evidence ledger. Originally a 12-to-24-month horizon; the GENIUS Act and Open Standard (the 140-company consortium behind Open USD, issuing natively on Solana) pulled it into the active plan. USDC support is live for early-access orgs today; OUSD support lands at issuance.

S0

Foundation: financial ontology + governed actions registry

@axiru/ontology v0 (typed, tenancy-guarded object model with sensitivity tags) and @axiru/actions v0: a declarative, versioned Action Type registry with 13 governed verbs plus the migrated Stripe verbs. Agent-initiated actions are staged by default (propose → review → execute) with graduated autonomy per action type. A CI ratchet now fails any new write path outside the registry.

July 1, 2026

Shipped
S1

Stablecoin rail: Solana ingestion + decision path

Shipped: Solana SPL transfer ingestion (CPI-aware, Token-2022, resumable), the chain-vs-books reconciliation matcher with typed exceptions, and the usdc_solana rail ACTIVE in the decision engine. Pre-execution USDC transfer decisions are live on POST /api/v1/decisions for early-access orgs, with rail-scoped policies, velocity limits, and hash-chained audit. USDC shipped first; Open USD (OUSD) support lands at issuance. Open Standard launched June 30 with native issuance on Solana, the integration path this rail was built for.

July 5, 2026

Shipped
S2

Reconciliation persistence + stablecoin policy packs

Wiring ingestion → reconciliation → the evidence ledger (nightly + on-demand runs; reconciliation exceptions that suspend agent autonomy), GENIUS-Act-aligned policy packs, agent attribution on every evidence record, and exportable examiner bundles for enterprise stablecoin operations.

July 2026

In flight
Recently landed

Changelog: recent highlights

The shorter changelog. Customer-visible work only.

July 5, 2026

USDC-on-Solana rail activated + public API transfer decisions

usdc_solana promoted to an active rail in the decision engine, and POST /api/v1/decisions now accepts stablecoin transfer intents for early-access orgs: rail-scoped v2 policies, velocity limits over prior authorizations, org kill-switch parity, and every decision hash-chained with the canonical transfer fingerprint. Exact 6-decimal amounts end to end.

July 4, 2026

Solana ingestion + chain-vs-books reconciliation engine

@axiru/rails-solana (SPL transfer ingestion: CPI-aware, Token-2022, resumable pagination) and the reconciliation matcher: signature-anchored matching with amount verification, deterministic amount+time fallback, and typed exceptions. Unknown-wallet detection fires even on matched transfers, the payout-redirect fraud shape.

July 3, 2026

Cross-rail hardening batch

Velocity limits on agent pre-authorizations now evaluate real rolling-window spend aggregates (fail-closed to approval when unavailable), refund execution holds a crash-safe lease with a Stripe re-check on reclaim, and v1/v2 evaluator disagreements page operators through the alerting pipeline.

July 2, 2026

Security & correctness audit batch 2

All P0 and P1 findings from the July 2 external codebase review fixed and merged with regression tests. CI now also runs the write-path guard and the ontology/actions suites on every PR.

July 1, 2026

Phase 0 of stablecoin controls: ontology + actions registry

@axiru/ontology v0 and @axiru/actions v0 shipped: typed objects, 13 governed verbs, staged-by-default agent execution with graduated autonomy, rail_stablecoin flag, and the Policy Spec v0.1 draft. The foundation for governing money movement beyond Stripe.

May 27, 2026

Cross-rail ops dashboard: shadow agreement + quarantine queue

/dashboard/ops/cross-rail now surfaces the v1-vs-v2 evaluator agreement rate with an explicit M11 cutover gate, plus quarantine-queue KPIs and a JSON feed. First customer-visible slice of M9.

May 23, 2026

Security audit batch 1: C-1, H-1, H-2, plus mediums and lows

Critical content-type guards, timing-safe token compare, error-response sanitization, rate-limit fingerprint hardening, and the Slack response_url allowlist (SSRF guard) shipped after external review.

May 23, 2026

API truth pass on /implementation and /pricing

Marketing pages now reference the real POST /api/v1/decisions endpoint (replacing an aspirational /v1/decide), and the MCP snippets use the real spend-governance tools: axiru.request_spend_approval and axiru.check_spend_policy. Filed two external reviewer audits in /docs/audits.

May 23, 2026

Public roadmap (this page) + /implementation engineer page

Trajectory now visible to buyers without scheduling a call. Engineer-facing /implementation page shows the 10-line integration plus MCP examples.

May 2026

Typed-v2 Prisma PolicyV2 reader for x402 authorizations

End-to-end wiring through Decision Engine v2 + Prisma-backed v2 policies + signer. /api/v1/authorizations now serves real customer policy data.

May 2026

Automated key-rotation rehearsal driver + green log

18 assertions across 7 steps. First green log archived under docs/cross-rail/key-rotation-rehearsals/. Operationalizes M12.

May 2026

x402 demo: fail-closed scenarios + downstream verification

Demo app exercises invalid-token / expired-token / wrong-rail paths and verifies the Go verifier rejects them. Foundation for M7's conformance suite.

May 2026

Fail-closed contract test at the service seam

Locks the fail-closed default at the engine's service boundary so regressions surface in CI, not in production. Required by SOC 2 control narrative.

Beyond Phase-1

What's after the Stripe phase

Three horizons. These are directional bets, not dated commitments; we'll move items into the milestone plan above when they earn a quarter.

Horizon 1

Months 4–12 · multi-processor parity

Stripe is the first rail, not the only rail. Once Phase-1 closes, the same decision engine extends to the rails real finance teams already use for redundancy.

  • Plaid ACH + Modern Treasury adapters: Bank-to-bank governance with the same OVT type system, deterministic policies, and immutable ledger. Same engine, new adapters.
  • Adyen, Braintree, Square adapters: Multi-processor merchants get one policy plane across providers. Cross-rail dedupe stays free: a refund that touches two providers still counts once.
  • Cross-rail policy templates: Velocity caps, country blocklists, and goodwill-credit limits expressed once and enforced across every connected provider.
Horizon 2

Months 12–24 · custody + settlement depth

Stablecoin governance itself was originally slotted here; the OUSD launch and the GENIUS Act pulled it forward into the active plan (see the stablecoin phase above). What stays in this horizon is depth on custody and chain settlement: blockchain settlement is irreversible, and you can't claw a stablecoin back.

  • Fireblocks + Coinbase Prime custody integrations: Custody providers become a first-class adapter: same idempotency key, same decision ledger, same fail-closed semantics under load.
  • Sealed-at-decision tokens for chain settlement: x402's Ed25519/ES256 signing path generalized for non-HTTP rails: a signed allow becomes the only auth a downstream broadcaster will accept.
  • Additional chains + PYUSD in production: The type system already reserves these rails. Production wiring extends the engine beyond the Solana-first launch with deterministic, signed authorization.
Horizon 3

Months 24–36 · sovereign + on-prem

Regulated entities won't route financial-intent payloads through a multi-tenant SaaS regardless of how strong the encryption is. The architecture is non-custodial today; the deployment topology needs to match.

  • VPC sidecar deployment: Run the decision engine inside the customer's VPC. Control plane stays managed; data plane never leaves the customer boundary.
  • On-prem Kubernetes distribution: Helm chart with the engine, signer, ledger writer, and JWKS endpoint. Same code as the SaaS, deployed under customer-controlled keys.
  • Sovereign cloud architectures: Region-locked deployments for jurisdictions that require it. Same SOC 2 controls; localized residency and key custody.

These horizons are subject to design-partner input and market signal. If one of them matters for your team, the fastest path to influence the ordering is to become a design partner.

How we update this

Status here matches what's merged

If a milestone shows shipped here, the underlying PRs are merged into main and the change is in production or staging. We update the page on the same day.

  • Shipped: code is on main, deployed to staging or production, and the milestone's definition-of-done is met.
  • In flight: there's at least one open PR actively driving toward this milestone, or CI is running on the closing change.
  • Next: on the 90-day plan, not yet started. We reserve the right to reorder these based on design-partner feedback after milestone M5.

Want to weigh in on what we build next? Design partners get roadmap input. Book a design-partner conversation →

Next step

Buy the trajectory, not just the feature list.

The product is what's shipped today. The roadmap is what makes Axiru a long-term bet. Shadow mode is free: connect Stripe and you're seeing your own data in five minutes.

Start in shadow mode first. Move to live enforcement later.

See how it works →

We use cookies for analytics and marketing measurement. You can reject non-essential cookies at any time.

Privacy policy
Roadmap & changelog | Axiru | Axiru