Release qualification in progress

TasteGeo

GeoServer compatibility,
rebuilt in Rust.

Rebuilding GeoServer compatibility in Rust.

A Rust-native geospatial server built by comparing existing OGC requests and operational behavior with a reference server.

GET /ows?service=WMS&request=GetMap

View compatibility status Explore the architecture

Terrain layers converging on the TasteGeo service core

Rust-native runtimeOriginal brand artwork

01 / 07

Compatibility-firstRust edition 2024GPL-2.0-or-later

01 / PRODUCT

A compatibility server built for controlled replacement.

TasteGeo rebuilds the public behavior teams already depend on while making runtime, storage, and verification boundaries explicit.

Behavior-first OGC

WMS, WFS, WMTS, WCS, and REST contracts are compared at the public HTTP boundary.

Requests, responses, errors

Rust-native runtime

A memory-safe native runtime targets predictable deployment without a JVM dependency.

Rust 2024, Axum, Tokio

Isolated data adapters

Protocol code does not bind directly to PostGIS, GeoPackage, Shapefile, or GeoTIFF implementations.

Versioned capability boundaries

Evidence-led migration

Read-only analysis, semantic diffs, shadow traffic, and rollback gates support phased adoption.

Compare before cutover

Cross-platform delivery

The same configuration contract and operating workflow target Linux, Windows, and macOS.

One server model

Ten-language experience

Product, verification, documentation, and community routes are available in ten languages.

Locale-aware UI and metadata

Protocol + store wall

One surface.
Many contracts.

Every core contract in the generated matrix is currently partial support under validation. This is a measured compatibility surface, not a completion claim.

WMS

Maps, feature info, and legends

WFS

Feature queries and transactions

WMTS

Matrix sets and tile cache

WCS

Coverage subsets and output

REST

Catalog and service configuration

PostGIS

Primary vector adapter

GeoPackage

Portable SQLite datasets

Shapefile

Bounded vector ingestion

GeoTIFF

Raster and coverage store

COG

Cloud-optimized raster target

03 / Compatibility surface

Works with existing
GeoServer clients.

We validate compatibility by preserving protocol semantics, errors, catalogs, and operational flows. This is not a declaration of complete compatibility with any product.

WMS request

SERVICE=WMS
REQUEST=GetMap
VERSION=1.3.0

Normalized evidenceSemantic comparison

WMS consumersCompatibility target

WFS consumersCompatibility target

WMTS clientsCompatibility target

REST automationCompatibility target

PostGIS workflowsAdapter under validation

Existing data_dirRead-only analysis path

OGC toolingSemantic comparison target

Map rendering clientsGolden image target

04 / JAVA ↔ RUST

Keep GeoServer's contract. Change the runtime deliberately.

GeoServer is the mature reference with a broad Java extension ecosystem. TasteGeo is an independent Rust implementation under qualification, not a drop-in completion claim.

Evaluation point	GeoServer	TasteGeo Server
Runtime	Java 17 or 21, packaged application or servlet container	Native Rust server target, release qualification in progress
Language safety model	Java managed memory and JVM garbage collection	Rust ownership and borrow checking, no GC in the default path
Operational resource model	Mature JVM heap, GC, and container tuning practices	Native binary and explicit memory lifetimes, workload validation in progress
Compatibility	Established OGC and operational behavior	Same-request semantic comparison against a reference server
Extensions	Large core, extension, and community module ecosystem	Versioned plugin boundaries with a deliberately limited surface today
Data stores	Broad, mature vector and raster integrations	Priority adapters are implemented and validated incrementally
Migration	Existing production configuration and data_dir	Read-only diagnosis, separate conversion, shadow traffic, rollback
License	GPL version 2 or later	GPL-2.0-or-later, independently developed

GeoServer reference documentationRuntime Extensions License

Keeptheclients.Replacetheruntime.

Keep the clients. Move the runtime to Rust.

Workspace architecture

Boundaries before
speed.

We fix dependency direction and verify public HTTP behavior. No storage engine or framework gets to define protocol semantics.

01 / Foundation

Foundation

Protocol- and storage-independent values, parsers, coordinate systems, and observability boundaries.

geometrycrsfilterogc-commonconfigobservability

02 / Domain

Domain

Catalog, security, style, and versioned extension contracts live in one layer.

catalogsecuritydatastore-apistyleplugin-api

03 / Adapters

Adapters

Data access is isolated so protocol implementations never depend directly on a particular store.

store-postgisstore-geopackagestore-shapefilestore-geotiff

04 / Services

Services

OGC services and the administration API are assembled above rendering and cache layers.

rendertile-cachewmswfswmtswcsrest-api

05 / Assembly + Verification

Assembly + verification

The server assembles boundaries; verification tools compare only public HTTP and fixtures.

servercompat-tests

06 / PERFORMANCE

Performance numbers need a reproducible context.

TasteGeo will publish results only after both servers run on the same hardware, datasets, request mix, warm-up policy, and correctness gates.

Public benchmarkMeasurement in preparation

Comparison contract

Each run records the exact build, environment, dataset, concurrency, cache state, and semantic result. A faster incorrect response is a failed result.

Review verification evidence

01p50 / p95 / p99

Response latency by OGC workload

02Throughput

Sustained requests per second

03TTFB

Time to first response byte

04CPU

Processor cost at equal load

05RSS

Resident memory and growth

06Connections

Database pool pressure

No estimated or local-only values are presented as public performance claims.

05 / Readiness

Evidence before
declaration.

TasteGeo separates local code-quality gates from external release qualification. Core contracts remain partial support under validation while final promotion is in progress.

Current statusRelease qualification in progress

View verification fixtures