Commercial Model
Commercial packaging guidance for ABS Core as proprietary, self-hosted infrastructure.
Commercial Model
ABS Core is not presented here as a public self-service SaaS subscription. Commercial discussions are structured around proprietary infrastructure licensing for customer-controlled deployment.
Commercial Tiers & Methodology
While exact pricing is quoted per deployment, we follow a volume-based tiering model based on Governed Events Per Day (GEPD):
| Tier | Governance Scope | Target Scale |
|---|---|---|
| Explorer | Up to 1,000 events/day | PoCs & Early Prototypes |
| Industrial | Up to 100,000 events/day | Production Fintech Services |
| Enterprise | Unlimited events/day | Institutional Banking Core |
Primary Commercial Metric
The Annual Contract Value (ACV) is primarily driven by:
- Event Volume: Total number of intercepted tool calls.
- Enforcement Depth: Complexity of the policy graph (Procedural vs WASM).
- Audit Retention: Storage duration in the Forensic Ledger.
- Verification Grade: Depth of cryptographic proof-of-state.
| Feature | Explorer | Industrial | Enterprise |
|---|---|---|---|
| Forensic Ledger | Local / D1 | Local / D1 | Hybrid / Dedicated |
| Blockchain Proof | Not Available | Polygon Amoy (Early Access) | Mainnet (Q3 Roadmap) |
| Engine Version | v4.3.3 Prototype | v4.3.3 Enterprise Core | v4.3.3 High Precision |
| Audit Trail | Local Hash-Chain | Cloudflare D1 | Hybrid / Dedicated |
[!NOTE] Blockchain anchoring on public mainnets (Bitcoin/Ethereum) is currently in R&D Pilot stage. Production deployments v4.3.3 utilize local cryptographic hash-chains (tamper-evident) with an optional transition to public L2 (Polygon) for Industrial tier partners.
Buyer Evaluation & ACV Guidance
Technical and commercial evaluation begins with deployment scope and governance requirements. ABS Core is licensed as infrastructure, with pricing tailored to the risk level of the governed workflows.
[!NOTE] Indicative Value: ABS Core contracts are structured as annual proprietary software licenses for client-controlled deployment. Contract values vary based on the number of governed agents, environment (Cloud / On-premise / Customer VPC), and specific compliance mandates. Pricing is determined per-engagement based on institutional scale and operational criticality.
This model allows for precise ACV estimation during due diligence without requiring public fixed-price tables, common in enterprise infrastructure software.
Related material
For positioning and diligence framing, see the Licensing page.