BladeRun has not shipped GA yet. The 2026 program is intentionally a closed cohort. You will not find a logo wall on this page because the founding bank partners are protected by the design partner contract, and because we would rather earn the reference than borrow it. Below is what the program is, who it is for, and what design partners commit to.
Tier 1 banks · 2026 cohort
cohort closes · enterprise GA follows
access included for the cohort
design partner pricing through GA
After the cohort closes, the platform ships to the broader enterprise market on different terms. The entitlements below are inherent to the design partner relationship and are not available a la carte.
Mike Patterson (CEO), Paul Marsolan (CTO), and Chris Moos (CSO) staff every architecture, threat-model, and roadmap call. Not a customer success layer relaying questions back to engineering, the engineering decision-makers, on the call.
Design partners review the rolling 9-month roadmap quarterly and have explicit veto on the deployment, identity, and federation surfaces. Your production constraints become the priority sequence.
The bank rule channel and signal taxonomy are defined by the founding cohort. Founding seats carry permanent governance representation in Federation rule decisions, the highest-leverage product surface BladeRun will ever ship.
Cohort pricing is held below 2027 enterprise GA pricing, contractually, for the duration of the partnership. The exact terms are sized against deployment topology, fleet size, and Federation contribution.
Pre-completed SIG, CAIQ, and custom Tier 1 bank VRA questionnaires. SOC 2 Type I report under NDA today; Type II in scope. Pen test results and full subprocessor list shared on request.
SaaS in your VPC, single-tenant on-premises, or fully air-gapped. Customer-managed keys, sealed update channel, and contractual data-residency commitments, available to the cohort from the first deployment.
The cohort is intentionally diverse on geography, regulator surface, and AI program maturity. Below are anonymized archetypes that describe the institutions we are in active diligence with, not specific named banks. Named partners are announced jointly when the cohort closes.
Multi-region production AI agent fleet across customer service, commercial payments, and internal operations. Mature ARB process, established Federation interest, and an existing AI risk and model governance program looking for the runtime layer.
EU-headquartered universal bank with a formal AI program under EU AI Act and DORA scope. Strict data-residency requirements, on-premises preference, and a defined need for sovereign keys and sealed update channels.
Globally significant bank with significant agentic commerce and AP2 / MPP exposure on the merchant-acquiring side. Need spans both bank issuer governance and merchant-side agent identity at the same institution.
Super-regional bank deploying AI agents ahead of peers and recognizing that the runtime governance layer needs to ship before the fraud wave does. Lean security org with high decision velocity and strong founder-buyer dynamic.
We could put logos here. We are choosing not to. Vendor logo walls are easy to fabricate and hard to verify. Until the design partner cohort closes and the institutions in it agree jointly to be named, this page describes archetypes. After the cohort closes, named partners are announced together with their consent and on terms each partner controls. Reference calls for active prospects in legal review are available under NDA on request.
The design partner program is a working relationship, not a logo arrangement. Each side has explicit commitments. Below is what we ask of partners; the founder access, roadmap influence, Federation seat, and held pricing are what we commit in return.
Up-front working session with the founders covering architecture, threat model, deployment topology, and existing AI agent fleet shape. Output is a written scope memo signed by both sides before procurement begins.
BladeRun engineering joins your Architecture Review Board sessions for the cohort engagements. We bring deployment diagrams, network topology, identity integration patterns, and any reference architecture you need pre-formatted to your template.
Pilot in a single agent workflow you choose. Gateway in shadow mode for week one. Enforcement enabled with SOC sign-off on your timeline. Reversible by routing rule. Full Time Machine evidence from day one.
Opt-in to the bank Federation Network. Contribution is one-way signal hashes only, no raw prompts, no customer data, no model output. The privacy contract is reviewed on a separate signoff path so the platform contract is not gated by federation legal.
Not yet. Until the design partner cohort closes and the founding banks agree jointly to be named, we do not publish case studies. After the cohort closes and pilot deployments produce results, case studies are co-authored with the partner and published only on terms the partner controls. We will not ship a case study without active partner sign-off.
Yes, under NDA, for active design partner prospects in legal review. The references are with named contacts at institutions in the cohort and prior personal references from the InAuth and Smobile customer base, banks the founders worked with directly through prior acquisitions. References are arranged after the technical session and before the pilot deployment.
Publicly: the platform architecture, the Federation Network white paper, the threat taxonomy, the deployment topology options, and the buying motion. Confidential under NDA: pen test reports, SOC 2 Type I report, the full subprocessor list, design partner names, pricing memos, and any partner-specific deployment detail. The split is intentional and audit-friendly.
The 2026 design partner cohort is bank-only. The merchant Federation network and the broader enterprise GA path open separately on a different timeline. If you are a card network, an issuer-processor, or a major payment platform looking at agentic commerce specifically, reach out. Those conversations are scoped under a separate program.
If the cohort closes before procurement completes on your side, you transition into the 2027 enterprise GA path. You retain the right of first refusal on the next Federation rule channel and any deployment-specific work already started during your evaluation carries over. We do not "sell out" institutions that have started serious diligence. That is part of how the program is run.
If your institution looks like one of the archetypes above and your AI program is moving from pilot to production in 2026, the design partner inquiry is open. Inquiries are read by the founders directly.