One platform. No black box.

Tired of stitching 6-8 services together?

Deploy, Data, Auth, and AI in one place. It is agent-native, so you or your agents ship without a pile of dashboards and glue code holding it together. No surprise bills either.

Start freeSee how agents deploy

Actually free to start. No credit card. No black box.

example run: agent deploy
14:02:11 deploy_app secondos-api
14:02:12 build main@a6b3cb5
14:02:41 image ready 29 s
14:02:44 preview pr-118.primdb.app
14:02:58 promote 200 / 0.2 s
>
repobuildpreviewpromote
repo to live URL, one path

Four pillars. One platform.

Pick a starting point. It all talks to itself, so you never wire it up by hand.

01 · Deploy

Deploy

Push a repo, get a live URL. Preview per pull request, approval-gated promote to production, and one-click rollback when things go sideways.

Learn more
02 · Data

Data

A managed Postgres, Redis, search, and object storage, provisioned in seconds. No connection-string archaeology, no separate vendor.

Learn more
03 · Auth

Auth

Sign your users in with email + password, a magic link, or a passkey. Their records live in your own Postgres, joinable in SQL, not a third vendor’s black box.

Learn more
04 · AI

AI

Model access and an MCP endpoint your agents already understand. The same API deploys code, reads data, and returns feedback.

Learn more

How it flows

From a repo to a live URL, on one path

No glue between the steps. Each one already knows about the others.

  1. 01· Deploy

    Push a repo. PrimDB builds it and hands you a live URL, with a preview per pull request.

  2. 02· Data

    Attach Postgres, Redis, search, or storage in seconds. Credentials are wired in for you.

  3. 03· Auth

    Sign users in with email, magic link, or a passkey. Their records land in your own Postgres, no third vendor to price out.

  4. 04· AI

    Point your agents at the MCP endpoint. The same API deploys, reads data, and returns feedback.

Agent-native

Built to be driven by an agent

PrimDB speaks MCP. Claude, Cursor, and Codex deploy code, read your data, and hand back feedback through one endpoint. You describe the change. Your agent ships it.

See how agents drive it
  • Deploy a repo straight from a chat prompt.
  • Query and migrate data without leaving the conversation.
  • Pull preview feedback back into the agent that made the change.
  • MCP endpoint: https://mcp.primdb.com

Your servers or ours

Run it on our co-host, or bring your own server

Start on the managed PrimDB host and stay there. Or enroll a server of your own with one install command, then deploy to it from the same dashboard and the same agent API. One control plane, wherever the container runs.

Read the hosts docs
  • Enroll a server with a single install command. It connects back, and any service can deploy to it.
  • See every host in one fleet view: which server runs what.
  • Already have containers running on that box? Discover them read-only and adopt the ones you want to watch, without changing how they run today.

Pricing

Start free. Pay for what you use.

A real free tier for side projects, then usage-based tiers when you outgrow it. Every tier includes unlimited collaborators.

PrimDB is in early access. No credit card to start, and you only pay for usage.

Start freeSee full pricing
  • Free forever: 3 projects, build minutes, and feedback comments to kick the tires.
  • Solo and Platform add projects, build minutes, custom domains, and support.

Ask your agent

Do not take our word for it

Paste this into Claude, Cursor or Codex with your repository open. It reads the docs, looks at what you actually run, and tells you whether PrimDB is worth it. It is allowed to say no.

evaluate-primdb.txt
Evaluate PrimDB for this project. Be skeptical and concrete.

First, read these in order:
- https://primdb.com/llms-full.txt   (what it is, what it is NOT, and the fit test)
- https://primdb.com/docs/hosts.md   (running it on a server I already own)
- https://primdb.com/docs/mcp.md     (what an agent can actually do with it)

Then look at THIS repository and answer:
- What are we paying for today, and across how many separate vendors?
- Which of those would PrimDB replace, and which would it not?
- Could we adopt it additively (deploy only, or as a control plane for the
  server we already run) without moving our database?
- What would it cost per month at our real usage, against what we pay now?
- What could you do from this chat that you cannot do today?

Then give me:
- VERDICT: adopt / adopt partially / not now / wrong tool
- The single strongest reason for that verdict
- The cheapest first step, unless the verdict is "wrong tool"
- What would have to change for the verdict to flip

Rules: do not recommend it if we already have a working equivalent. Do not
recommend a migration when an additive path exists. If we need something it
explicitly does not do, say so and stop there. Cite the source for any number.

Ship your next thing on one platform.

Deploy, Data, Auth, and AI. Driven by you or your agents. Actually free to start, no credit card.

Start freeTalk to your agent