TSQL.APP — the application layer your database was missing
A metadata-driven framework that renders a complete, secure, multi-user business application directly from SQL Server. If you can write T-SQL, you can build and change the application.
The idea
Most business applications keep the data model in one place and the application in another. Two languages, two release cycles, two teams, and a permanent gap between them.
TSQL.APP closes the gap. The application definition lives in a metadata database alongside the business data. One row in api_card is one screen. Rows in api_card_fields are its columns. Rows in api_card_actions are its buttons, and each button is a T-SQL script. The framework reads all of it at runtime and renders the UI.
The result: the people who understand the data — who already write the queries, the views, the stored procedures — are the people who build the application.
What you get out of the box
- Screens from views. Point a card at a table or view and it becomes a working list-and-form screen with sorting, filtering, search and pagination.
- Buttons that run T-SQL. Any stored procedure or script can become a button on any screen, with keyboard shortcuts.
- Interactive dialogs in T-SQL. Multi-step modal dialogs — inputs, date pickers, record pickers, data grids, toasts — written as ordinary stored procedures.
- Parent–child navigation. Model real relationships: an order and its lines, a shipment and its registrations, a customer and its invoices.
- Role-based access control. Read, create, update and delete permissions expressed as SQL conditions, per screen, per button, per relationship.
- Scheduled background jobs. Any T-SQL batch can be queued and scheduled without leaving the platform.
- REST endpoints. Publish a query as a paginated JSON GET endpoint for dashboards, integrations and front-end applications.
- Excel and print output. Grids export to Excel and print without extra work.
Who it's for
Organisations with a serious SQL Server estate and business logic already living in the database. Teams whose operational reality changes faster than a conventional release cycle can follow. Companies replacing a sprawl of Access databases, spreadsheets and one-off tools with something governed and auditable.
Where TSQL.APP is not the right answer
TSQL.APP is built for internal, data-dense operational applications on SQL Server. It is not a consumer-facing app builder, not a public website CMS, and not a fit if your data doesn't live in SQL Server. We'll say so in the first conversation rather than the third invoice.
Talk to the team that builds on it every day
Prefer to explore first? static.tsql.app ↗ has more examples, documentation and technical resources.