Get the weekly radar
One short email with the freshest products, every week.
Centia.io auto-generates REST, GraphQL, and realtime APIs from your PostgreSQL and PostGIS tables.
Grounded in available product and source data
Hand-writing CRUD endpoints for every table is the step Centia.io removes: define a data model in PostgreSQL, and the platform generates REST, GraphQL, Spatial SQL, and realtime WebSocket subscriptions over those tables automatically, rather than requiring a developer to build and maintain each endpoint by hand.
Geospatial data gets first-class treatment through built-in PostGIS 3.4 support, covering formats like GeoJSON, Shapefile, and GeoPackage — a detail that matters specifically for teams building mapping, logistics, or location-aware features rather than a generic CRUD app. Realtime WebSocket subscriptions push data changes to connected clients as they happen, and serverless functions let a team run sandboxed code on demand, on a schedule, or triggered by events, without standing up separate infrastructure for background jobs.
What sets Centia.io apart from a typical backend-as-a-service is native Model Context Protocol (MCP) support: coding assistants and LLM agents, including Cursor and Claude Desktop by name, can connect to the backend directly, which matters for teams building AI-agent-facing tooling rather than only human-facing apps. The SDK currently targets TypeScript and JavaScript, with authentication running on OAuth2 and rule-based access control, plus rate limiting, SQL parameterization, and role-based permissions on the security side.
Teams can run Centia Cloud as a managed service or self-host through Docker Compose, and the project is stated to be open source under the AGPLv3 license — a copyleft license worth understanding before building a closed-source product on top of a self-hosted deployment. Pricing is currently a free beta tier with limitations the site doesn't spell out in detail, and no other named tiers are published yet.
The site doesn't detail how schema changes propagate to already-generated REST, GraphQL, or realtime endpoints, so teams making frequent schema changes should test that behavior directly rather than assume APIs update automatically without any redeployment step.
Yes — the site states native Model Context Protocol (MCP) support, naming Cursor and Claude Desktop specifically as tools that can connect as custom agents, which is a less common feature among backend platforms generally aimed at human developers only.
AGPLv3 is a copyleft license, which typically requires that modifications made to the software be released under the same license if the modified version is used to provide a network service — worth reviewing directly with the actual license text before building a closed-source product on top of a self-hosted deployment.
The site states built-in PostGIS 3.4 support for GeoJSON, Shapefile, and GeoPackage formats, positioning it specifically for applications working with mapping or location data rather than only generic relational data.
The site states the SDK is available for TypeScript and JavaScript; it doesn't name other language SDKs, so teams working primarily in other languages would need to integrate through the generated REST or GraphQL APIs directly.
