Introduction
Polymesa is a business app development platform. You model your data as related tables, and the platform gives you the application around them: interfaces, workflows, automations, and reporting, on top of a real PostgreSQL database.
What you get
Section titled “What you get”A real database. Entities are provisioned in PostgreSQL. Your data stays queryable with any tool that speaks SQL — no proprietary export step.
TypeScript, not a builder. Business logic is code: typed classes, generated entity definitions, SQL that fails to compile when you rename a column. No drag-and-drop canvas that becomes a ceiling.
Interfaces per audience. Ops get a dashboard, finance get reports, customers get a portal — all reading the same underlying tables.
Access control that holds. Sharing is enforced with PostgreSQL row-level security, so a bug in a controller cannot leak rows the caller may not see.
How it fits together
Section titled “How it fits together”| Layer | What it is |
|---|---|
| Entities | Your tables and fields |
| Guest code | Triggers, jobs, controllers, views — TypeScript you write |
| Pages | Custom React views attached to entities |
| Automations | Trigger-driven logic tied to record changes |
| Sharing | Row-level rules governing who sees what |
| CLI | Moves all of the above between workspaces |
Everything except user accounts is configuration: retrievable to a directory, committable to git, deployable to another workspace.
Who it is for
Section titled “Who it is for”Teams replacing spreadsheets, shared inboxes, and manual handoffs with something that has a schema — but who do not want a six-month engineering project, and do not want to be trapped by a no-code tool at month seven.
You should be comfortable with SQL and TypeScript. The platform removes the infrastructure, not the programming.
Where to go next
Section titled “Where to go next”- Quickstart — install the CLI and deploy something
- Core concepts — the model worth understanding first
- Runtime overview — what your code can do