Platform

The core every app stands on.

Six years of engineering in one platform: data, identity, permissions, APIs, automations, messaging, integrations and AI. Isolated per customer, operated for you, and shared by every app you build.

Read the docs

01 Data02 Identity03 Permissions04 APIs05 Automations06 Messaging07 Integrations08 AI agents

Capability map

Everything a business app needs. Already running.

The parts every serious app ends up building, built once and kept running, so your apps only add what makes them different.

Data

Model your business, not tables.

Types and relations, with two dozen field types: text, money, dates, files, locations, nested data
Queries with filters, grouping and calculations
Tables, boards, calendars, cards and dashboards
Full-text search over what each person may read
Files and images behind short-lived signed links

Identity

People, and the way they sign in.

Users, groups and roles
Password, magic link, Google and Microsoft sign-in
Two-factor authentication, required per role
API keys and OAuth for integrations and AI clients

Permissions

Who may see and do what.

Nothing is visible until it is granted
Grants per type, action and field
Record-level rules such as “cases I own”
One check for screens, REST, MCP, apps and agents

APIs

Every surface, from day one.

A REST API generated from your model
An MCP server for records and an MCP builder for configuration
Webhooks in and out
A browser SDK and a server SDK for apps

Automations

Business logic without a backend team.

Triggers on records, buttons, forms and webhooks
Scheduled jobs on any cadence
Branching, code steps and AI steps
They run on writes from every surface

Messaging

Reach people, reliably.

E-mail with templates and history
SMS and push notifications
In-app notifications and live events
Development sends only to test recipients

Integrations

Connect the rest of your stack.

Connectors with encrypted credentials, several accounts each
Usable from automations, code, apps and the console
External MCP servers for agents
A secret store: written, never read back

AI

Agents and assistance, built in.

Agents with instructions, tools and their own identity
Assistants for records, builders for configuration and apps
Chat embedded in any app
Claude, GPT and Gemini

Configure

Most of an app is configuration.

The builder has carried real systems for years. Data models, forms, views, dashboards, navigation and automations are set up in the browser, versioned with everything else, and promoted to production like code.

Forms with sections, conditions and calculated fields
Views as tables, boards, calendars, cards and lists
Canvases for dashboards and record details
Navigation modules per role
Translations for every label
Your colours and logo

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

Configured in the builder. No code involved.

Case

permissions

listshoweditdelete

Sales

Supportown

Clientownown

Agent Avaask

all recordsown recordsafter approvalno access

rule Client · Case · where owner = signed-in user

Why can Clara edit case #1042?

Role Client → rule “cases I own” → owner = Clara ✓

Access

One permission model. Enforced everywhere.

Define access once, by role, type, field and record. Every screen, API call, app and agent goes through the same check, so a new app can never become a back door.

APIs

REST, MCP and webhooks. No extra work.

As soon as a type exists, it has an API, guarded by the same permissions. Integrations use API keys, AI clients connect over MCP with OAuth, and apps use the SDK.

Collections, filters, paging and embedded relations
Transactional writes: all or nothing
Cached reads that still check permissions
Long requests kept alive for AI clients

1# Open cases, newest first, with the caller's permissions
2curl -G https://acme.jetstack.app/api/v1/collection/case \
3  -H "x-api-key: $JETSTACK_KEY" \
4  --data-urlencode 'filters=[{"property":"status","type":"is","param":"open"}]' \
5  --data-urlencode 'orderBy=created_on' --data-urlencode 'orderDir=desc'

Environments & history

Every change recorded. Every state restorable.

Development and production for every tenant, and one history for each: from the builder, the AI assistant, the CLI, MCP and REST. Compare any two states, restore any of them, and choose how strictly production is guarded.

Changes from the UI, AI, CLI, MCP and REST in one timeline
Compare and restore any recorded state
Production policy: open, reviewed or locked
Configuration as code: pull the tenant into git
Data migrations shipped with releases, run once

DevelopmentProduction

Production policyOpenReviewedLocked

Studio agent
website · booking page added
10:42dev
Petr · builder
field client.vat_id added
11:05devRestore
CLI
crm v34 deployed
11:20dev
MCP
role support · tickets.read granted
11:31dev

Promote to production

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

Operations

Operated for you. Isolated by design.

Every environment runs on its own: its own application container, database, cache, private network and file storage. We keep it updated, backed up and monitored.

Daily backups, and a final archive before anything is retired
Releases in rings, development first, without downtime
A usage screen: database size, files, records, users, apps, API calls
A public status page
Hosted in the EU

Next step

See the core under your own use case.

Bring a process, a spreadsheet or a prototype. We'll show you how it maps onto the core.

A walkthrough on your data model
Which parts are configuration, which are code
An honest view of effort and cost