How Saltcorn Builds an App from Raw Data

Updated

Saltcorn turns raw data into a working app by following a four-step path: structure your data, connect your processes, build workflow tools, and own the system behind the work. It is an open-source database app builder that is self-hostable and designed to avoid lock-in, so the same approach works whether you are replacing a spreadsheet or assembling an internal operations tool.

The four moves from raw data to working tools

Saltcorn describes the build process as "From raw data to working tools, in four moves." Each move maps to a distinct part of the app:

  1. Structure your data — define the records and fields your team works with.
  2. Connect your processes — link those records to the steps and flows your team follows.
  3. Build workflow tools — assemble the views, dashboards, and forms people use day to day.
  4. Own the system behind the work — keep the app self-hosted and free of lock-in.

The order matters because each move depends on the one before it. You cannot build a useful workflow tool until the underlying data is structured and the processes are connected.

What "structured data" means here

Saltcorn is built around your own data rather than a fixed schema. Structuring data means deciding what a record represents and which fields it needs — for example, a job with a status, an owner, and a due date. This is the foundation the rest of the app sits on.

Connecting processes and building tools

Once data is structured, the next moves connect processes and build the tools your team actually uses. Saltcorn's stated goal is to give your team "a unified place" — one home for ops where processes, records, workflows, dashboards, and tools live together instead of being spread across spreadsheets and SaaS.

That framing points to the kind of app you end up with: an internal operations tool that combines records, workflow steps, and dashboards in one place, rather than a single-purpose form or report.

When this approach fits

Saltcorn is a reasonable fit when:

  • Your team's work is currently spread across spreadsheets and multiple SaaS tools.
  • You want a custom app built around your own data and processes.
  • You need to self-host and avoid lock-in.

It is less obviously suited to cases where a standard off-the-shelf tool already matches your process, since the value here comes from building around how your team actually works.

What to check before you start

Because Saltcorn is self-hostable and open-source, the practical questions are about your own environment: where you will host it, who will maintain it, and which processes you want to bring into one place first. The four-move path gives you a sequence to follow — structure, connect, build, own — so you can start with one process and expand from there.