jumpasaservice/tabularia-gateway repository overview

⁠Tabularia gateway

Tabularia is an open-source, self-hosted data preparation platform: people build data flows visually — joins, filters, pivots, SQL, Python and R — on data from databases, files, SFTP, S3, APIs and SharePoint, run them on the engine that fits (Polars, DuckDB, chDB, an external ClickHouse, BigQuery), and publish trusted datasets, pixel-perfect reports and live dashboards. Permissions, data contracts, lineage and an audit trail come with it from the first day.

This image is the gateway, Tabularia's control plane: the API every client talks to.

• Sign-in and access: passwords, single sign-on over OpenID Connect, API tokens and service accounts; folders with view, run, edit and manage rights; an audit log that can be sent to a SIEM.
• What people build: flows and their versions, datasources, saved views, SQL scripts, reports, dashboards, notebooks — and the checks of who may read what.
• Orchestration: schedules, flow groups, Pushmail, webhooks and the runs' history (APP__ROLE=orchestrator runs only this background work, api only the requests, all both).
• The AI assistant and the MCP server, with spending caps and a metadata-only mode.
• Administration: settings changed live from the panel, database backups, and on Kubernetes the worker autoscaling, Python and R environments, container registries.

The gateway processes no data itself: the engine does, and the browser app is the frontend. A working installation runs the three images together, with PostgreSQL, Valkey (or Redis) and an S3-compatible object storage.

⁠Tags

Pin an exact version in production and upgrade the three images together, following the upgrade guide⁠. Every release is described in the changelog⁠.

⁠Getting started

• Production on Kubernetes: the Helm chart in the repository installs the three images, with the gateway and the orchestrator as separate workloads, network policies and a read-only root filesystem — Kubernetes and Helm⁠.
• Try it on your computer: three commands with Docker Compose — getting started⁠ — or a local Kubernetes with minikube⁠.

⁠Configuration

Settings are environment variables; the ones the gateway needs first:

All of them, with defaults and the Helm values that set them: configuration reference⁠. Many limits, waits and caps can also be changed while it runs, from Administration → Settings.

⁠The container

• Listens on port 8000; GET /health answers while the app is serving (a liveness check).
• Runs as an unprivileged user (uid 10001), writes only to /tmp, and works with a read-only root filesystem.
• Holds pg_dump and pg_restore for PostgreSQL 14 to 18, for the database backups.
• Python 3.12 on Debian bookworm slim.

Before a release is pushed, its images are built for both architectures, started for a smoke test, checked for the licences of the packages they hold, and scanned for secrets (the maintainers' fingerprints and TruffleHog's verified credentials). The process is described in the repository: release process⁠.

⁠Links

• Website and documentation: tabularia.org⁠
• Source code and issues: github.com/JumpAsAService/Tabularia⁠
• Licence: AGPL-3.0⁠. The notices of the third-party software are linked from the app's menu and the website's footer.