GC2 (Geo Compute Cloud)

At a glance

GC2 (Geo Compute Cloud) is a geospatial backend from MapCentia built on PostgreSQL and PostGIS. You import files such as GeoPackage, Shapefile or GeoParquet into tables, then reach them through parameterized SQL over REST or WebSocket, auto-generated GraphQL, OGC API Features and Maps, and WMS/WFS. It runs as a managed cloud, free during its beta, or self-hosted with Docker under AGPLv3.

Good fit

Developers who need spatial data behind a web map, field app or open data portal and would rather not write their own API server. It also suits GIS teams that want QGIS to read and edit the same tables over WMS/WFS and WFS-T, and people who want Claude Code or Codex to provision a spatial backend through GC2's MCP server and plugin.

Consider something else when

Your app has little spatial data, so a general-purpose Postgres backend would do the job. Also skip the beta cloud if you need more than 10 tables or 10 sub-users, or published pricing before you commit. If you plan to modify the server and run it for others, check the AGPLv3 obligations first.

Start here

Create a backend in the GC2 Cloud console, or start the stack with Docker Compose. Install the CLI with npm install @mapcentia/gc2-cli --global, run gc2 login, add a schema and table with gc2 schema add and gc2 table add, and pipe a query to gc2 sql. Then import a spatial file and request its OGC API Features items to confirm GeoJSON comes back.

Cost and requirements

GC2 Cloud has no pricing tiers during the beta, with limits of 10 tables and 10 sub-users; the FAQ does not say what follows the beta. Self-hosting is free under AGPLv3 and needs Docker with Compose v2, plus Node.js and npm for the CLI. The stack runs an HTTP app, a WebSocket service, PostGIS 16 and Redis. The MCP server uses the CLI login or an access token.

Limits to know

The self-hosting README still uses the earlier Centia.io name and its @centia-io/cli package, so its commands differ from the GC2 docs. Postgres storage there is ephemeral until you uncomment a volume, and the sample conn.env uses the password 1234. Setup goes through a browser installer whose critical SQL scripts may need several re-runs. The OGC API is read-only; edits go through WFS-T or the other APIs.

Related work

• Supabase: a general-purpose Postgres backend as a service with auth, realtime and storage (alternative)
• Anthropic: maker of Claude Code, one of the agents GC2's plugin installs into (context)

Still unclear

• What will GC2 Cloud cost after the beta, and will the 10-table and 10-sub-user limits change?
• Where is GC2 Cloud hosted, and what backup, retention and uptime terms apply to data stored there?