schema to running server
From a single schema file to a running server with REST endpoints, a browser UI, and AI tooling. No glue code in between.
v0.4 — schema-driven
One schema file generates the server, browser UI, AI tools, and REST API. Works with existing databases or net-new.
# schema.mmdentity User {id uuid @primaryemail string @uniquename string?createdAt datetime @default(now())}entity Project {id uuid @primaryownerId uuid @refs(User.id)name string @min(1) @max(120)}
01 / cycle
A single schema drives the server, the database adapter, and the import pipeline. Edit it, regenerate, and the rest follows.
s2ai.face · s2ai.genius · s2ai.import · s2ai.builder
02 / capabilities
schema to running server
From a single schema file to a running server with REST endpoints, a browser UI, and AI tooling. No glue code in between.
Import an existing database or start from a fresh schema. Same pipeline either way.
One file drives server, UI, AI tools, and API docs. No drift.
PostgreSQL, MongoDB, MySQL, SQLite, Excel, Elasticsearch — connected at the same time.
OpenAPI-compliant interfaces with identical shape across every resource.
Rules defined once. Enforced at the server, the UI, and the type system.