App Studio
Apps built on the database you already run.
Desktop, installable PWA and native mobile, from one description.
The same pipeline that turns your schema into CRUD endpoints keeps going and builds the app on top of them. Describe the screens in English — lists, forms, detail views, filters — and each surface is generated from that one description. 15 databases and 5 file formats, supported out of the box.
data → api → mcp → app
From table to shipped app.
The app is built against your real data from the first draft, so what you see on screen is what your users will see.
Point at your data
Postgres, MySQL, ClickHouse, MariaDB and 11 more, cloud or local — or CSV, Parquet, XLS, JSON and NDJSON. The connection runs outbound-only, and nothing is copied out to build against.
APIs appear
Create, read, update and delete on every table, view and materialized view — live in about five seconds. For logic beyond CRUD, describe it in English and have it done in under five minutes.
MCP comes with it
The same data is reachable by agents as well as people, over OAuth, with no second integration to build later.
Describe the screens
Say what the app should do. Lists, forms, detail views, filters — in the words you would use explaining it to a colleague.
Ship it
Desktop, installable PWA and native mobile, all from the one source you just described.
What’s never lost. Every call the app makes through APIs, MCP and Custom API is logged, with traces exportable to any OpenTelemetry collector on self-hosted — Jaeger included. Every change to an org, project, Custom API, module or space is versioned, so an admin can roll back a dangerous one with a click.
What you can’t do. Authentication for your own users, third-party integrations, and logic that has nothing to do with your database. That work stays yours to build, manage and maintain.
Three surfaces, one description.
One description, generated three times. The surfaces differ in density and input, not in what they can do.
Desktop
A full browser application for the people who live in it all day, with the density that implies.
Installable PWA
Installs from the browser, opens like an app, works on any machine without a store review.
Native mobile
A real native mobile build for people working away from a desk.
What you stop having to build.
Each of these ships with the app rather than in the quarter after it.
It drops in.
A layer over the infrastructure you already run, on trusted sub-domain architecture. APIs, desktop apps, websites, web apps and mobile apps, without writing code.
30× is a stopwatch reading.
One hundred thousand tables across ten databases, configured as a single project. At thirty seconds on the wall clock, CRUD was live on every one of them — a table’s endpoints appear the moment it finishes indexing.
The URL is the query.
Query parameter support deep enough that complex reads, and bulk create, update and delete, are a matter of constructing a URL. That is roughly 90% of what an API project turns out to be. Deep AI integration covers the rest.
SaaS, or your own metal.
Run it as a hosted service or take a licence and deploy it on-premise.
Fifteen engines, five file formats.
Supported out of the box, so the app is built on the database you already have.
Rewind the whole system.
Automatic versioning of every artifact. Going back to any last known good state is a few clicks.
Build from wherever you are.
Connect Claude, Cursor, VS Code, Codex, Windsurf, Cline and Gemini to your setup.
Identities, not API keys.
Permission roles that restrict who reaches which part of the system, defined in a simple UI.
It reaches your people.
Slack, Teams, Google Chat, Discord, Mattermost, PagerDuty, Opsgenie, email and your own webhook, out of the box.
The short answers.
Is this a prototyping tool?
No. It builds against your production database from the first screen, and the APIs underneath are the same ones you would call from anywhere else. There is no separate step where you rebuild it for real.
How is this different from Agent Studio?
Same pipeline, different ending. App Studio produces something a person opens; Agent Studio produces something that works on its own. Many teams run both on the same data.
Who is it for on my team?
Whoever understands the job. The description is in English and the data connection is a UI, so the person who knows what the app should do can be the person who builds it.
Which databases work?
Fifteen engines tested, including ClickHouse, Postgres, MySQL and MariaDB, plus flat files like CSV and Parquet. Whatever you already run is most likely already supported.
See it work on your own data.
Book a session and we build one screen together against your database — or ours, if you would rather not bring your own yet. You leave with a working app, not a slide about one.