CoreSpatial Server for ArcGIS Enterprise migration
CoreSpatial Server by NGS is a secure, open-standards GIS platform for organizations moving off ArcGIS Enterprise. It publishes your maps, features, and imagery over OGC standards, runs on air-gapped and disconnected networks, and now ships a FIPS 140-3 GeoServer build, all on a per-deployment subscription.
Where each part of ArcGIS Enterprise lands in CoreSpatial
Most ArcGIS Enterprise deployments come down to the same handful of building blocks. Each one has a direct home in the CoreSpatial suite.
| In ArcGIS Enterprise today | In CoreSpatial by NGS |
|---|---|
| Map and feature services | CoreSpatial Server (GeoServer) publishing WMS, WMTS, WFS, and Mapbox Vector Tiles |
| Enterprise geodatabase | PostgreSQL 15 with PostGIS 3 |
| Imagery and raster services | CoreSpatial Server with GDAL drivers for NITF, RPF, DTED, JPEG2000, and MrSID, plus CoreSpatial Map Manager for drag-and-drop imagery |
| Portal web maps, dashboards, and stories | CoreSpatial Portal maps, dashboards, and GeoStories, with role-based access control |
| Scene layers and 3D | CoreSpatial 3D, a self-hosted Cesium ion streaming 3D Tiles |
| Basemaps | CoreSpatial Basemaps, served from your own network |
| Licensing | One subscription priced per deployment, not per user or per CPU |
Secure by default, from the data center to the tactical edge
Teams leaving ArcGIS Enterprise in defense and government environments rarely get to relax their security requirements on the way out. CoreSpatial Server is designed for those environments.
FIPS 140-3 GeoServer Build
Since release 2026.3.3, CoreSpatial Server ships a FIPS 140-3 GeoServer build that uses the Bouncy Castle FIPS (bc-fips) provider in a hardened RHEL 9 container, with Keycloak SSO for administrator sign-in.
Air-Gapped and Disconnected
Every service runs on your own infrastructure with no call out to a cloud service, from full Kubernetes clusters to lightweight k3s runtimes at the tactical edge.
Compliance Artifacts Every Release
Each quarterly release includes an SBOM (SPDX, CycloneDX, and HTML), a Vulnerability Advisory Report, and system administrator documentation for your ATO package.
Immediate Critical Patching
High and Critical CVEs are patched immediately, without waiting for the next scheduled release.
How an ArcGIS Enterprise migration to CoreSpatial works
- Inventory. Map every service, client, and dependency in your current stack, including any application hard-wired to the Esri REST API, so nothing surprises you in production.
- Move the data. Geodatabases, shapefiles, and rasters move into PostGIS and cloud-optimized imagery with GDAL.
- Republish the services. Map and feature services become OGC services on CoreSpatial Server. Anything that already speaks OGC keeps working.
- Rebuild the cartography. Esri symbology does not convert cleanly, so styles are rebuilt in SLD, CSS, or YSLD, and that work is budgeted up front.
- Run in parallel. CoreSpatial runs alongside ArcGIS Enterprise and is validated against your real workflows before anything is switched off.
NGS delivers this as the fixed-scope, fixed-price SDI Modernization package, typically 4 to 8 weeks. Our CEO started his career at Esri Defense Services, so we know both sides of this move.
ArcGIS Enterprise migration questions
Can CoreSpatial Server replace ArcGIS Enterprise?
For publishing maps, features, imagery, and tiles over OGC standards, yes. CoreSpatial Server handles the services, PostGIS holds the data, and CoreSpatial Portal and CoreSpatial 3D cover web maps, dashboards, and 3D. Applications built directly on the Esri REST API need changes, and those are identified during the inventory.
Can our analysts keep using ArcGIS Pro?
Yes. ArcGIS Pro and other desktop GIS clients can add WMS, WMTS, and WFS layers, so analysts can keep their desktop tools while the server side moves to CoreSpatial.
Does CoreSpatial Server run in air-gapped environments?
Yes. CoreSpatial Server, its basemaps, and the rest of the CoreSpatial suite run entirely on your own infrastructure, so they work on air-gapped, disconnected, and bandwidth-constrained networks.
Does CoreSpatial Server support FIPS 140 environments?
Since release 2026.3.3, CoreSpatial Server ships a FIPS 140-3 GeoServer build from the NGS FIPS fork, using the Bouncy Castle FIPS provider in a hardened RHEL 9 container. Read the 2026.3 release notes.
How long does a migration from ArcGIS Enterprise take?
The SDI Modernization package typically runs 4 to 8 weeks, with a fixed scope and price agreed before work starts. Larger estates can be migrated in phases while both systems run side by side.
How is CoreSpatial licensed and purchased?
CoreSpatial is an annual subscription priced per deployment, not per user or per CPU. Government customers can buy through the NGS GSA Multiple Award Schedule contract or the DoD Tradewinds Solutions Marketplace. See how CoreSpatial pricing compares.
Plan your move off ArcGIS Enterprise
Tell us what you run today and we will map out where each piece lands in CoreSpatial.