Xata through Squiid

What Xata is

Xata runs Postgres with an emphasis on what happens around the database rather than inside it. Copy-on-write branching creates a full-size staging database from production in seconds without copying the data, anonymisation rules mask personal fields as the branch is made, and zero-downtime schema migration tooling applies changes safely. The platform also handles separation of storage and compute so branches are cheap to keep around. The platform exposes a standard Postgres connection alongside its own API, so existing ORMs and migration tools keep working.

The staging problem this addresses is real in AI-coded projects. Testing a generated migration or a new feature against a tiny seed database proves very little, and testing against a copy of production means copying customer data onto a machine nobody audited. A branch that has the shape and volume of production with the personal fields scrambled is the version of staging teams actually want. Branch lifecycles can be tied to a pull request, so the staging database appears and disappears with the code it was created for.

Why connect it through Squiid

Xata is on the Squiid roadmap. When it lands, Squiid will provision the project, hold the database credentials and API key, and expose both the database and the platform API through https://api.squiid.io/v1/xata/... with Authorization: Bearer $SQUIID_API_KEY, with Postgres drivers working by base URL swap (gateway convention). Storage, compute and plan cost will bill at Xata's listed prices on your single Squiid invoice, and an agent creating branches will do it with a key you can rotate in one click.

• One account, one key, one bill, one dashboard. Xata sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Xata credentials. Your code carries SQUIID_API_KEY, so XATA_API_KEY, XATA_BRANCH, DATABASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Xata costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Postgres project with branching
• Copy-on-write staging branches from production
• Anonymisation of personal fields in branches
• Usage and plan on one Squiid invoice
• Xata list pricing, no markup

How to connect Xata

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces XATA_API_KEY, XATA_BRANCH, DATABASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/xata/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Xata charges a plan fee plus compute and storage usage, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Xata usage, with no markup and no per-request margin.

Xata has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Xata usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: dump the database and restore it into a project in your own Xata account; Xata has no project transfer we are confident of. Squiid never owns your code, your schema or your domain, and the gateway speaks Xata's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Xata through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Xata usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.