A small, deliberate group of Tier 1 banks working with us as partners, with founder access, roadmap input, and a founding Federation seat. We work with these partners today; their names are held under NDA, and we would rather earn the reference than borrow a logo, so the institutions below are described as archetypes.
The partner program is deliberately small so each partner's threat model actually shapes the platform. It is a working relationship, not a logo arrangement. Below is what the program is, who it is for, and what partners commit to.
bank partners · under NDA
access on every call
founding Federation governance
partner pricing, by contract
The entitlements below are inherent to working with us as a partner and are not available a la carte. They are how a partner's production constraints become the priority sequence.
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.
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.
Partner pricing is held for the duration of the partnership, contractually. 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 group is intentionally diverse on geography, regulator surface, and AI program maturity. Below are anonymized archetypes that describe the institutions we work with, not specific named banks. Named partners are announced jointly, only with each partner's consent.
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.
The 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.
We hold partner names in confidence by contract. Case studies are co-authored with the partner and published only on terms the partner controls, with active sign-off, and we would rather earn a reference than borrow a logo. That is why this page describes the institutions we work with as archetypes.
Yes, under NDA, for active partner prospects in legal review, with named contacts at the institutions we work with, plus 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, the SOC 2 report, the full subprocessor list, partner names, pricing memos, and any partner-specific deployment detail. The split is intentional and audit-friendly.
The bank partner track is bank-only. The merchant Federation network and the broader enterprise track run in parallel. 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 your institution looks like one of the archetypes above and your AI program is moving from pilot to production, the partner inquiry is open. Inquiries are read by the founders directly.
