I'm building an open-source platform for your database, API, auth and apps

Описание и применение

Excalibase объединяет базу данных, API, аутентификацию, права доступа, реальное время и хостинг приложений в одной платформе, упрощая разработку и снижая задержки.

Задача

Developers need a unified platform that provides a database, API, authentication, real‑time features, and app hosting without managing separate services.

Результат

Excalibase consolidates database, API, auth, permissions, real‑time, and app hosting into a single platform, reducing network latency, simplifying permission enforcement, and enabling rapid deployment via AI tools.

Рабочий процесс

• Create a project in Excalibase
• Define database schema (tables, columns)
• Add tables to generate API endpoints
• Set row/column permissions per role
• Configure authentication for app users
• Deploy app containers alongside the database
• Use MCP server to manage tables, permissions, and deployments via AI tool

Доказательства

It started as a GraphQL engine for Postgres, because I like SQL. It's now an open-source platform as a service: one place for the database, the API on top of it, auth, and the apps that use it.

Источник

When you create a project, you get: A database. Postgres, or MySQL from this week's release. Backups and point-in-time restore are built in.

Источник

A GraphQL and REST API generated from your schema. Add a table and it's in the API.

Источник

Permissions per row and per column, written per role. "Users can only read their own notes" is one rule, and it applies to GraphQL, REST and realtime alike.

Источник

Auth for your app's own users.

Источник

Realtime subscriptions and functions.

Источник

App hosting: your containers run next to the database, so there's no network hop to a database in another region.

Источник

An MCP server, so your AI coding tool can create tables, set permissions and deploy your app. It only gets your token's permissions, and secrets don't show up in the chat.

Источник

A GraphQL query, nested relations and the permission rules all compile into one SQL statement. One request means one query to the database, whatever the nesting depth, and no N+1.

Источник

Run it anywhere: Hosted, One box (Docker or Podman), Kubernetes.

Источник