From 5dd7d6452c775b91bdda757bafc26e765878219d Mon Sep 17 00:00:00 2001 From: pratyushsood24 Date: Sun, 28 Jun 2026 00:13:15 +1000 Subject: [PATCH 1/2] =?UTF-8?q?docs:=20add=20OPEN-CORE.md=20=E2=80=94=20ca?= =?UTF-8?q?nonical=20open=20vs=20commercial=20capability=20line?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Records the accepted open-core model (2026-06-27): free/paid line at operation/governance/scale, never protocol/verify. All three pillar libraries Apache-2.0; Cloud/Enterprise-Edition/Sovereign/on-chain are the commercial editions. Capability split only — dollar amounts stay in product-truth.json / idprova.com, not here. Co-Authored-By: TechBlaze --- OPEN-CORE.md | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 OPEN-CORE.md diff --git a/OPEN-CORE.md b/OPEN-CORE.md new file mode 100644 index 0000000..7a3c1ad --- /dev/null +++ b/OPEN-CORE.md @@ -0,0 +1,82 @@ +# IDProva Open-Core Model + +> **Status:** accepted 2026-06-27. This document is the canonical statement of *what is open and +> what is commercial* in IDProva. Dollar amounts live in pricing collateral (see +> [`product-truth.json`](https://github.com/techblaze-au/idprova-cloud) and idprova.com), **not here** — +> this file defines the capability line, which is stable; prices change. + +## The governing rule + +**The free/paid line is drawn at operation, governance, and scale — never at the protocol or the +verify path.** Paywalling the protocol or the ability to verify would break the "neutral / open" +claim that is the entire point of a cross-standard trust layer. So everything needed to *speak the +protocol* and *verify* is open source; what you pay for is having someone *operate and govern it at +scale* for you. + +This mirrors how the credible neutral-infrastructure projects draw the line: Sigstore, SPIFFE/SPIRE, +and CT keep signing/verification open and monetise the *operated* service and the *enterprise +governance* around it; HashiCorp Vault, Keycloak/RH-SSO, and Ory keep the engine open and charge for +namespaces/governance/HA/support. + +## What is OPEN (Apache-2.0, public — `github.com/techblaze-au/idprova`) + +All three pillar **libraries**, in full: + +| Pillar | Crate | Open capability | +|---|---|---| +| **A** | `idprova-webbotauth` | RFC 9421 HTTP Message Signatures sign **and** verify; RFC 7638 JWK-thumbprint ↔ `did:aid:` binding; JWKS / Signature-Agent directory model. | +| **C** | `idprova-vc` | W3C VC Data Model 2.0 issue **and** verify (`eddsa-jcs-2022`); DAT→VC bridge; AP2/A2A mandate types. | +| **B** | `idprova-trust-registry` | Issuer data model; single-authority **TrustList sign + offline verify**; SQLite issuer store + `may_attest`; cross-standard **resolver**; RFC 6962-style **Merkle log: inclusion + consistency proof generation AND verification, signed tree heads**. | + +The federation **spec + proof verification** is open on purpose: it is what makes "neutral / +mirrorable / decentralised" *provable* rather than promised. Anyone can verify a signed trust list or +a tree head offline, with no network and no chain. + +## What is COMMERCIAL + +The open libraries give you the primitives; the commercial editions *operate and govern* them. + +### Cloud (hosted SaaS — idprova.com) +Operating the hosted directory / trust-list / **transparency log** (uptime, monitoring), **HSM key +custody**, and **HA / replication** of the trust-anchor key. You could self-host the open library +instead; Cloud is "we run it, with custody and uptime guarantees." + +### Enterprise Edition (self-host, commercial licence — separate component, NOT in the public repo) +The multi-operator / governance layer: +- multi-operator **federation management** & peer-admission orchestration; +- **governance**: issuer-admission approval workflow, tamper-evident audit of trust-list changes; +- **RBAC, SCIM**, compliance reporting, anomaly detection; +- SLA / support. + +> ⚠️ **Naming:** "Enterprise **Edition**" (this self-host governance component) is distinct from any +> "Enterprise" *tier* of the hosted SaaS. They are different products. See the pricing collateral. + +The open `idprova-trust-registry::federation::mirror()` is a documented boundary stub that returns an +"operator/enterprise edition" error — live multi-operator sync is the line where the commercial +component begins. + +### Sovereign (paid licence) +Air-gapped / offline trust-list deployment + IRAP / Essential-Eight evidence packs, per-agency +licence. The open library already verifies fully offline; Sovereign is the packaged, supported, +accreditation-ready deployment for government / DISP / PROTECTED environments. **This is the +beachhead — a structural exclusion the global incumbents cannot occupy — not an afterthought.** + +### Commercial / on-chain (paid — being validated) +On-chain (XRPL-first) KYA anchoring + a **KYA attestation API** (per-call) + issuer/registry +**membership**. This is the newest and least-de-risked surface, so it is **validated with a +"founding issuer" pilot before pricing is fixed** — it is deliberately *not* baked into the canonical +pricing file yet. + +## Why open-source here is the entry ticket, not the moat + +Open source buys credibility and auditability — necessary for a trust layer, but not sufficient as a +defence (walt.id, SPIRE, Keycloak are open and ahead). The defensible position is the **intersection +that no single incumbent can occupy at once**: + +1. **Sovereign / air-gapped** — a structural exclusion of operator-owned directories (Visa TAP, + Cloudflare Web Bot Auth, MS Entra Agent ID, Google AP2); +2. the **neutral cross-standard resolver / verifier** — the "Switzerland" layer an operator-owned + directory will never build; +3. **standards citation** (Commonwealth / NIST / TRQP) as an influence moat. + +Position: *the open, neutral, sovereign verify-resolve-reference layer* — **not** "the Visa of KYA." From 3ab198de36a1ac8d505b8d8da72dac041fe8e58f Mon Sep 17 00:00:00 2001 From: pratyushsood24 Date: Sun, 28 Jun 2026 01:19:59 +1000 Subject: [PATCH 2/2] docs(readme): replace unanchored $149/mo Cloud price with 'Contact us' The $149/mo figure matched no tier in canonical product-truth.json; the managed/governance Cloud line is sales-led (Enterprise = Contact us per the 4-tier plan). Removes the unbacked price claim from the marketing surface. Co-Authored-By: TechBlaze --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1db8f22..e018ca2 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ You keep Okta. You keep Entra ID. You keep Auth0. You add IDProva for the agents Three deployment stories — pick whichever fits your environment: ### 1. Global Cloud -Hosted IDProva on AWS, GCP, or Azure in your region of choice. AU (live), US East (v1.0), EU Frankfurt (v1.0 stretch), Singapore + UAE (v1.1). Web dashboard, SSO, RBAC, compliance report generator, SIEM integration, anomaly detection. Starting at $149/mo. → [idprova.com](https://idprova.com) +Hosted IDProva on AWS, GCP, or Azure in your region of choice. AU (live), US East (v1.0), EU Frankfurt (v1.0 stretch), Singapore + UAE (v1.1). Web dashboard, SSO, RBAC, compliance report generator, SIEM integration, anomaly detection. Contact us for pricing. → [idprova.com](https://idprova.com) ### 2. Self-hosted Enterprise Run the full stack inside your VPC. Apache 2.0 source. No licence fees for the protocol. Commercial Enterprise Edition available with SLA, support, and additional management features.