Skip to content
excalibase

FAQ

Questions, answered straight.

Short answers to what people usually ask first. For detail, see the docs and the roadmap.

What is Excalibase?

An open-source platform as a service. A project gets a database (Postgres, MySQL or DocumentDB), GraphQL and REST APIs generated from its tables, permissions, auth for your app’s users, edge functions, file storage, containers for your own images, and static sites. You can use the hosted free beta, or run the whole thing yourself on Kubernetes or on a single Docker or Podman host.

How is it different from Supabase, Railway or Vercel?

They overlap with parts of it. Supabase is the closest on the database and API side: both give you Postgres with generated APIs, auth and storage. Railway and Vercel are closer on the hosting side, where Excalibase runs your containers and static sites next to the database. What Excalibase tries to do is put the database, the API, the users and the hosting in one project with one set of permission rules, and let you run all of it yourself.

Those products are older, larger and far more proven than this one. If you need what they have today, use them. Excalibase is a smaller project that is still in beta.

What is the license?

Apache License 2.0, for every repository in the GitHub organization.

Who runs it?

One person. It is a solo maintainer working on it nights and weekends, with a day job, since May 2025. That is why the roadmap is short and why some things are slower than a funded team would manage.

Where is my data hosted, and what are the beta limits?

On one server today, so there is no multi-region setup and a failure of that machine affects everyone on the hosted beta. The Free plan is deliberately small: one project with one small database instance, a couple of apps and a handful of sites. Backups are on, but treat the beta as a place to build and try things, not to keep the only copy of anything important.

Can I self-host it?

Yes, and that is a goal of the project. The whole platform runs on one Linux machine with Docker or rootless Podman, or on Kubernetes with Helm charts. A single host has no high availability. Static sites are served from Cloudflare, so a self-hosted install needs its own account to offer them.

Is it production ready?

No. It is a beta. The engine and the platform have automated tests and each release is exercised end to end, but there is one maintainer, one hosted server, and no uptime guarantee. Use it for side projects, prototypes and evaluation, and if you run it for something that matters, run it yourself and keep your own backups.

What does it cost?

The hosted beta is free. Paid plans are planned for later, and nothing is charged now. If that changes you will be told in advance, and you will not be charged unless you agree. Self-hosting costs only what your own machines cost.

How does the security model work?

Every request runs as exactly one role, and the engine enforces your row and column rules itself, inside the SQL it generates, for GraphQL, REST and realtime alike. A table with no permission for a role does not exist for that role. Your app’s end users are stored separately from your own tables, and only the auth service can read those tables, so a bug in your permissions cannot expose password hashes.

Tables are open to anonymous callers only if you give them a permission. If you find a hole, please write to hello@excalibase.io.