Skip to content

Integrations

Integrations let you bring your own third-party accounts into ALIGN, so the platform can use external services on your behalf: basemap providers, street-level imagery and, over time, the tools you already work with.

You connect an account once, and from then on the service is available inside the builders, without pasting anything again for every map or layer. Each provider has its own page below with what it is, what it unlocks in ALIGN, and how to connect it.

Integrations come in two kinds, and the difference decides who they serve.

Provider keys, such as Mapbox, MapTiler, Google or Mapillary, are API keys. You can add yours from Dashboard, Integrations, and they then serve your own work. An organization can also hold its keys, in Settings, Organization, Integrations: configured once, they serve every member, so nobody has to obtain a key of their own, and the billing stays in one place.

Personal connections, GitHub and Supabase, work through OAuth and always stay personal. They are tied to your account and are never shared with the organization, whatever your role. What an organization decides here is only whether its members may connect them at all, for everyone including owners and admins. Viewers never connect an OAuth account.

A connected credential is handled according to which of the two kinds it is, because map providers issue two kinds and they are not protected the same way.

A secret key, such as a Mapbox sk. token, never leaves our servers. No route of our API returns it, it is never written into a map you save, an export or a shared link, and it is deleted when you remove the integration.

A public key, such as a MapTiler key or a Mapbox pk. token, is made to be used by a browser. It is stored on your ALIGN account, and it is carried by the maps you publish, because the visitor’s browser loads the tiles itself and needs the key to do it. What protects a public key is not secrecy, it is the domain restriction you set in your provider’s console. ALIGN names the exact domain to allow when you publish.

The map stored in your Datastore carries no key at all, whichever kind you use. The key is added to the published copy only, at the moment it is served.

Providers that power the Street View widget of the Map Builder: click a point on the map and see the nearest panorama.

ProviderWhat it powersStatus
MapillaryCommunity street-level imagery in the Street View widget.Available
Google Street ViewGoogle 360° panoramas in the Street View widget.Available

Providers whose tiles and styles become available as basemaps (Add Data → Basemap and the Basemap switcher), and, for some, routing and geocoding in widgets.

ProviderWhat it powersStatus
MapboxMapbox basemaps, Directions routing, Reverse geocode.Available
MapTilerMapTiler basemaps.Available
ProviderWhat it powersStatus
SupabaseA managed PostgreSQL + PostGIS database for the apps you build.Available
ProviderWhat it powersStatus
GitHubPush your app’s source to your own repository, run GitHub Actions.Available

Not a key and not a personal OAuth account of the kinds above: a plugin you install in your desktop GIS, which signs in to ALIGN the way the browser does and carries your own role. An organization decides whether its members may connect desktop plugins at all, in Settings, Organization, Integrations.

ToolWhat it powersStatus
QGISPublish layers, their style and their metadata, or a whole project as a web map, from QGIS to your Datastore.Beta