Skip to main content

Intro

Centia.io is a Backend as a Service (BaaS) that gives you a production‑ready backend — data, auth, realtime, and tooling — so you can focus on building great apps instead of maintaining servers.

What you get​

  • Data you model the way you want
    • Define schemas, tables, columns, and constraints using the Web App, CLI, or API. See Getting started to create your first schema and table. Read the guide →
  • Realtime APIs
  • Client SDKs
  • Authentication and OAuth
  • Objects and files
    • Store and serve files alongside your data. Objects →
  • Open, developer‑first tooling
    • A web app for visual management, a CLI for automation, and familiar SQL workflows that fit into your existing toolchain. Open source →

Three ways to interact​

Centia.io gives you three interfaces — use whichever fits your workflow:

  1. Web App — A visual interface for managing schemas, tables, users, clients, and more. The quickest way to explore and configure your backend. Open console →
  2. CLI — Automate provisioning from the terminal. Great for scripting, CI/CD, and local development. Install the CLI →
  3. API — Full HTTP REST and WebSocket access for every operation. Ideal for programmatic control and integration. API reference →

API conventions​

The REST API follows a few rules across all /api/v4 resources, so once you know one endpoint you know them all:

  • Lists are bare JSON arrays, single resources are objects.
  • One or many by the same route. A GET or DELETE with a single id answers with (or acts on) one resource; a comma-separated list of ids in the same path segment answers with an array or acts on all of them. Likewise a POST takes either one object or an array of objects.
  • All-or-nothing on lists. Every element is validated first — an unknown id, a bad field or a conflict in any element means nothing is created, deleted or queued, and the error names the element.
  • Errors carry an HTTP status and a stable errorCode string (such as JOB_NOT_FOUND or INVALID_REQUEST) that each page documents.

How you’ll build with Centia.io​

Choose deployment:

Then:

  1. Create a backend and sign in.
  2. Model your data with the Web App, CLI, or API (schemas, tables, columns). Follow Getting started →
  3. Connect your app with the SDK and start reading/writing data. SDK →
  4. Add realtime subscriptions where your UI needs to react instantly. Realtime →
  5. Secure access with OAuth and enforce rules per user or role. OAuth → • Rules →
  6. Ship. Your frontend can be deployed anywhere; Centia.io runs and scales the backend for you.

When to use Centia.io​

Use Centia.io when you want to:

  • Ship quickly without building auth, data APIs, and realtime from scratch.
  • Keep full control over your data model and query with SQL.
  • Build reactive experiences (e.g., live dashboards, chats, collaborative apps).

Next steps​

Head to Getting started to create your first schema and table, then hook it up to your app with the SDK. Start building →