MapSmith / GIS infrastructure
A spatial platform you can build on.
Self-hosted GIS that connects spatial data, map authoring and analysis with programmable APIs and a CLI.
Self-hosted platform · architecture notes
The problem
Developers and teams publishing and operating spatial services.
A map interface alone is not a GIS platform. Teams also need hosted data, permissions, repeatable analysis and a way to automate the same workflows outside the browser.
How it works
One connected workflow.
- 01Data & servicesPublish collections and serve spatial features and vector tiles.
- 02Maps & analysisAuthor maps and run server-side spatial operations.
- 03SDK & automationUse APIs and the CLI for publishing, queries and platform workflows.
Engineering workflow · a simplified view of the product, not a screen mockup.
Engineering decisions
What matters beneath the interface.
Build on PostGIS and MapLibre, with a Go service layer and a shared API surface for the web workspace, SDK and CLI. Analysis jobs produce hosted layers that can be used in maps.
The platform is an evolving implementation, not a claim of feature parity with mature enterprise GIS suites. Self-hosting gives deployment control but also carries an operational responsibility.
My contribution
From product to implementation.
Product architecture, full-stack engineering and platform operations.
- PostGIS-backed vector tiles and hosted collections
- Server-side analysis producing new spatial layers
- SDK and CLI access to the same platform services
Angular · Go · PostGIS · MapLibre · Keycloak · Docker