Skip to content
Jetstack

Your organization's own app platform

All your apps. One core.

Jetstack gives your organization one isolated platform for every app it runs. Build internal systems, client portals and public websites with AI or your own code, and run them all on one shared core: data, users, permissions, APIs, automations and AI agents. Hosting your apps is included.

See how it works
  • 6 years of development
  • An isolated tenant per customer
  • Hosted in the EU
  • App hosting included

Fits the tools your team already uses

  • React
  • TypeScript
  • Tailwind CSS
  • Vite
  • shadcn/ui
  • Claude
  • ChatGPT
  • Gemini
  • Claude Code
  • Cursor
  • VS Code
  • MCP
  • REST
  • Webhooks
  • Git
  • Google sign-in
  • Microsoft sign-in

The new bottleneck

AI made front ends cheap. Everything behind them is still hard.

Anyone can generate a good-looking app in an afternoon. Then come the questions that decide whether it can go live: Where does the data live? Who may sign in, and what may they see? How does it reach the rest of the business? Who runs it and backs it up? Answer them app by app and you end up with ten apps, ten databases, ten logins, and nothing that talks to anything.

CSVZapierExport

Jetstack core

1 database1 sign-inpermissions · APIs · automations · AI
CRM
Portal
Website
Field app
Reports
Customer stored 4 timesA login per appNightly CSV syncWho has access? Nobody knows.

Each app arrives with its own database, its own users and its own gaps.

The core

Everything behind the front end. Built once. Shared by every app.

Six years of engineering went into the core. Every app on your tenant plugs into it, so your twentieth app costs a fraction of your first.

  1. 01 · DATA

    Your data model, not a spreadsheet

    Types, fields and relations, modelled in the builder or declared in code. Queries, views, full-text search, files with signed links and comments, all on records every app shares.

    • Types & relations
    • Queries & views
    • Full-text search
    • Files

    Client

    type
    • nameText
    • vat_idText
    • owner→ User
    • projects→ Project[]
  2. 02 · IDENTITY

    One account across every app

    Users, groups and roles, with sign-in by password, magic link, Google or Microsoft, plus two-factor authentication. People sign in once and every app knows who they are.

    • Google & Microsoft
    • Magic links
    • Two-factor
    • Groups & roles
    GContinue with Google
    Continue with Microsoft
    E-mail me a link
    2FA · 482 117
  3. 03 · PERMISSIONS

    Rules that hold everywhere

    Decide who sees and does what, down to a single field and a single record. “Cases I own” is a rule the platform enforces in every screen, API and agent, not code each app repeats.

    • Role-based
    • Field-level
    • Record-level rules
    • Explain access
    RoleClientcan editCasewhereowner = signed-in user
    list ✓edit ✓delete ✕
  4. 04 · APIS

    An API for everything, from day one

    A REST API, an MCP server for AI clients, webhooks and a browser SDK, all generated from your model and guarded by the same permissions.

    • REST
    • MCP
    • Webhooks
    • SDK
    GET/api/v1/collection/case
    POST/api/mcp · tools/call
    webhook· case.updated
  5. 05 · AUTOMATIONS

    Work that runs itself

    Triggers, schedules and visual workflows with branching, code steps and AI steps. They fire on every write, whether it comes from a form, an app, an API call or an agent.

    • Triggers
    • Scheduler
    • Code steps
    • AI steps
    Case created
    Assign by region
    Notify owner
  6. 06 · MESSAGING

    Reach people where they are

    E-mail, SMS, push notifications and live events, with templates and history. Development environments never message real people.

    • E-mail
    • SMS
    • Push
    • Live events
    E-mail sent · Proposal
    Push · Visit tomorrow 09:30
    SMS · Your code is 482 117
  7. 07 · INTEGRATIONS

    Connected to everything else

    Connectors to outside services keep their credentials encrypted and work from automations, apps and agents alike. Agents can also use any external MCP server.

    • Connectors
    • External MCP
    • Web requests
    • Secret store
    Google Drive
    SharePoint
    Payment gateway
    Any MCP server
  8. 08 · AI AGENTS

    Agents that work like colleagues

    Agents with their own instructions, tools and identity, working on the same data and under the same rules as everyone else.

    • Assistants
    • Builders
    • MCP tools
    • Approvals

    Ava · Sales assistant

    • Reads: leads, e-mails
    • Asks before writing

Apps

Then build any front end on top.

Each app is your own code (React, TypeScript, Tailwind) or a configured screen. Put it inside the back office, give it the whole window, or give it a domain of its own. Deploy as many as you need: hosting is part of the platform, not an extra bill.

crm.acme.com

Systems shaped exactly to how your team works

CRM, case management, approvals, planning, ERP add-ons. Built fast, changed often, never forked into another silo.

  • Roles and field-level permissions from day one
  • Boards, tables, calendars and dashboards: configured or coded
  • Automations run on every change
crm.acme.com

Pipeline

⌘KMy leads

42

▲ 8%

9

▲ 2

14 d

▼ 3 d

New5

Clara Weiss

Website · today

Northwind

Referral

Qualified4

Orbit Labs

€24,000

Kestrel

€9,800

Proposal3

Tidewater

€41,500

Hosting included. No per-app fees and no separate hosting bill: build one app or twenty on the same tenant.

Explore apps & Studio

Build

Build with AI. Your way.

In the browser, in your own editor, from any AI client, or without code. Every route ends in the same place: a versioned app on your core.

In the browser

Studio

Describe the app and watch it build. An AI app builder, a TypeScript-aware editor, a live preview and the app's problems in one window. Nothing to install.

≈1 s

from edit to live preview

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
~/acme

❯

In your editor

CLI & workspace

One command connects a git workspace to your tenant. Claude Code, Cursor or VS Code scaffold apps, deploy to development and show you the plan before production.

AI client/api/mcp/builder

Give the ERP integration read-only access to invoices and customers.

builder_apply mode: "check"

◆ 3 changes: role erp_readonly, invoice.read, customer.read

builder_apply mode: "apply" expect: "a91f…"

✓ Applied · recorded in history

From any AI client

MCP builder

Connect Claude, ChatGPT or Cursor. Agents can configure what the builder screens can (roles, permissions, forms, automations, apps) and always check before they apply.

Client

Add field
NameText
VAT IDText
OwnerUser

Without code

Visual builder

Data models, forms, views, dashboards and automations, built by clicking. The way Jetstack has always worked, and still first-class.

Configuration and code are not rival modes. They meet in the same core: mix them per app, or per screen.

In practice

One tenant runs the whole company. And its website.

A day at Acme, where every app sits on the same core. There is no integration project anywhere on this list.

  1. 09:12www.acme.com

    A visitor sends the contact form

    The website is a public app on Acme's own domain. Its form calls a rate-limited public route.

    Public route

    01
  2. 09:12crm.acme.com

    The lead is already in the pipeline

    No sync, no Zapier: the form wrote into the same records the sales team works with.

    Shared records

    02
  3. 09:13Automation

    Petr gets it on his phone

    An automation assigns the lead by region and sends a push notification.

    Automation + push

    03
  4. 09:20Agent Ava

    A reply is drafted, then approved

    Ava drafts a follow-up from the lead's history and waits. Petr reads it and clicks Run.

    Confirm before write

    04
  5. 14:05portal.acme.com

    The client gets a portal

    The contract is signed. Clara signs in to the portal and sees her project, and nobody else's.

    Record-level permissions

    05
  6. 16:30Back office

    Marketing publishes a case study

    Written in the back office, live on the website a moment later, because the article is just another record.

    Content as records

    06

AI agents

Agents with a job description. And a permission boundary.

Give each agent a personality, instructions and the tools it may use: your data, any external MCP server, outside web APIs. Every agent acts as its own user, so it sees exactly what its role allows. Run it in the back office, inside your apps, in automations, or from Claude and ChatGPT.

  • Claude, GPT or Gemini, with your own keys
  • Assistants work with records; builders build apps
  • Asks before it writes, when you want it to
  • Every step visible in the conversation
More about agents

Ava

Sales assistant

Personality
Warm, brief, never promises discounts.
Model
Claude
Acts as
ava@acme.com · role Sales
Tools
CRM recordsCalendar (MCP)Web requests
Writes
Asks first
run · lead #1042working

    Production discipline

    Move at AI speed. Keep production boring.

    Every tenant comes as a pair: development, where people and agents build, and production, which only gets what was tested. Every change, whether clicked in the builder, written by an agent or pushed from git, lands in one history you can compare and restore.

    Development + production

    Two isolated environments for every tenant. Development never e-mails real people.

    One change history

    Who changed what, from where, and when. Compare any two states; restore any of them.

    Promote in one step

    Configuration and every app's tested release reach production together.

    Approvals

    Require a second person for deploys, or lock production so it changes only by promotion.

    Sandboxed previews

    Code an agent wrote runs in a preview without your session until you've looked at it.

    Test as each role

    Throwaway test users check what every role can see and do before anyone else does.

    DevelopmentProduction
    Production policyOpenReviewedLocked

    1. Studio agent

      website · booking page added

      10:42dev

    2. Petr · builder

      field client.vat_id added

      11:05devRestore

    3. CLI

      crm v34 deployed

      11:20dev

    4. MCP

      role support · tickets.read granted

      11:31dev
    Promote to production

    Your tenant

    Your own tenant. Nothing shared with anyone.

    Each customer runs in environments of its own: their own application container, database, cache, private network and file storage. Someone else's heavy report can't slow you down, and your data never sits next to anyone else's.

    Hosted in the EUYour data stays in the European Union.
    Backed up dailyDatabases and files, with a final archive before anything is retired.
    Zero-downtime releasesPlatform updates roll out environment by environment, without interrupting work.
    Your data, always exportableEvery record and the full database schema, in standard formats, at any time.
    Serious sign-inGoogle and Microsoft sign-in, magic links and two-factor authentication per role.
    Audit trailAn event log of who did what, plus the full history of every configuration change.
    crm.acme.comwww.acme.comportal.acme.com
    Your tenant

    Production

    • App container
    • Database
    • Cache
    • Files
    • Private network

    Development

    • App container
    • Database
    • Cache
    • Files
    • Private network
    Other tenants
    of building and running the platform

    6years

    of building and running the platform

    behind every app

    1core

    behind every app

    per tenant: development and production

    2environments

    per tenant: development and production

    extra fees for hosting your apps

    0

    extra fees for hosting your apps

    Where Jetstack fits

    Not another app builder. The place your apps live.

    The quickest way to understand Jetstack is to put it next to what teams usually reach for.

    AI app generatorsSaaS toolsCustom buildJetstack
    Many apps on one shared databaseOne app, one databaseOne silo per toolIf you build itBuilt in
    Users, roles, field- and record-level permissionsYou bolt them onBasic, per toolYou build themBuilt in
    Front ends designed exactly your wayYesNoYesYes
    Development & production, history, approvalsRarelyNoYou set it upEvery tenant
    AI agents inside permission boundariesNoLimitedYou build itBuilt in
    Who runs the infrastructureYouThe vendorYouWe do
    Hosted in the EUVariesVariesYou arrange itYes
    A team that can build it with youNoNoYour hiresYes

    Ways to work with us

    Build it yourself. Build it with us. Or let us run it.

    Self-serve

    Build it yourself

    Get a tenant, open the Studio or your editor and ship. Docs, CLI, MCP and our support whenever you need it.

    Developer guide
    Together

    Build it with us

    Your team and ours in one workspace. We set up the core and the hard parts; you build the apps you know best.

    How we work

    FAQ

    Questions, answered.

    What exactly is Jetstack?

    A platform your organization gets as its own isolated tenant. It provides the core every business app needs (data, users and sign-in, permissions, APIs, automations, messaging, integrations and AI agents) and hosts any number of apps on top: internal systems, client portals, public websites and AI agents.

    Is app hosting really included?

    Yes. Deploying and hosting your apps is part of the platform, with no per-app fee and no separate hosting bill. Build one app or twenty on the same tenant.

    Do we have to code?

    No. You can build in the visual builder, let the Studio's AI agent write the app, or have our team deliver it. When you do want code, it is standard React and TypeScript in your own git repository.

    Can apps run on our own domains?

    Yes. Your back office can live on crm.yourcompany.com and your website or client portal on a domain of its own, all on the same tenant and on the same data.

    Which AI models can we use?

    Agents run on Claude, GPT or Gemini with your own provider keys. Any MCP-capable client (Claude, ChatGPT, Cursor, Claude Code) can connect to your tenant with a specific user's permissions.

    Where is our data, and can we take it with us?

    Tenants are hosted in the EU, isolated from each other and backed up daily. You can export all your data, every record and the full database schema, in standard formats at any time.

    We already have a prototype from Lovable, Bolt or Claude Code. Can it move here?

    Usually, yes. The front end becomes a custom app; its database, sign-in and business rules move into the core, where they gain permissions, history and an API. We can do the move with you.

    How is Jetstack priced?

    Per tenant, with no per-app fees. The platform fee covers hosting, operations, updates and support; delivery work by our team is quoted separately. Tell us what you're planning and we'll put a proposal together.

    How long does it take to go live?

    A focused app can be live in days. A complete system with integrations and data migration typically takes a few weeks.

    Let's build

    Start with one app. Grow into a platform.

    Tell us what you want to build: a portal, a back office, a website, an agent. We'll show you how it would run on Jetstack.

    • A demo on your own use case
    • An honest answer about fit
    • A clear proposal and timeline
    What is it about?

    We use your details only to answer you. Privacy policy

    Tell us what you want to build

    A portal, a back office, a website, an agent, or something you have already started. We'll get back to you shortly.