Blaze: Compiling JSON Schema for 10x Faster Validation. Read our paper

Accelerate Your XML-to-JSON Modernisation Initiative

Accelerate Your XML-to-JSON Modernisation Initiative

For Regulatory Industries | Fully Standards Compliant | Premium Support

For Regulatory Industries | Fully Standards Compliant | Premium Support

A growing library of battle-tested JSON Schemas implementing standards from ISO, IETF, IEC, W3C, XBRL, and more. Ready to plug into your OpenAPI specs and API Gateways. Eliminate years of schema development, ongoing maintenance, and the regulatory risks of implementing standards yourself.

Led by a member of the JSON Schema Technical Steering Committee

These are the standards we are covering so far:

Organisation Standard Title
IEEE IEEE Std 754-2019 IEEE Standard for Floating-Point Arithmetic
IEEE IEEE Std 1003.1-2017 IEEE Standard for Information Technology—Portable Operating System Interface (POSIX)
IETF RFC 3066 Tags for the Identification of Languages
IETF RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
IETF RFC 4648 The Base16, Base32, and Base64 Data Encodings
IETF RFC 4918 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
IETF RFC 5322 Internet Message Format
IETF RFC 5646 Tags for Identifying Languages (BCP 47)
IETF RFC 5789 PATCH Method for HTTP
IETF RFC 6901 JavaScript Object Notation (JSON) Pointer
IETF RFC 7807 Problem Details for HTTP APIs
IETF RFC 8141 Uniform Resource Names (URNs)
IETF RFC 9110 HTTP Semantics
ISO ISO 3166-1:2020 Codes for the representation of names of countries and their subdivisions
ISO ISO 4217:2015 Codes for the representation of currencies and funds
ISO ISO 639:2023 Codes for the representation of names of languages
ISO ISO 8601-1:2019 Date and time — Representations for information interchange — Part 1: Basic rules
ISO ISO 8601-2:2019 Date and time — Representations for information interchange — Part 2: Extensions
ISO ISO 80000-1:2022 Quantities and units — Part 1: General
ISO ISO/IEC 2382:2015 Information technology — Vocabulary
ISO ISO/IEC 9899:2024 Programming languages — C
JSON-RPC JSON-RPC 2.0 JSON-RPC 2.0 Specification
W3C XML Schema Part 2 XML Schema Datatypes Second Edition
XBRL XBRL 2.1 Extensible Business Reporting Language (XBRL) 2.1
XBRL XBRL DTR XBRL Data Types Registry
XBRL XBRL UTR XBRL Units Type Registry

Regulated Industries Can't Afford Schema Implementation Risk

Eliminate compliance exposure, implementation complexity, and maintenance burden

Regulatory Risk

Schema errors become regulatory violations

In regulated industries, validation failures aren't technical bugs; they're compliance breaches. When schemas accept malformed data or fail to enforce constraints, you're exposed to regulatory penalties and audit failures. Hand-crafted schemas rarely capture every edge case that auditors scrutinise.

Implementation Burden

Industry standards often exist only in XML

Many standards provide XML schemas, but often JSON implementations are non-existent or poorly documented. Translating XML Schema to JSON Schema requires deep dual-format expertise and significant time investment. Most organisations can't do it or burn extraordinary resources trying.

Ongoing Maintenance

Standards evolve, and your schemas must too

Industry standards release updates. Regulations change. JSON Schema and OpenAPI change too. Maintaining schema accuracy isn't a one-time project; it's perpetual expert work. We track updates, maintain backward compatibility, and ensure your schemas stay compliant as regulations evolve.

Pricing

Sourcemeta is led by Juan Cruz Viotti, a member of the Technical Steering Committee that defines and maintains the JSON Schema specification itself. You are not buying interpretation, but definitive expertise from the source. This level of implementation quality and support simply doesn't exist elsewhere.

Community

Free

  • Full access
  • Commercial evaluation
  • Non-commercial use
  • Open-source projects
  • Research and education
Explore on GitHub

Enterprise

Custom Pricing

Tailored to your organisation's size, compliance requirements, and support needs

  • Commercial Licensing
  • Production deployment rights
  • Company-wise usage
  • Custom licensing terms
  • Enterprise Support
  • Direct access to JSON Schema TSC member
  • Priority technical support
  • Assisted onboarding and integration
  • Optional Add-Ons
  • Custom schema development
  • On-demand schema training
  • Self-hosted or managed schema registry
  • High-performance schema validation (Blaze)
Schedule Consultation

What's the Alternative?

This is not about $ref. It's about having the in-house talent and correctly implementing dozens of specifications, reading paywalled standards, handling edge cases, keeping up with updates, and obsessively guaranteeing compliance.

Do it yourself With ChatGPT Ignore the problem With Sourcemeta Sourcemeta
Reading Specifications €30,000
(375 hours)
Hope ChatGPT was illegaly trained with the potentially copyrighted standards Not needed Done for you
Implementation & Testing €60,000
(750 hours)
Ask ChatGPT Basic type checks everywhere Hundreds of schemas ready and more coming
Annual Maintenance €20,000/year
(250 hours)
Ask ChatGPT again None (as you are barely validating) Done for you
Standards Compliance If done correctly No guarantees No compliance at all Guaranteed
Security Risks Low (if done correctly) Data breach: €50K-500K+
GDPR: €20M or 4% revenue
Security incident: €100K+ Battle-tested
Support Your team's problem Your team's problem Your team's problem Premium support by a member of the JSON Schema Technical Steering Committee
Total First Year €110,000+
Assuming you managed to hire a JSON Schema expert
€0 → Catastrophic Risk €0 → High Risk ROI in the first month

Cost calculations assume a mid-level developer at €80/hour (conservative industry average)

Do you have any questions?

I'm Juan Cruz Viotti, founder of Sourcemeta, member of the JSON Schema Technical Steering Committee, O'Reilly author, and award-winning University of Oxford alumnus.

I'd love to discuss how JSON Schema, OpenAPI, and Sourcemeta tooling can help you build world class APIs.

Industry leaders rely on our tooling

94% of developers in the API space know JSON Schema. Don't miss out
Sony logo KrakenD logo Octue logo Saleor logo GitGuardian logo Jülich Forschungszentrum logo Fingerprint logo Neon logo Veritone logo IT's logo

"This is definitely going to become an incredibly important reference library 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 this 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"

"Right now there is a big disconnect between ontology work and API work. This project has the potential to bridge that gap by making widely used ontologies available on JSON Schema"

Build in-house JSON Schema expertise

On-demand training: Master JSON Schema for OpenAPI

Learn advanced patterns, schema-first design, and production-grade techniques from a member of the JSON Schema Technical Steering Committee. 14 modules and over 9 hours of content covering the entirety of JSON Schema 2020-12, from basics all the way to dynamic references.

Buy the Video Course

Open Source

We maintain critical open-source projects for the JSON Schema ecosystem. Explore the full suite on GitHub.