Engineering at Spatialnode

Spatialnode builds geospatial products that must remain understandable under pressure: GIS platforms, mapping applications, digital twins, AI-assisted spatial tools, and the cloud foundations behind them.

Our principles

Principle	What it means in practice
Ship useful increments	Break work into reviewable, deployable slices.
Treat geography as data	Preserve coordinate reference systems, provenance, precision, and licensing.
Make the safe path easy	Automate tests, previews, checks, backups, and least-privilege access.
Prefer boring systems	Start with proven tools and clear boundaries; add complexity only when it pays for itself.
Leave it clearer	Improve names, tests, docs, and observability where you touch code.

The standard

A change is complete only when it solves the stated problem, is reviewed, is tested at the right level, and can be operated by someone who did not write it.

How work moves

flowchart LR
  A[Problem] --> B[GitHub issue]
  B --> C[Small branch]
  C --> D[Pull request]
  D --> E[Review + checks]
  E --> F[Merge to main]
  F --> G[Automated deployment]
  G --> H[Verify and communicate]

Stack defaults

Area	Spatialnode defaults
Web	React, TypeScript, Next.js, Tailwind CSS
Maps	MapLibre GL JS, Deck.gl
Services	FastAPI or Django; Axum/Rust when performance or concurrency warrants it
Spatial data	PostGIS, GDAL, STAC, GeoParquet, OpenStreetMap
Delivery	Docker, GitHub Actions, Coolify, Cloudflare, AWS

Start with Getting started. The full handbook is designed to take under 45 minutes.