subscription-service / pricing

Same code on every tier.

FOSS, Apache 2.0

subscription-service Core

Any team that can run Docker or Kubernetes

$0

The full pipeline, operator UI, observability, and built-in plugins. The same code on every tier.

Get on GitHub

Supported FOSS

subscription-service Pro

Teams who want the same code with a vendor behind it

Per-instance subscription

Core plus certified vendor profiles, enterprise IAM/storage plugins, business-hours support, and a quarterly upgrade-readiness review.

Managed SaaS

subscription-service Cloud

Teams who don't want to operate it themselves

Per-message or per-facility

We run it for you. Dedicated tenant, automated upgrades, 24/7 on-call, certified profiles, SOC 2 + HIPAA BAA.

What's in each tier

Capability Core Pro Cloud
HL7 v2 MLLP ingest
Matchbox mapping
HAPI FHIR R4 + Subscriptions Backport
Operator UI (all 8 routes)
OIDC auth (any provider)
Multi-tenancy toggle
Per-channel security toggle
US Core profile validation
Prometheus + JSON logs + traces + agent API
Vendor profiles — community quality
Vendor profiles — certified, with regression suite + indemnity
Vendor profiles — professionally mapped
Storage backend plugin: sharded multi-region
Authorization plugin: Azure AD groups
Authorization plugin: Okta/Auth0/etc SSO
FHIR R4B + R5 forward compat (when shipped)
Audit export ITI-20 bundle
Business-hours email support
24/7 on-call add-on add-on
Hosted environment add-on
SOC 2 attestation
HIPAA BAA
HITRUST attestation roadmap
Migration / integration consulting add-on add-on
Training add-on add-on

"add-on" means available at this tier as a paid add-on. "roadmap" means committed but not shipped yet. "—" means not offered at this tier.

Why isn't feature X a paywall?

Because we don't believe in feature-gated open source. If a capability ships in Core, it ships forever — no future "Pro-only" relabel. Commercial value is in service, certification, and scale, not in withholding code. Read the rationale in the FAQ.