Protomaps: Self-hosting map tiles has gotten cheap and easy

Software developer Bruce Roettgers published an implementation breakdown documenting how developers can self-host global vector map tiles for five dollars per month using the open-source Protomaps ecosystem. According to bruceroettgers.eu's report, hosting map data on commodity cloud storage avoids the steep volume cliffs of proprietary map platforms. The approach relies on PMTiles, a single-file archive format that serves geographic tiles directly over HTTP Range requests without requiring dedicated backend tile servers.

This technical breakdown analyzes tile extraction methods, cloud storage hosting economics, edge caching setup, and frontend client integration for engineering teams deploying interactive maps. It provides web developers and independent product creators with a sustainable alternative to commercial mapping platforms that charge escalating rates per impression. Readers will discover the concrete commands, storage architecture, and network configurations required to run planet-scale maps while preserving strict cost predictability.

01Daily builds and bounding box extracts

Generating map datasets begins with obtaining precompiled geographic extracts distributed through the Protomaps build service. Engineering teams seeking full global coverage can download the latest daily build archive directly from the project build repository. This single prepackaged archive contains complete planetary mapping information structured for immediate query resolution across standard geographic coordinates.

Projects that do not require global coverage can isolate target areas using the Protomaps command line interface. The command line utility allows engineers to define explicit bounding boxes or restrict compilation to selected zoom levels. Filtering geographic boundaries creates substantially smaller archive files that reduce transfer times and diminish recurring storage fees.

02Edge storage pricing and bandwidth economics

Deploying map tiles across European Union provider Bunny.net provides global storage paired with content delivery edge caching. Edge storage pricing ranges from one cent per gigabyte monthly without replication to five and a half cents per gigabyte monthly for maximum planetary distribution. Network bandwidth across Europe and North America costs one cent per gigabyte on standard tiers and half a cent on high volume routes.

Hosting the full 139 gigabyte planetary map with five-fold replication costs five dollars per month in storage. A desktop browser loading a European map and zooming into a city transfers five megabytes, costing five thousandths of a cent. At five cents per thousand visits, self-hosting can run one hundred times cheaper than Mapbox flat visitor fees.

03Storage zone streaming with rclone tooling

Uploading planetary archives directly through web interfaces presents reliability challenges when transferring hundred-gigabyte assets. Standard web application programming interface uploads frequently experience connection timeouts after fifteen minutes of sustained transmission. Configuring storage zones with Amazon S3 compatibility enables resilient multipart chunk streaming over standard command line utilities.

1. Zone provisioning Create an edge storage zone with Amazon S3 API compatibility enabled in the provider console.
2. Tooling configuration Register storage access credentials and regional S3 endpoints inside the local rclone configuration file.
3. Stream transfer Execute the copyurl command with 256 megabyte chunk sizes using an active tmux session.

Transferring archives directly from public build mirrors into cloud storage bypasses local network bandwidth bottlenecks entirely. Running rclone inside terminal multiplexers or lightweight virtual servers prevents residential connection drops from aborting large transfers. Configuring chunk sizes of 256 megabytes optimizes transfer throughput while providing continuous progress reporting across multi-hour upload operations.

04Pull zone delivery and abuse limits

Connecting an edge storage zone to a fronting pull delivery zone establishes planetary caching across edge points of presence. Network operators must configure allowed referrer security rules under general settings to prevent third-party domains from hotlinking tile assets. Restricting domain access protects site owners from unbudgeted bandwidth consumption generated by external scrapers and unauthorized web properties.

Defending pull zones against abusive downloads prevents malicious scrapers from pulling entire 139 gigabyte archives. Administrators can limit download speeds to ten kilobytes per second once single requests exceed ten megabytes under network settings. Enabling large object delivery optimizations ensures edge nodes cache segmented byte range responses while request rate caps block rapid automated scraping.

Note: Bunny.net drops the last octet of visitor IP addresses by default across its network edge. Any personal data deliberately transmitted through CDN endpoints remains subject to standard European Union data processing rules. This safeguard operates automatically across all edge points of presence without manual scripting.

05MapLibre integration and client style wiring

Displaying self-hosted vector tiles inside web browsers requires integrating client-side rendering engines such as MapLibre GL. Developers install the pmtiles package from the npm registry to register custom protocol handlers inside application code. Registering the protocol enables the client map renderer to request specific binary byte segments directly from content delivery networks.

Configuring rendering libraries involves pairing the protocol handler with custom cartographic style definitions and remote vector tile endpoints. MapLibre decodes geographic geometry and label data in real time using local client graphics hardware. Once loaded, client applications pan and zoom across geographic features without executing server queries against backend database clusters.