Tier 1
bank partners, under NDA
Founder
access included at every tier
1 hr
meeting before any commitment
Your VRA
timeline, we work to your calendar
How we sell

Two ways to deploy. Both by inquiry.

Same platform, same detection, same SLA. You choose where it runs: BladeRun-operated SaaS in your own VPC, or fully on-premises in your environment. Price is a function of deployment topology, agent fleet size, retention, and Federation participation.

On-premises · sovereign
On-premises
By inquiry

The whole platform runs inside your environment under your own IAM, with a fully air-gapped option for sovereign and regulator-mandated workloads.

  • All platform components, production-licensed
  • Fully on-premises or air-gapped deployment
  • Customer-managed keys end to end
  • Sealed update channel with offline signature verification
  • Optional Federation participation via one-way export
  • Custom data-residency and retention contracts
  • Long-term-support release line
Always included

What you get on every tier.

There is one BladeRun platform. We do not gate detection coverage, redaction classes, or Federation rule channels behind a higher tier. The same seven components ship in every deployment.

01 · Gateway

Reverse proxy in your AI call path

Every prompt and response inspected. Every MCP endpoint verified. Under 15ms. NPI, PCI, and PII redaction with deterministic per-session tokenization.

02 · Sentinel SDK

In-process agent runtime

Tool-call inspection, identity attestation, and policy enforcement inside the agent.

03 · BladeRun.js

Page tag on customer-facing surfaces

Detects agents arriving in the browser, accepts attestation tokens from registered shopping agents, and scores synthetic abuse.

04 · Overseer AI

Behavioral baseline at fleet scale

Per-agent behavioral baselines and drift detection across the entire agent fleet.

05 · Kill Switch

Per-agent and fleet-wide containment

One-call quarantine of a single agent or the entire class. Reversible. Audited.

06 · Time Machine

Durable record of every action, sealable on demand

Prompt, tool call, sub-agent spawn, response, and policy decision written to your S3 bucket under your KMS keys.

07 · Federation Network

Cross-bank threat signal network

One-way signal hashes, k-anonymity, double-blind membership. Privacy-preserving.

SOC 2 Type II
Type I report available now under NDA. Type II audit in progress.
included · all tiers
VRA / SIG / CAIQ
Pre-completed Tier 1 bank vendor risk packages. Standard or custom questionnaires accepted.
included · all tiers
Penetration test results
Most recent third-party test report shared under NDA before legal review.
included · all tiers
Founder access
Mike Patterson (CEO), Paul Marsolan (CTO), Chris Moos (CSO), direct working sessions on architecture and roadmap.
included · all tiers
The buying motion

How banks actually buy this.

VRA, ARB, Legal, InfoSec, Compliance, Procurement. We know the order, the artifacts, the timelines, and the friction points. Our onboarding is engineered around that workflow, not against it.

Stage 01 · 60 to 90 days

Vendor Risk Assessment

Completed VRA questionnaire, SOC 2 Type II, penetration test results, data-flow diagrams, subprocessor list, and incident response procedures. We arrive with the artifacts pre-formatted.

Stage 02 · 30 to 60 days

Architecture Review Board

Reference architecture, deployment diagrams, network topology, and identity integration patterns. Documentation pre-formatted for your ARB template, with the founders on the call.

Stage 03 · 30 to 45 days

Legal & privacy review

MSA, DPA, BAA where applicable. The Federation Network privacy contract is reviewed separately and gated to a different signoff path so the platform contract is not blocked.

Stage 04 · 30 to 60 days

Pilot in one workflow

Gateway in shadow mode for week one. Enforcement enabled with SOC sign-off. Reversible by routing rule. Full Time Machine evidence from day one. Pricing is anchored after the pilot.

Pricing FAQ

What banks ask before procurement.

Do you publish prices?
No. Every BladeRun deployment is sized against deployment topology (SaaS in VPC vs on-premises vs air-gapped), agent fleet size, retention requirements, and Federation participation. Tier 1 banks do not buy from a price list, and we do not pretend to sell from one. Pricing is shared in writing after the technical session and before legal review.
Why work so closely with a few banks first?
Two reasons. First, the AI agent attack surface is moving faster than any single vendor's roadmap. A small group of Tier 1 banks at the table ensures the platform ships against real production constraints, not whitepaper threats. Second, the founding Federation seats are the highest-leverage product surface BladeRun will ever ship. The founding institutions define the rule channels and signal taxonomy that every later member inherits.
How is pricing set?
Pricing is set against deployment topology (SaaS or on-premises), agent fleet size, retention, and Federation participation, and shared in writing after the technical session. Founder access, roadmap input, and the founding Federation seat are inherent to the relationship, not line items.
Is on-premises priced differently from SaaS?
Yes. On-premises deployments carry additional engineering, sealed update channel, and long-term support obligations that are reflected in pricing. SaaS-in-VPC and single-tenant on-premises are common starting points for banks; air-gapped deployments are quoted separately under the Custom Sovereign tier and typically include a joint engineering allocation.
Is the Federation Network priced separately?
Federation membership is included on every tier. Contribution is opt-in. The platform works fully without it. Members who contribute one-way signal hashes receive the full bank rule channel; non-contributors receive the curated subset. The privacy contract for Federation participation is reviewed separately so the platform contract is not gated by Federation legal review.
Can we run a paid proof of concept before procurement closes?
Yes. The standard pilot is 30 to 60 days, scoped to one workflow, and runs in shadow mode for the first week. The pilot output, Time Machine evidence, behavioral baselines, classifier verdicts, is yours regardless of whether you proceed. Pilot terms are a short addendum to a mutual NDA and do not require a full MSA in place.
Start with a conversation

One hour. Then we talk numbers.

A 1-hour meeting with the founders. Architecture, threat coverage, deployment topology. Then a written pricing memo against your specific scope.