Skip to content

Data and databases

An application needs data. From inside the App Builder you reach the same data surfaces as the rest of ALIGN, plus the ability to connect a real database. This page covers how each one shows up in the IDE. The platform pages go deeper on each topic.

The Data panel in the tool rail opens on your Datastore: your saved assets, vectors, rasters and web-service references, all in open, cloud-native formats. Drop an asset into your app, or point the AI Builder at one with an @ mention. It is the same catalogue you use everywhere in ALIGN.

Read more on the Datastore page.

In the App Builder, data comes in through your Datastore. To browse trusted open datasets by hand, open the Data Hub from the Map Builder; from inside the IDE, ask the AI Builder: it searches the Data Hub and can extract data for your project when you ask it to.

When your app needs to store or serve its own data, the Data Sources panel lets you connect Supabase, a managed PostgreSQL database with the PostGIS spatial extension.

From the panel you can:

  • link your Supabase account,
  • pick an existing project or create a new database, which deploys a managed Postgres and PostGIS instance for your app,
  • and manage the connected project, including its edge functions.

Creating a Supabase project from ALIGN is the simplest way to give your application a spatial database of its own.

Any account or key you connect is stored securely and scoped to what it is for. It is never written into a saved app, an export, or anything you share. See Integrations for how ALIGN keeps credentials out of your artifacts.