All your business apps, connected in one space.

Pages, databases, boards, calendar, mail and whiteboards that link to each other, so every client, task and date lives in one place.

See every app

No credit card. Self-host whenever you want.

The workspace on a tablet: revenue by order status, read live from PostgreSQL

Q4 launch

Clients, tasks, dates and mail for the launch, on one page.

Board

Database
Calendar

Trusted by product teams everywhere

Northwave
Kollektiv
Halcyon
Foundry
Axiom Lab
Praxis

Six apps that already talk to each other.

Each one is a block you can drop into any page. They read the same data, so a client added in the database shows up on the board, in the calendar and in your mail.

Write plans, notes and wikis. Mention a client, a task or an email and it stays linked, wherever it moves.

Works withDatabaseBoardMail

Your workspace in your pocket.

The same pages, boards and inbox on your phone, synced as you work. Check today's tasks on the way in, answer a client from the train.

What you get

A backend stack you would have built — already built.

Three primitives, one Docker Compose file, full keys to the kingdom.

Auth that just works

Auth with GoTrue under the hood, social providers, magic links, and Turnstile-protected sign-ups out of the box.

PostgREST + Postgres

Your schema is your API. Row-level security, typed queries, instant realtime — no glue code.

GDPR by default

GDPR by default: consent ledger, DSAR exports, breach response runbook, and EU data residency baked in.

Workspace anatomy

One canvas, many windows.

Notes, auth, metrics, Postgres rows, email events, and product workflows all live in one place without losing the backend wiring underneath.

Screens from the running app

Unedited screenshots of osionos on two demo workspaces, a sales CRM and a product catalog, shown the ways your team needs them.

A CRM from two databasesDeals with formulas for weighted value and health, coloured by stage and odds.
The pipeline as a boardOne column per stage, each card a deal with its amount, owner and close date.
Next steps on a calendarThe same deals by follow-up date, coloured by stage.
Big deals as cardsOne filter turns the table into a gallery of deals above 60,000.
Forecast and regionsDeals closing soon, win odds and accounts on a map, read from the same rows.
Dashboards over your rowsTotals, charts and breakdowns, next to every database the workspace reads.
Rows on a mapEach product pinned at its warehouse address, coloured by category.
Projects on a timelineStart and end dates drawn as bars, labelled with their status.
Two views side by sideSplit the editor to keep the board and the numbers in sight.
Same data, any themeThe analytics view in Midnight, one of nine colour themes.
Set up the way you workLight or dark, an accent colour, density, corners and text size.

Inside the studio

One network for every database, app and team.

Prismatica joins your databases into one network. Each team builds on the part it is allowed to reach, and the tablet below lets you run the backend yourself.

Make a space for the sales team: a pipeline map, shared notes, Postgres and Redis.

Connect every engine
Ten engines, from Postgres and MongoDB to Redis, DynamoDB and any HTTP API, join one network. Create, read, update and delete through a single typed API.
Build on the same data
Diagrams, views, maps and notes read the live records. The LLM trace draws how a model moves through your data, step by step.
Decide who reaches what
Organisations, teams and public spaces are subnetworks. Attribute-based rules decide which engines and apps each one can reach.
Ask for a space
Tell the assistant what your team needs. It lays out the engines, apps and rules, and you adjust the result.

Run the stack yourself

The real grobase backend on a tablet: start and stop any of its services, watch a request cross it, then see how it grows.

Running: 18 of 55
Engines: 5 of 10
Request: Complete: served by PostgreSQL
Events: Not delivered: Outbox relay is off

Application core

Query router Running

Validates the caller and routes queries to the data plane.

Needs Adapter registry, Rust data plane and 3 more

Needed by Nothing

Query plane: 18 of 55 services running.

LoadLaptopQuietBusyPeak

12 pods running

The chart’s floor: two of every stateless plane, so losing a pod never takes the API down.

Autoscaled at 70% CPU
Scaled by hand
One stateful replica

Inside the namespace a NetworkPolicy denies every connection the chart does not allow; each arrow is an allowed call.

Mermaid source

flowchart TD
  clients(["Clients"])
  ingress["Ingress"]
  kong["Kong gateway<br/>HPA 2–8"]
  realtime["Realtime<br/>Fixed, 2"]
  data["Rust data plane<br/>HPA 2–10"]
  redis[("Redis<br/>StatefulSet, 1")]
  tenant["Tenant control<br/>HPA 2–6"]
  registry["Adapter registry<br/>HPA 2–6"]
  postgres[("PostgreSQL<br/>StatefulSet, 1")]
  clients --> ingress
  ingress --> kong
  kong --> data
  kong --> realtime
  data --> redis
  data --> tenant
  data --> registry
  tenant --> registry
  tenant --> postgres
  registry --> postgres
  realtime --> postgres
  classDef hpa stroke-width:2px
  classDef manual stroke-dasharray:4 3
  classDef state fill:#f3f3f3
  class kong,data,tenant,registry hpa
  class realtime manual
  class redis,postgres state
  %% HPA target: 70% average CPU. Every other connection is denied by NetworkPolicy.

Pricing

Pick a tier. Switch anytime.

No seat counts. No vendor lock-in. Self-host whenever you want.

Free

€0forever

For solo builders and side projects.

1 project · 5K MAU
Auth, Database, Storage
Community support
EU data residency

Team

Self-hosted

Freeforever · MIT

Run the whole stack on your VPS.

Unlimited everything
Docker Compose + Helm
Audited GDPR runbooks
Optional paid support

See the docs

Built for engineers

Read the docs.
Ship in an afternoon.

Every endpoint typed. Every recipe runnable. Every page versioned.

Open the docs

import { createClient } from '@grobase/js';

const baas = createClient({ url, anonKey });

const { data, error } = await baas
	.from('projects')
	.select('id, name, owner:users(email)')
	.eq('archived', false);

FAQ

Answers, before you ask.

Can I really self-host the whole stack?
Yes. The entire backend infrastructure repo is MIT licensed: Kong, GoTrue, PostgREST, Postgres, MailHog. One docker compose up and you are running locally; the same images deploy to any VPS.
Where does my data live?
Wherever you put it. The hosted tier runs in EU regions (Paris and Frankfurt). Self-hosted means your machines, your jurisdiction, your DPA — we never see the data.
How does pricing work as I grow?
You pay per active project, not per seat. Move from Free → Team in one click. If you outgrow Team, self-host: same code, no migration.
How do I migrate from another BaaS?
PostgREST means your schema is the API. Most teams import their existing dump, point Kong at it, and ship in under a day. We have migration recipes for Supabase, Firebase and Hasura.
What about security audits?
Auth flows ship with Turnstile, rate-limit and CSP defaults. The repo includes a published threat model, breach-response runbook, and OWASP ASVS L2 mapping in /docs/gdpr/.

Start with one page. Connect the rest as you grow.

Open source, GDPR-ready, and yours to host.

Read the docs

No credit card. Self-host whenever you want.