Build the backend and interface as one connected system.
Define typed data once, then shape secure routes, automation, aggregation, and editable interfaces around the same project context.
TYPED SCHEMAS
DYNAMIC ROUTES
AUTOMATED WORK
PROJECT / COMMERCE
One model. Every layer.
CONTAINER
orders
customerId · status · total · createdAt
API
POST /dynamic
WORKFLOW
after_create
PIPELINE
revenue_by_status
INTERFACE
orders dashboard
HOW AUTOTABLE FITS TOGETHER
From schema to working product.
Start with an orders container and carry one typed model through the backend, automation, and interface.
Each layer stays connected to the same tenant and project, so the application can grow without rebuilding its foundation.
01 / DEFINE CONTAINERS
Describe the data.
Create an orders container with typed fields, validation, indexes, and access rules.
02 / USE DYNAMIC ROUTES
Work with records.
Create, filter, update, export, and execute against the schema through project-scoped endpoints.
03 / ADD WORKFLOWS AND PIPELINES
Automate the behavior.
React after_create, schedule recurring work, and aggregate revenue without disconnecting business logic from data.
04 / CONNECT AN INTERFACE
Ship the experience.
Use the same project data in an editable Ozmishow page, an internal tool, or your own application.
TENANT PANEL / BACKEND CONTROL
Shape the system from one project workspace.
Tenant Panel is where developers define containers and fields, set validation, configure authentication and access rules, and manage project settings.
✓ Model typed records and relationships
✓ Control routes, roles, and authentication
✓ Keep configuration scoped to the active project
Replace with Tenant Panel screenshot
EDITABLE PREVIEW
Future screenshot area · Replace only the image source and keep this application frame.
Replace with Ozmishow screenshot
EDITABLE PREVIEW
Future screenshot area · The image remains independently selectable in the visual builder.
OZMISHOW / INTERFACE BUILDER
Turn project data into an editable experience.
Build pages and reusable sections with visual editing while each component can stay connected to AutoTable-backed content.
✓ Compose responsive pages from reusable sections
✓ Edit content, media, layout, and presentation visually
✓ Connect the interface to project-scoped AutoTable data
AUTOMATION AND DATA ENGINE
The behavior around your data is part of the product.
Use project-aware building blocks to move from validated records to reliable application behavior.
Each capability works from the same schema context, keeping queries, automation, permissions, and interfaces aligned.
01 / DYNAMIC ROUTES
Operate on typed records.
Create, filter, update, delete, export, and execute against the schemas enabled for a project.
02 / WORKFLOWS
Coordinate business behavior.
Validate a change, branch by record state, update related data, or hand work to an outbox phase.
03 / PIPELINES
Shape application-ready results.
Filter, join, group, calculate, and project records for dashboards, reports, and downstream steps.
04 / SCHEDULED OPERATIONS
Run recurring work deliberately.
Use cron-triggered workflows for cases such as reviewing overdue items or preparing a daily work batch.
05 / NOTIFICATIONS
Turn events into messages.
Create notifications from workflow-controlled events without mixing delivery concerns into record validation.
06 / TENANT AND PROJECT ISOLATION
Keep every request in context.
Resolve schemas, roles, workflows, and runtime data inside the active tenant and project boundary.
START WITH A REAL REQUEST
Your schema is already an application boundary.
Send an orders record through the project-scoped dynamic route. AutoTable applies the container's field rules, authentication, authorization, workflow lifecycle, and response handling around the request.
Change the schema definition as the product evolves; the route stays connected to that model.
HTTP / CREATE ORDER
PROJECT-SCOPED
POST /api/v1/{tenantSlug}/{projectSlug}/dynamic?schemaName=orders HTTP/1.1
Authorization: Bearer <access-token>
Content-Type: application/json
{
"customerId": "cus_1042",
"status": "paid",
"total": 184.50,
"currency": "USD"
}Typed validation and configured workflow behavior run inside the selected tenant and project.
adamsin
Now that you know the basics of AWS, you should be able to deploy your application to AWS. You don’t need to use all the AWS services, here is what you can probably get started with:
