Developer portal
How the platform works, in detail
Architecture, operational guides and ready-to-run API examples — the same documents the team maintains in the repository, rendered through the site.
01
System architecture
How a single canonical schema definition drives persistence, validation, the admin panel, API, permissions, and events.
23 sections
02
Knowledge base
Practical step-by-step instructions — from a new model to promotion to production.
29 sections
03
API Cookbook
Ready-made examples for REST, JSON:API, GraphQL, forms, webhooks, and the SDK.
17 sections
04
Field Type Matrix vs. the Market
A comparison of our catalog of 56 field types against Strapi, Contentful, Sanity, Payload, Directus, Hygraph, and Contentstack — with a list of real gaps.
6 sections
05
Technical documentation (system design)
A complete system overview for review — stack, frontend and backend layers, patterns, security boundaries, data model, testing, and deployment.
13 sections
06
Marketplace & extensions architecture
How third parties build, publish, review, install and monetise declarative extensions without ever running code inside the platform.
10 sections
07
PIM design patterns
The five classification-bridge and polymorphic-choice patterns, how each is expressed in this platform, and where the configurator logic runs.
9 sections
Read next
Related reading
Continue with the articles and scenarios that build on this document.
- Schema-driven architecture: one definition, every artifactWhy a single canonical schema definition should generate persistence, validation, admin UI, REST, OpenAPI, GraphQL and permissions instead of each being written by hand.Article
- Generating REST, OpenAPI 3.2 and GraphQL from the same registryA walkthrough of how the published schema registry produces a consistent query language across REST, JSON:API and GraphQL, with an OpenAPI document that can never fall behind.Article