The Registry
The Registry
Enterprise-grade | High-performance | Self-hosted
Enterprise-grade | High-performance | Self-hosted
Designed by a member of the JSON Schema Technical Steering Committee
Map Your Organisation
Group schemas by team, department, domain, or vendor, as deep as your organisation requires. Every layer gets its own health score and contact details, so quality and ownership are visible and actionable across your entire structure.
Explore a live instance
Monitor Your Schema Health
Every schema gets a live quality score from our schema linter, the most advanced one in the market. Things like unused definitions, missing descriptions, anti-patterns, and much more are surfaced automatically and aggregated up through your organisational structure.
Learn more about our linter
Embrace GitOps
Your schemas live in Git, and so does your registry configuration. Every schema change and registry deployment goes through your existing review workflow. Database-backed registries force you to rebuild approval processes, access controls, and audit trails from scratch inside the registry itself. With Sourcemeta One, you get all of that out of the box, using the Git tools and processes your team already knows.
Learn more about the configuration file
Deploy Headless
Sourcemeta One ships with a fully featured web explorer for navigating and understanding your schemas. But it is entirely optional. Run the registry headless for API-only deployments, or build your own frontend on top of our complete HTTP API. Everything you see in our UI is powered by the same API you have full access to.
Learn about the API
Built for Performance
Written in C++ and powered by Blaze, our high-performance JSON Schema validator. Each instance starts in under 2 milliseconds, consumes under 3 MiB of RAM at idle, and requires zero external dependencies. No database, no message queue, no JVM. Just a single stateless Docker container that scales horizontally without limits.
Read the research paperHow We Compare
The table below covers the most commonly evaluated alternatives. One path not shown is building a registry in-house. It is a viable option for teams with significant engineering capacity and deep JSON Schema expertise, but carries high development cost, ongoing maintenance burden, and rarely matches the governance capabilities of a dedicated solution.
| Confluent | Apicurio | SchemaStore | Sourcemeta One | |
|---|---|---|---|---|
| Specialised in JSON Schema | one of nine supported formats |
one of nine supported formats |
||
| No database required | requires a running Kafka cluster as storage backend |
requires PostgreSQL or Kafka for production |
static files on GitHub |
|
| Deploys as a single Docker container | requires Kubernetes Operator for recommended deployment |
|||
| Self-hosted | via Confluent Platform |
— not meant to be self-hosted for general use |
||
| GitOps-native | ||||
| Rejects invalid schema submissions | validates Kafka message IDs, not JSON Schema correctness |
validity rule is optional and disabled by default |
many schemas are invalid, community-contributed without spec enforcement |
|
| Aggregated schema health scores | powered by the most advanced JSON Schema linter in the market |
|||
| Arbitrary directory structure | groups cannot be nested, maximum two levels |
flat file structure |
||
| Spec-compliant schemas with IDE compatibility | schemas served as-is |
schemas served as-is |
known VS Code compliance issues mean schemas are compromised to work around them |
automatically serves a transformed version for VS Code without affecting registry schemas |
| High performance, low resource usage | JVM-based |
Quarkus Java runtime |
— file serving only, no JSON Schema processing performed |
C++, starts in under 2ms, under 3 MiB RAM at idle |
| Premium support plan available | ||||
| Support includes JSON Schema TSC expertise | ||||
| By a company in the European Union | Confluent by IBM |
Red Hat by IBM |
Microsoft |
|
| Source-available for audit |
Enterprise Ready
Built for teams where security, compliance, and operational independence are non-negotiable.
Full Code Transparency
The Sourcemeta One Enterprise edition, while not open source, is fully available on GitHub for security audits, compliance reviews, and internal assessments. No black-box concerns, no blind trust required. If Sourcemeta ever ceases to exist, you retain full rights to continue running and maintaining your own instance.
Built for Regulated Supply Chains
Every release ships with signed container images via Cosign and Sigstore, and a signed SPDX Software Bill of Materials. Cryptographic operations are built against the OpenSSL FIPS provider for industries where compliance is non-negotiable.
Deploy Anywhere, Depend on Nothing
No database, no message queue, no external services. A single stateless Docker container for x64 and ARM64 that your team can deploy, scale, and operate without specialist knowledge, even in airgapped and highly regulated environments.
Handle Any Load, At Any Scale
Built in C++, proven by research to be at least 10x faster than alternatives. Each instance starts in under 2 milliseconds and consumes under 3 MiB of RAM at idle. Stateless by design and fully independent, instances scale horizontally without limits or coordination overhead.
Enforce Your Own Guidelines
Every organisation has its own schema requirements. Define custom linting rules, each annotated with your own explanations so teams understand not just what is wrong but why. They integrate directly into the health scoring system, making compliance with your internal guidelines visible across every schema your teams produce.
Start With a Complete Foundation
Most governance programmes begin the same way: extract all your schemas, discover a mess, and spend months cleaning it up. The majority of what you find will map to standards your industry already defined. The Sourcemeta One Enterprise edition ships with hundreds of expertly implemented ISO, IETF, W3C, and industry schemas, heavily unit tested and maintained by us, so you start with a solid foundation on day one.
"This is definitely going to become an incredibly important tool for defining concepts using best in class standards"
"This is a terrific project and should be a standard subscription for any enterprise working with JSON Schema"
"This aligns exactly with my thinking! OpenAPI should not include schemas but should reference them externally from a source of truth like this one"
"Before the standard library, defining foundational schemas in an enterprise was a time-consuming, error-prone task that could result in inconsistencies. This library is a game-changer, delivering huge time savings while ensuring improved API consistency and strong governance of API definition files"
Pricing
Deploy the open-source version at no cost, pilot it with your team, and evaluate it with no time limits.
JSON Schema is ubiquitous and critical to our operations, yet so many of us have barely scratched the surface when it comes to putting the specific to work, let alone getting our house in order
The API Evangelist
Free
- All core features
- BSL 1.1 license
- Community support via GitHub
Pairs with the JSON Schema CLI and Sourcemeta Studio VS Code extension for a complete local development workflow.
Deploy for FreeEnterprise
- Standard Library (ISO, IETF, W3C, and more)
- Custom linter rules for your organisation
- Supply chain security (Cosign, FIPS, SBOM)
- Premium support by a TSC member
- Assisted onboarding and integration
- Optional custom schema development
Open Source
We maintain critical open-source projects for the JSON Schema ecosystem. Explore the full suite on GitHub.