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.
How it works
Section titled “How it works”You connect an account once by adding its key in your ALIGN settings (Dashboard → Integrations). From then on, that service is available inside the builders, without pasting the key 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 obtain the key.
Where your keys go
Section titled “Where your keys go”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.
What you can connect
Section titled “What you can connect”Street-level imagery
Section titled “Street-level imagery”Providers that power the Street View widget of the Map Builder — click a point on the map and see the nearest panorama.
| Provider | What it powers | Status |
|---|---|---|
| Mapillary | Community street-level imagery in the Street View widget. | Available |
| Google Street View | Google 360° panoramas in the Street View widget. | Available |
Basemaps & map services
Section titled “Basemaps & map services”Providers whose tiles and styles become available as basemaps (Add Data → Basemap and the Basemap switcher), and — for some — routing and geocoding in widgets.
| Provider | What it powers | Status |
|---|---|---|
| Mapbox | Mapbox basemaps, Directions routing, Reverse geocode. | Available |
| MapTiler | MapTiler basemaps. | Available |
| TomTom · HERE | Basemaps and traffic. | Roadmap — connectable, setup pages coming |
Data & databases
Section titled “Data & databases”| Provider | What it powers | Status |
|---|---|---|
| Supabase | A managed PostgreSQL + PostGIS database for the apps you build. | Available |
Source control & CI
Section titled “Source control & CI”| Provider | What it powers | Status |
|---|---|---|
| GitHub | Push your app’s source to your own repository, run GitHub Actions. | Available |