WebGIS & Geoportal Pricing

The figures below are starting prices for a base system, not fixed quotes. Every project is scoped from your actual data volume, the number of modules, and how much field workflow needs to be digitised — so the final number moves with complexity, in both directions.

What determines which tier fits you is mostly architecture. A Non-GeoServer system is lighter and cheaper to host, and is usually enough for a village, a sub-district office, or a single-purpose thematic map. A GeoServer stack costs more because it adds an OGC service layer (WMS, WFS, WMTS) that lets other institutions consume your data directly — worth it when interoperability is a requirement, not a nice-to-have.

Two things are excluded from every tier: hosting or VPS and VAT. We deliberately keep infrastructure out of the quote so you own the server account and are never locked into us for renewals.

• Data volume and condition. Clean, ready-to-use shapefiles are cheap to load. Data that needs topology repair, reprojection, or attribute reconciliation adds work — see spatial data integration.
• Number of modules. A read-only map costs far less than one with field input, user roles, document generation, and an analytics dashboard.
• 2D or 3D. 3D adds data acquisition (photogrammetry, point cloud) and heavier hosting — see Digital Twin City.
• User roles. A single admin is simpler than a multi-level hierarchy of manager, surveyor, and public viewer.
• Training and handover. We include basic handover; structured training for a larger team is quoted separately.

Not sure which tier applies? Send us your data sample and a short description of the workflow — we will tell you which architecture is actually needed, including when the cheaper one is enough.