← All work
Working product / capabilityProperty & geospatial intelligence

GeoM8

A reusable spatial foundation for location-aware products.

GeoM8 combines property, address, parcel, building and imagery data into a shared platform for analysis and operational workflows.

PythonFastAPIPostgreSQLPostGISDockerQwenLinux
GeoM8 project preview
01 / The situation

Property products often repeat the same difficult work: joining address data, spatial geometry, imagery and domain-specific analysis. That creates inconsistent results and slows every new product built on top.

02 / The product

GeoM8 provides a common property intelligence layer that can be queried by address, visualised in maps and reused by products such as RoofM8.

03 / System shape

The useful part is how the components become one workflow.

01identityAddress & property data
02queryPostGIS spatial layer
03evidenceImagery & buildings
04serveProperty APIs
05RoofM8 + futureDomain products
04 / What this proves

A working example of joined-up engineering.

01

Spatial foundations can be reused instead of rebuilt per product.

02

Local open-weight models can sit beside conventional APIs and data services.

03

Property identity, geometry and imagery can support multiple operational products.

05 / The engineering

How the system is put together.

  • PostgreSQL and PostGIS for spatial storage and query
  • Property and address lookup with ranked matching
  • Reusable APIs for buildings, parcels and imagery
  • Local AI services using open-weight Qwen models
  • Containerised services on dedicated infrastructure
06 / The trade-offs

Deliberate architecture choices.

  • Keep foundational property data central rather than duplicating it across products
  • Use local models where cost, privacy and control are valuable
  • Retain managed services where they provide genuine operational leverage
07 / What became possible

The result is working capability.

These are capability outcomes rather than invented client metrics. Commercial measures can be added as the products are deployed and benchmarked.

01

A consistent property identity across products

02

Faster development of domain-specific workflows

03

Greater control over inference cost and deployment

04

A platform that can support new spatial products without starting again

More working evidence

Related work.

Discuss a similar problem ↗