Apps & Studio

Build the front end. Everything behind it is already there.

Apps on Jetstack are your own code (React, TypeScript, Tailwind) or configured screens. They run on your tenant and your domains, and share one core for data, sign-in, permissions and automations. Deploy as many as you need: hosting is included.

Studio documentation

www.acme.com

acmeServicesReferencesBlogContact

Heat, cooling and service that just runs.

Installed in a week. Serviced for years.

Get a quote

Case study: 40 heat pumps in 30 days

Let's talk

Name

E-mail

Message

Send

portal.acme.com

acme.K

Welcome back, Clara

Your projects

Heat pump installationIn progress

Annual serviceScheduled · 12 Nov

Documents

Contract.pdf Signed

Quote-0142.pdf Approved

Upload a document

crm.acme.com

Pipeline

⌘KMy leads

▲ 8%

▲ 2

14 d

▼ 3 d

New5

Clara Weiss

Website · today

Northwind

Referral

Qualified4

Orbit Labs

€24,000

Kestrel

€9,800

Proposal3

Tidewater

€41,500

3 apps · 1 core

Anatomy

An app is a front end, a few routes and a manifest.

The manifest declares what the app needs: its data types, roles, permissions, menu items, schedules and secrets. A deploy reconciles the tenant with it, and a rollback undoes it.

public/

The built front end, served from your tenant or your own domain.

server/

Small handlers in a sandbox, with the platform's Internal API.

jetstack.app.json

The contract: what the app owns, needs and may do.

1{
2  "manifestVersion": 2,
3  "name": "Website",
4  "compat": { "platformApi": ">=6" },
5  "access": { "visibility": "public" },
6  "viewport": "full",
7  "routes": {
8    "POST /contact": { "handler": "server/contact.php", "auth": "public" }
9  },
10  "schema": { "types": [
11    { "system_name": "lead", "name": "Lead", "properties": [
12      { "system_name": "name", "name": "Name" },
13      { "system_name": "email", "name": "E-mail", "data_type": "pEmail" }
14    ]}
15  ]},
16  "capabilities": ["records.write:lead"],
17  "limits": { "perIpPerMinute": 20 }
18}

Where apps live

Inside the back office, or on a domain of their own.

Inside the back office

An app opens from the menu within the platform's layout, next to configured views and dashboards.

The whole window

A full-window app draws its own navigation. Administrators get a floating system tray on top of it.

The home page

One app can claim the tenant's root address, so everyone lands in it after signing in.

A domain of its own

A website or portal on www.yourcompany.com, alone on that domain, with sign-in on the same domain.

Inside other screens

Widgets, value renderers, record actions and automation steps bring an app into the back office.

On another site

A website hosted elsewhere can call an app's public routes, with limits for every visitor.

Studio

Describe it. Watch it build. Ship it.

The Studio puts an AI app builder, a TypeScript-aware editor, a live preview and the app's problems in one browser window. Nothing to install and no build server: apps build right in the browser.

App builderdev

Add a booking page. Save requests to Reservations and notify the front desk.

Reading the data model

Writing src/pages/Booking.tsx

Adding route POST /bookings

Checking the build: no problems

App.tsxBooking.tsxMjetstack.app.json

1export function Booking() {
2  const slots = useSlots();
3  return (
4    <Card className="p-6">
5      <SlotPicker slots={slots} />
6      <Button onClick={request}>
7    </Card>
8  );
9}

building…

preview · /booking

An AI app builder that reads your data model and the docs
Fast refresh: changes appear without losing the page's state
Inspect: click an element in the preview, change its text and classes
Co-editing: people and the agent in the same file
Branches for experiments, merged back three ways
Problems from the build, the types, the browser and the server
A sandboxed preview, so drafted code never acts with your session
Publish when it's ready; every release keeps its history

Minutes from one request to a built app

Our own runs with the Studio's app builder, one request per case

Filtered invoice table

model cost $0.81

3.1 min

Booking page with a server check

model cost $0.65

2.5 min

Lead page with a form

model cost $0.53

2.2 min

Dashboard over existing data

model cost $0.49

1.6 min

Mortgage calculator

model cost $0.17

0.9 min

Fix a planted crash

model cost $0.07

0.5 min

Measured in October 2026 with Claude Opus 5.5 as the app builder, with no human edits. Every case built; two finished with problems still listed for review. Costs are model usage at list prices.

Shared services

Every app gets the platform's services for free.

Sign-in, search, notifications, background jobs and live events work the same in every app, so a full-window app can still offer a bell, a search box and a jobs list in its own design.

Sign-in & roles
Records & files
Full-text search
Notifications
Background jobs
Live events
AI assistant context
Translations

Extensions

Bring app features into the back office.

Widgets

An app's element on any dashboard canvas, with settings chosen in the canvas builder.

Renderers

A field's value shown through the app's own component, in every table and detail.

Record actions

“Generate contract” on a case: a button that runs the app's route, available to MCP too.

Automation steps

The app's logic as a step in the automation builder, with typed inputs.

Releases

Every deploy is planned, recorded and reversible.

Work happens in the app's draft, shared by the Studio, your editor and AI agents. Publishing makes an immutable release; deploying shows the plan first and records who did it. Rolling back is one step.

Draft

One working copy for people and agents

Release

Immutable, numbered, previewable

Plan

What it creates, changes or removes

Deploy

With a second person's approval, if you want

Rollback

One step back to the last good release

Already started?

Your prototype can move in.

Built something in Lovable, Bolt, v0 or Claude Code? Keep the front end. It becomes a custom app, while its database, sign-in and business rules move into the core, where they gain permissions, history and an API.

The prototype

Its own database and logins
Permissions in front-end code
Manual deploys, no history
Nobody on call

On Jetstack

Shared records and one sign-in
Rules enforced by the platform
Releases, environments and rollback
Operated and backed up for you

Hosting included

No per-app fees. No hosting bill.

Deploying and hosting apps is part of every tenant, with no per-app fee and no separate hosting bill. Build one app or twenty, internal or public, on our domain or yours.

Deploy and roll back as often as you need
Your own domains for public apps
Every app in development and production

Apps FAQ

Building apps, answered.

Which technologies can we use?

Studio apps use React, TypeScript, Tailwind CSS and shadcn/ui, built in the browser from an app kit with routing, forms, dates, charts, tables, toasts and animation. Apps built on your own computer can use any packages. Server routes run as sandboxed handlers, and an app can also bring its own service behind the platform's gateway.

Can a public website run on Jetstack?

Yes. A website is an app with public routes, served alone on its own domain. Its forms create records in your back office, and its content can be edited there.

Do apps need their own database?

No. Apps declare the types they need in their manifest and use the tenant's records, so data is shared across apps under the same permissions.

Who can deploy apps?

People with the Deploy apps permission. Production can require a second person's approval for every deploy, or accept changes only by promotion from development.

What happens when we delete an app?

Its menu items, schedules, credentials and service are removed. Its types, records and roles stay as ordinary configuration, so no data is lost.

Let's build

Bring an idea. Leave with an app.

Tell us what you'd like to build. We'll show you the Studio on your own use case.

A live build on your use case
What the core already gives you
A plan for the apps that follow