KYE Protocol™ ecosystem · one orientation, four surfaces
Profiles define. Connectors integrate. Apps productise. Plugins extend.
KYE Protocol™ ships four ecosystem surfaces. Each one solves a specific adoption problem. Pick the one that matches what you're trying to do; the right starter, schema, and SDK is one click away.
One sentence per surface.
grid_viewKYE Connector Profiles™Profiles define the rules. 11 domain profiles — Payment, Commerce, Open Finance, Agent Runtime, Compliance Evidence, Pension, Health, Security & SIEM, Insurance, Utilities, Legal — each binding a family of connectors to a shared authority model + event family + evidence shape + conformance suite.view profiles →
extensionKYE Connector Hub™Connectors integrate KYE™. 14 connector categories (IPG · MPG · checkout · MCP · IAM · SIEM · GRC · KYC/KYB/KYA …), one canonical
kye.connector_manifest.v1 manifest schema, ~45 reference connectors searchable in the explorer.view connectors →
appsKYE App Store™Apps productise KYE™. 21 production-ready apps grouped by domain — KYE Payment Authority Gateway™, KYE Checkout Guard™, KYE Open Finance Authority Gateway™, KYE Evidence Pack Viewer™, KYE Contract Authority Gateway™, and 16 more.view apps →
powerKYE Plugin Marketplace™Plugins extend KYE™. 9 plugin categories (MCP tools, webhook verifiers, policy packs, evidence exporters, conformance fixtures, dashboard widgets, sandbox flows, approval workflows, SDK extensions) with 18 reference plugins.browse plugins →
From Core Protocol to Plugin — one tree.
Five layers, each a clean contract over the layer below. The same authority object travels from spec to runtime to evidence.
- L1L1KYE Core Protocol™ — vocabulary, schemas, runtime, decision codes, audit chain. The base contract.
- L2L2KYE Profiles — domain rules:
kye.payments.v1,kye.healthcare.v1,kye.federation.v1, etc. (36 v1.0 + 5 v1.1 preview) - L3L3KYE Connector Profiles™ — integration-category rules. Each profile binds a family of connectors to a shared authority model + event family + evidence shape + conformance suite.
- L4L4Individual connectors — specific systems (Stripe, Shopify, OpenBankProject, NHS API, Splunk, …) under their parent profile.
- L5L5Apps · Plugins · Widgets — KYE App Store™ productises · KYE Plugin Marketplace™ extends.
KYE Core Protocol™
└── kye.payments.v1 (KYE Profile)
└── KYE Payment Profile™ (Connector Profile)
├── KYE IPG / MPG Connector™
├── KYE Stripe Connector™
├── KYE PayPal Connector™
└── KYE Open-Banking Payment-Initiation Connector™
│
└── KYE Payment Authority Gateway™ (App)
└── KYE Webhook Verifier Plugin™ (Plugin)What are you trying to do?
- AI want to understand the rules for my domain. → KYE Connector Profiles™. Pick the profile that fits (Payment, Commerce, Open Finance, Health, Pension, Agent Runtime, Compliance Evidence, Security & SIEM, Insurance, Utilities, Legal). Each profile lists the authority model, the events it carries, the conformance fixtures.
- BI want to integrate KYE™ with a specific system I already run. → KYE Connector Hub™. Search the explorer by name / type / risk envelope. Pick a connector; ship the manifest; sign + submit.
- CI want a production-ready app I can deploy this quarter. → KYE App Store™. 21 apps across payments, commerce, open finance, sandbox, sector apps, agentic / MCP, audit, certification, legal.
- DI want to add a small focused module to my existing KYE™ stack. → KYE Plugin Marketplace™. MCP tools, webhook verifiers, policy packs, evidence exporters, dashboard widgets — ~half a day of work each.
- EI want to write code against the runtime. → Build with KYE™ + Developer quickstart. Three SDKs (TypeScript / Python / Go), 38 conformance fixtures, reference Gateway, KYE MCP Server™.
- FI want to see the runtime semantics live before I write anything. → Interactive Widgets. Six live widgets, no signup, no install — agent-purchase simulator, Decision Map™ viewer, Connector Hub™ explorer, Blast Radius Map™, Evidence Pack Viewer™, Choose-Your-Role router.
Open contracts. Paid operations.
| Surface | Open source · Apache 2.0 | KYE Cloud™ · commercial |
|---|---|---|
| Profiles | Every kye.connector_profile.v1 manifest, supported-connector list, conformance suite, dictionaries. | Sector-specific profile bundles · regulated-industry presets. |
| Connectors | Every kye.connector_manifest.v1 beneath a profile · sample IPG / checkout / MCP / SIEM connectors · SDK adapters · local test harness. | Managed Connector Hub™ · enterprise connector engine · SLA-backed delivery · connector health monitoring. |
| Apps | Reference architectures · sample kye.app_manifest.v1 · SDK examples per app. | Hosted apps in KYE App Store™ — KYE Payment Authority Gateway™, KYE Checkout Guard™, KYE Evidence Pack Viewer™ Pro, etc. |
| Plugins | kye.plugin_manifest.v1 · sample plugins · permissions dictionary · conformance fixtures. | Hosted KYE Plugin Marketplace™ · install / monitor / replay UI. |
| Runtime | Reference Gateway: PEP middleware · embedded ePDP · conformance runner. | Managed runtime gateway, decision engine, state engine, graph engine, signal bus, evidence engine, dashboards. |
Why this split? The contracts have to be open or KYE Protocol™ isn't a protocol — partners and developers must be able to implement, integrate, and verify without depending on a hosted service. The runtime engine that scales decisions, signal delivery, and connector operations sits behind a paid layer where the operational moat lives.