Abstract map infrastructure background
Sources
Geocoding
Styles
Serving
Tilequery
Jobs
API Keys
Reverse
Places
Uploads
Vector Tiles
Static Maps
Usage
Releases
Workers

Operate maps from source to delivery.

Planisfy gives teams one self-hostable control plane for styles, tilesets, API keys, usage, and geodata operations.

Platform Capabilities

Everything needed to operate map infrastructure.

Planisfy connects publishing, serving, access control, and operations so teams can move from geodata to reliable map APIs without stitching separate tools together.

Map Delivery

Publish MapLibre styles, serve vector tiles, support tilequery, and expose static map surfaces from the same platform.

Search and Location

Offer geocoding, reverse geocoding, and places workflows alongside the maps your users already consume.

Data Workflows

Move source uploads through imports, processing jobs, review steps, and releases before they become production tilesets.

Access Control

Create scoped API keys, separate environments, and keep customer access visible without mixing operational concerns.

Operations

Track jobs, workers, usage, and delivery health from one place, with enough context to debug map infrastructure quickly.

Self-Hostable Core

Run the control plane and geospatial services where your team needs them, while keeping a clear path to managed delivery.

Workflow

A controlled path from raw geodata to production map delivery.

Planisfy keeps imports, jobs, styles, releases, keys, and delivery health connected so teams can ship map changes without losing operational context.

Schema validated
Worker capacity healthy
Release ready
Step 1

Import sources

Upload GeoJSON, MBTiles, or Overture extracts and keep each source traceable.

Step 2

Process jobs

Run tiling jobs, inspect artifacts, and promote clean outputs into review.

Step 3

Review artifacts

Check generated tiles, metadata, and source lineage before publishing.

Step 4

Publish styles

Connect tilesets to MapLibre styles with controlled draft and release states.

Step 5

Scope access

Issue API keys for the environments and workloads that should consume the map.

Step 6

Serve APIs

Deliver tiles, styles, tilequery, static maps, and search endpoints behind keys.

Step 7

Monitor usage

Watch health, jobs, and usage signals as releases move through production.

Frequently Asked Questions

Find answers to common questions about operating maps with Planisfy.

Need a deployment conversation? Get in touch

Ready to Build with Planisfy?

Publish styles, operate tilesets, and manage map access from one self-hostable control plane.