zokl reads your model live and materializes everything around it — the data store, a polished admin console, search and APIs, published websites, commerce, automations. Change the model, and the app changes with it.
Currently invite-only · zokl.ioWrite your entities, fields, relationships, and rules — or start from an industry standard. Versioned, machine-readable.
The runtime interprets it live: data store, admin console, search, APIs. Purpose-built, because your opinions live in the model.
Build customer-facing websites visually and ship them at your-name.zokl.site — commerce and payments included.
Lifecycle automations run your rules; HAL runs your requests. Change the model any time — the whole app follows.
Nothing is scaffolded. One intelligent engine reads your model live — upload a music-publishing model and a project-management model, get two different working apps from the same platform.
The model carries presentation and behaviour intent, so the result feels purpose-built — never a generic spreadsheet-with-forms.
HAL can do anything a user can — author the model, build the website, run imports — conversationally, with the same permissions and audit trail.
Data, admin, published multi-tenant websites, commerce, automations — not a database with an API. Enterprise-grade underneath: industry standards, tenant isolation, versioned models.
zokl is invite-only while we onboard the first industries. Tell us what you'd build.