One project, six parts
Everything is running from minute one.
There is nothing to enable, install, or wire up yourself. It all shares one hostname and one key, so a single base URL is enough for all your client libraries.
Full PostgreSQL
You are superuser inside it. Connect with psql, DBeaver, or any driver through your project's own port, always encrypted.
pgvector, pg_trgm, pgcrypto, citext, pg_stat_statements
Automatic REST API
Every table gets an endpoint at /rest/v1 without writing a backend. The database holds the permissions: your Row Level Security decides who sees which rows.
https://<project>.podx.my.id/rest/v1
Authentication
Sign-up, sign-in, and tokens for your users at /auth/v1. The same token is used by the REST API to pick a role: one key, one permission model.
/auth/v1
File storage
Upload and serve files through /storage/v1, on a volume that belongs to your project, not a temporary directory that disappears when a container moves.
/storage/v1
Connection pooler
Hundreds of application connections are folded into a few database connections. Handy exactly when traffic grows, and still over TLS.
transaction mode
Backups that run themselves
A daily backup plus a continuous archive of the transaction log, so the database can be restored to a point in time. Nothing for you to switch on.
daily + point-in-time recovery
Not in Base yet: read replicas and automatic failover (one instance serves reads and writes), and Realtime and Edge Functions. If your app depends on one of them, Base doesn't replace it yet.
Managed
What sets it apart from installing Postgres yourself
Installing PostgreSQL takes five minutes. What takes time is everything that comes after, and that is what you pay for here.
- Daily backups + point-in-time recovery
- A backup is taken every day and the transaction log is archived continuously. If data is deleted or damaged, the database is restored to the minute before it happened.
- You are superuser in your own database
- Create extensions, roles, and schemas as you like. No command allow-list, no ticket for something that should be one line of SQL.
- pgvector is already inside
- Along with pg_trgm, pgcrypto, citext, and pg_stat_statements. A search or AI app doesn't need a separate database.
- Open Studio in one click
- Browse tables, run queries, and edit data through XPod Studio straight from the console, with no client to install.
- Settings follow the size you pick
- The connection limit is computed from your plan's memory, not one default number for everyone.
- Connect from outside, over TLS
- A public TLS endpoint, so an app anywhere can use it. The connection string shown never carries the password.
Seven products, one platform
Which one do you need?
The difference is when your code runs: from always on, to not running at all until it is needed.
- What you bring
- An app from the catalog
- When it runs
- Always
- How it is billed
- Monthly
- What you bring
- Your own container image
- When it runs
- Always
- How it is billed
- Monthly, per active minute
- XPod Baseyou are here
- What you bring
- A PostgreSQL database
- When it runs
- Always
- How it is billed
- Monthly
- What you bring
- Static files
- When it runs
- Never
- How it is billed
- Plan + bandwidth
- What you bring
- Code in a container
- When it runs
- On a schedule
- How it is billed
- Per second of execution
- What you bring
- Code or a container
- When it runs
- When messages arrive
- How it is billed
- Per processed message
- What you bring
- One function (handler)
- When it runs
- When called
- How it is billed
- Per call + GB-second