SDCStudio
Every system that touches your data reads it a little differently, and every handoff between them needs a mapping someone has to build and keep up. SDCStudio helps your own experts define what your data means, once, and turns that definition into records every system can check.
What it costs you now
Handoffs
A partner, a new system, a merger: each one starts with meetings about what your fields mean, then code to translate them, then upkeep every time either side changes.
People
What a status code means, which unit a column is in, why a value is missing. When the person who knew moves on, the data keeps flowing and the meaning does not.
AI
An LLM reading your tables infers what the columns mean. Sometimes it is right. You cannot run a business on sometimes.
Lock-in
When your data model is built inside a vendor's product, it stays there. You rent the meaning of your own business.
Where we come in
Most of your model is already built.
The published component libraries cover the concepts businesses and governments share: parties, addresses, orders, invoices, clinical measures, and more. Reusing them is free.
You decide what it means.
AI proposes relationships and drafts definitions. A domain expert on your side corrects them and signs off. The expert authors the model; the machine does the typing.
You own the result.
Everything is in open standards, in your own store, with no private format. Check our work without trusting us: the validator is open source and runs offline.
The plan
1
Start from what you have
Upload a CSV or a Markdown template, convert a paper or PDF form, let an agent read the structure of your databases, or start from nothing in the visual editor.
2
Reuse first, then fill the gaps
Everything already published is reused at no cost. AI drafts only what is new, and your expert decides. Publish, and the model can never change or go missing.
3
Put it to work
Generate the schemas, the documentation and an application from the published model. Every record it produces is a Governed Data Record, bound to its meaning and checked before it is accepted.
What changes
A new partner reads your model, not your mind.
They fetch the published model and check your records against it. The mapping meeting becomes a link.
Your AI reads definitions instead of guessing.
An agent can look up what every field means and what it is allowed to be, and refuse what does not conform.
A record made today means the same thing in ten years.
Published models never change, so the meaning does not drift when people, systems or vendors do.
When it matters, you can prove it.
Settle an exchange through the Verifiable Settlement Layer and any counterparty can verify the Receipt offline.
Pricing
Buy credits and spend what you use. Reuse costs nothing, which is deliberate: the catalog only gets cheaper for everyone as it grows.
Browse the catalog
Free
Explore published reference models and reuse existing components at no cost. Download schemas and validate locally with the open-source validator.
Build models
Pay as you go
Mint new components and assemble data models. Reusing catalog components stays free. You pay when AI creates something new, or when you publish a finished model.
Settle in production
$1.00 per Receipt
Issue a Settlement Receipt through the Verifiable Settlement Layer: the Governed Data Record validated against its published model, the governance decision recorded, the Receipt signed and bound to both parties. 1,000 credits per Receipt. Verifying one is free, with no account.
For your architects
Standards
The Semantic Data Charter reference model (SDCRM, Apache 2.0) on W3C XML Schema 1.1, with RDF, OWL and SHACL, aligned to BFO (ISO/IEC 21838-2). No private format. Standards compliance and the BFO alignment.
Outputs
From one published model: XSD schema, XML and JSON record templates, JSON-LD, RDF, SHACL, GQL and HTML documentation, plus a generated Django application or a Supabase kit for your own TypeScript app.
Agents and API
The open-source sdcmodeler client and MCP server let any agent search the catalog, estimate, build and publish a model. The public catalog API needs no account.
Validation
Every record validates against its published schema with the open-source sdcvalidator, Apache 2.0. Run it locally, offline, with no account.
Security posture
Read from the code and the deployment, kept in a cryptographic inventory, and stated here so a security questionnaire can start from facts rather than from a form.
Transport
TLS 1.2 minimum on the load balancer in front of the service, with hybrid post-quantum key exchange (X25519MLKEM768) negotiated whenever your client offers it, since 9 October 2026. Traffic between the service and its database, cache, storage and key management stays inside Google Cloud on its internal TLS.
Signing
Every Settlement Receipt and practitioner credential carries two issuer signatures over the same digest: ES256 from a P-256 key held in a Cloud KMS hardware security module, and ML-DSA-65 (FIPS 204, post-quantum) from a second Cloud KMS key, software-held because that is the only level Cloud KMS offers for it. Both must verify. Every key ever used stays in the published key document.
Data
The database, cache, uploaded files and secrets use Google-managed encryption at rest. We never see a card number: Stripe collects and holds payment details and we keep a reference. Secrets are injected at deploy from Secret Manager, never stored in an image or a repository. Rendering a page makes no request to a third party; the typefaces ship with the application.
What we do not claim
No customer-managed encryption keys today. No third-party certification; the controls above are stated as built, not as audited. Verification of anything we sign needs no account and no call to us: the verifier is open source and the keys are published.
Browsing the catalog is free and needs no account. See how much of your model already exists.