WHY PER-DEPLOYMENT
Bridge deployments vary by orders of magnitude. A single-product Bridge API integration runs differently from a multi-product Workspace deployment across 14 facilities. Per-seat pricing distorts both ends.
Customers in regulated industries also have compliance constraints that change deployment cost: HIPAA-aligned audit retention is different from financial-services audit retention. Air-gapped deployments require different infrastructure than SaaS. Pricing has to reflect these realities.
What we commit to: a written scope before any signature. A clear breakdown of what changes the price. A clear renewal posture (we renew quickly, on terms that don't surprise the customer).
DEPLOYMENT TIERS
Three structural tiers.
Pilot
First production deployment, single product, time-boxed.
→Single Bridge product
→Single deployment environment
→8-12 week scope window
→Includes audit-trail review with regulator (if applicable)
Scoped on a call
Production
Full-scale single-product or multi-product deployment.
→One or more Bridge products
→Multiple environments per product
→Standard SLA: 99.95% routing availability
→Annual renewal with predictable terms
Scoped on a call
Strategic
Multi-year, multi-product, with custom Context modules.
→All Bridge products available
→Custom Context modules included
→Dedicated deployment engineering
→Multi-year hold horizon (matches Kyros structure)
Scoped on a call