Atlas
Current version:v3.0.0
- Self-hosted Mapbox maps, search, and navigation
- Mapbox behind your firewall, even on air gapped networks
- Streets, Satellite, Terrain, Boundaries, and custom tilesets
Mapbox Atlas allows you to deploy commercial-grade maps, search, and navigation on private, air gapped networks in minutes. You can host Atlas on bare metal hardware, a virtual private cloud, or secure enclave that you have complete control over, then deploy to your applications. Atlas supports the latest Mapbox vector map technology, including Mapbox GL JS, so maps render quickly and are highly customizable.
Atlas license
To install and use Atlas, you must have a Mapbox user account with a valid Atlas license.
Need an Atlas license? Contact us to learn more.
Access token
Once you have an active Atlas license, you will need to create a Mapbox secret access token with atlas:read scope. This secret access token enables you to use the Atlas installer.
- Go to the Mapbox access token page.
- Click on +Create a token.
- Give the new token a name like "Atlas".
- Uncheck all the default public scopes under Public scopes.
- Under Secret scopes, check the ATLAS:READ scope.
- Click Create token.
- Save your new Atlas token in a secure place. Once you leave the Access Tokens page, you will not have access to this token again. Do not commit the Atlas token to GitHub or share it with anyone outside of your organization.
System requirements
Data and disk size
Below are the approximate sizes and zoom levels (if applicable) for each dataset. Exact file sizes are subject to change with new data from periodic updates.
| Dataset | Low res (dev) | Mid res | High res |
|---|---|---|---|
| Mapbox Streets v8 | 550 MB (z8) | Not Available | 292 GB (z16) |
| Mapbox Satellite | 304 MB (z8) | 42 GB (z12) | 1.7 TB (z14) |
| Mapbox Terrain v2 | 435 MB (z8) | 35 GB (z12) | 635 GB (z15) |
| Mapbox Terrain-RGB | 1.4 GB (z8) | 435 GB (z12) | 3 TB (z14) |
| Mapbox Countries v1 | 512 KB (z8) | Not Available | 307 MB (z16) |
| Mapbox Boundaries | Not Available | Not Available | 15 GB |
| Search | 5 GB | Not Available | 75 GB |
| Navigation | 100 MB | Not Available | 85 GB |
Hardware configuration
Hardware requirements depend on which services (maps, search, and navigation) that you deploy.
Maps
Size storage based on the tilesets you need for your use case, plus headroom for growth.
Search and navigation
Search and navigation use 7 Docker containers. We recommend, at a minimum, the following configurations for a deployment using both search and navigation. Deployments using only search or only navigation may need less resources. The development configuration is appropriate for testing and evaluating Atlas, and is not recommended for production workloads.
| Development | Production |
|---|---|
| 2 CPU | 4 CPU |
| 4 GB RAM | 16 GB RAM |
| 10 GB SSD | 160 GB SSD |
Get started
- Set up Atlas for local development: Getting Started with Mapbox Atlas.
- Set up Mapbox GL JS: GL JS.
- Set up map styles: Map Styles.
- Deploy Atlas to production on AWS S3 or Nginx: Deploy to production.