POSTGRESQL-FIRST · 100% OPEN SOURCE · BETATB / 001

From PostgreSQL
to a REST
API… and more.

Expose the tables, views and functions your application needs, and get permissions down to rows and fields, screens for your team, dashboards and automations - with PostgreSQL still deciding.

Your PostgreSQL. Your infrastructure. Your control.

DEPLOY WITH DOCKER
totalbase / docker

docker compose up -d. PostgreSQL ready. TotalBase ready. Admin: http://localhost:3050/admin/.

On your infrastructurePostgreSQL + TotalBase
Illustrative Docker Compose sequence; prior configuration is required.
TABLES · VIEWS · FUNCTIONS

00 / SEE IT BUILD

A field service app,
built from nothing.

Tables, roles, screens, dashboards and workflows, created through TotalBase's MCP server - the same calls an AI agent makes - while the admin fills up. Then the app opens.

Acme's field service app built through the MCP server, call by call, while the admin fills up.

01 / GENERATE THE API

Expose the resources you need.
As a REST API.

Choose tables, views and functions; TotalBase generates an API documented and protected by permissions.

REST API + OPENAPI

A REST API for your tables, views and functions.

Select fields, filter records and query real relationships. OpenAPI documents the resources you expose and their permissions.

In this example: one active product and its brand name.
Query parametersREST
01fields=id,name,brand.name
02where[active][_eq]=true
03order_by=name
04limit=1
Example response JSON
{
  "data": [
    {
      "id": "02",
      "name": "Mechanical keyboard",
      "brand.name": "Mono"
    }
  ]
}
Illustrative query and response; require a products.brand → brands.id relationship and read permissions.
AUTHENTICATION + PERMISSIONS

Security that accompanies every request.

Create users and roles for your application. A user can hold multiple roles; TotalBase resolves their permissions before accessing PostgreSQL.

  • Combine roles around each user’s responsibilities.
  • Define access by action, column and row.
  • An explicit DENY always takes precedence.
The effective permission applies equally from the API, a DataView or an integration.
Effective permissionsPOLICY
UserLucía Pérez
2 roles
SalesOperations
ScopeRule
Products · readAllowed
RowsOwn region only
ColumnsCost hidden

DENY takes precedence over every ALLOW.

02 / BUILD THE PANEL

02
DataViews

Panels for working with your data.

DataViews put tables, cards, kanban boards, calendars, Gantt charts, maps, trees, forms and custom pages in front of your team, in an App that works on a desktop, a tablet and a phone. Dashboards add reports from SQL, embeddable in another site.

Operations continue to respect the source resource’s permissions.

03 / AUTOMATE THE FLOW

03
Workflows

When an event happens, keep working.

Trigger workflows from data events, schedules, webhooks or a person. Write records, send emails, render PDFs, call HTTP and SOAP services, run JavaScript - and keep every run.

Automation connected to your application’s data and permissions.

04 / BUILT FOR AI AGENTS

Describe it.
An agent builds it.

TotalBase includes an MCP server: Claude, or any agent that speaks MCP, creates tables, permissions, screens, dashboards and workflows - and explains your data - through the same API you use.

Everything you can build

Every screen of the admin has its tools: what you can build by hand, an agent can build for you, and you can open and change it afterwards.

Under your permissions

An agent acts as a user, with a token and a role. It can't do more than that role can, and nothing reaches your users until it's published.

Every step recorded

Each change it makes is in the audit log, like anyone's: who did what, when, and what was there before.

05 / POSTGRESQL, WITH ALL ITS POWER

We do not replace PostgreSQL.
We respect it and leverage it.

TotalBase adds the application layer on top of PostgreSQL and reuses its native strengths instead of hiding or replacing them.

Advanced native types

PostgreSQL includes rich types such as JSONB, arrays, enums, UUID and ranges, without depending on an artificial layer above the database.

Real integrity

CHECK, UNIQUE, FOREIGN KEY, EXCLUDE, NOT NULL and domains keep integrity where it belongs: in the database itself.

Concurrency and transactions

MVCC and PostgreSQL’s concurrency model allow simultaneous writes with greater robustness and less unnecessary locking.

Functions and triggers

Native functions, procedures and triggers move business logic into the data layer without sacrificing performance or reliability.

Expressive SQL

CTEs, window functions, recursion and complex queries make PostgreSQL an exceptionally powerful engine for advanced logic.

Extensibility

PostgreSQL can be extended with modules and specialized tools, something many databases do not offer with the same maturity.

06 / OPEN SOURCE

Close to your data.
Open by design.

A tool this close to your data should be understandable from its code, run on your own infrastructure and evolve with the people who use it.

Transparency

Understand how it works from the inside.

Control

Run it on your own infrastructure.

Participation

Suggest improvements and build together.

Apache 2.0 · Beta 0.1.0 · PostgreSQL 15 to 18

View on GitHub

A FEW ANSWERS

Before you begin.