AUTOTABLE / SCHEMA-DRIVEN BACKEND
Model your data. Get a working backend.
Define containers and fields in Tenant Panel, use the resulting REST routes, and connect workflows and interfaces around the same project.
ACTUAL TENANT PANEL UI
SAMPLE DATA
Actual Tenant Panel with sample workspace data. Desktop shows collections; the mobile capture shows project selection.
FROM DEFINITION TO A WORKING REQUEST
A model with a clear contract.
Create a container, choose its field rules, and send JSON that follows that definition.
01 / DEFINE THE FIELDS
Give orders the fields they need.
{
"schemaName": "orders",
"fields": [
{"name":"orderNumber","type":"string","tag":"required"},
{"name":"status","type":"string","enumList":["draft","paid","shipped"]},
{"name":"total","type":"float","tag":"required"}
]
}Example field definition, shown as JSON. Configure the corresponding fields and route policy in Tenant Panel.
02 / USE THE PROJECT API
Create an order over HTTP.
POST /api/v1/{tenantSlug}/{projectSlug}/dynamic?schemaName=orders
Content-Type: application/json
Authorization: Bearer YOUR_AUTHORIZED_TOKEN
{ "orderNumber": "A-1042", "status": "draft", "total": 184.5 }The active container definition supplies validation. The route policy determines who may call this operation.
CONFIGURE THE BOUNDARIES
Start with one vertical slice.
Keep the first model small enough to test from configuration to interface.
01
Choose a tenant and project.
Use Tenant Panel to create or open the project that owns the application data and configuration.
02
Define a container and its access rules.
Add typed fields and validation. Review active routes, authentication requirements, and authorized roles before using records.
03
Make a request, then connect the next layer.
Create and read a test record. Add a workflow for behavior, a pipeline for a data view, and your preferred frontend for the experience.
FROM DEFINITION TO EXPERIENCE
Every layer has a clear role.
AutoTable runs the data operations and logic. Tenant Panel configures the project. Ozmishow presents the experience.
THE CONNECTED PRODUCT STACK
One model. Every layer connected.
01 / Your data model — containers, fields, and validation.
02 / AutoTable — dynamic APIs, workflows, and pipelines.
03 / Tenant Panel — configure your project and access rules.
04 / Ozmishow — compose the connected experience.
YOUR NEXT STEP
Build one model. Make one real request.
Follow the orders quickstart, then extend the model with the behavior your application needs.
From a data model to a working product.
A connected foundation for the things you want to build.