Screens over your APIs, for the people who only use them.
An app is an item in a project that turns its requests into screens: fields, tables, cards, charts, buttons. The operations desk, the support team, the person at the plant who needs one number and one button — they open the app full screen and never see a request. A runner seat sends exactly what the app sends and nothing else, and the backend makes sure of it.
At a glance
Built over the project's requests. Run by people who never see one.
An app lives in a project and calls only that project's requests. In the designer its screens are cards on a 24-column grid — Input, Table, Card, Text, Button, Chart, Number — dragged and sized with no overlap, and the links between them drawn as you pick one: a field feeds its button, a button fills its cards.
In a runner's seat the same app opens full screen, with an Applications dropdown and a toolbar that holds the licensed-to line, change password and log out. Behind it the backend sends exactly what the app sends — each request as stored, changed only where the app's own run fills it — and refuses the rest.
FlowsStart from the request, or from the whole project.
A new screen asks "what does it call?" and builds a field for every unfilled variable and a table or a card from the answer's shape.
A whole app in one step.
A container per folder, a screen per request — up to 80 — and a Home dashboard. With an OpenAPI document attached, enums become choices, ids become dropdowns of the related list, and passwords and secrets become hidden fields.
Dashboards, grouped by what repeats.
Number cards and charts, grouped by a field that repeats in the answer. Auto-refresh. Export the table under a chart.
Settings, once for the app.
A pinned environment, a start screen, inputs logged or not, a brand colour and a logo. Screens refresh every 5 seconds or more. Hidden screens open only from other screens.
Or ask Themis for it.
Themis creates the app, its containers and screens, a dashboard, a watcher, a function — and tries them before handing them over.
Functions kept with the app. Writes only on purpose.
Functions are kept with the app, in JavaScript, Go or Python. app.call runs a request of the project, app.publish sends to a broker or writes a device tag, app.read reads tags now — and the function can say, notify, go to a screen, open a popup or keep a value.
A write happens only from a button a person pressed, or from a watcher allowed to send changes. Beside it, the function behind a Refund button.
A seat that runs apps and nothing else.
An app runner is a user whose only permission is "Run apps", with the apps ticked. The boundary is in Go, and a test fails the build if a new window binding is neither guarded nor on the allow list.