@xata

Postgres at scale — with copy-on-write branching, data masking, separated storage & compute , 100% Postgres and your own cloud

 🌏 Earth
xata.io
Joined November 2020
  • Tweets1.5K
  • Following417
  • Followers4.1K
345Media
Introducing the latest in Postgres for agentic workloads. Agents can now branch or wake your Postgres database instantly.
6
6
2
101
355,699
A coding agent wants a database per task: created when the work starts, removed when it ends. One shared staging database was never going to keep up. Our CEO @monicasarbu on what to do instead, 2:50pm PT on Stage 2 at WeAreDevelopers in San José: "Databases in the Agent Era."
1
1
237
The short version: a copy of production per task, ready in seconds with copy-on-write, and a way to get real data into it without the PII. wearedevelopers.com/world-co…

Databases in the Agent Era · WeAreDevelopers World Congress North America

We are entering a new era where AI agents are first-class users of data infrastructure. These systems don’t behave like traditional applications. They operate in loops, branch workflows continuousl…

wearedevelopers.com
1
86
Live now: Graham walks through Account Observatory, the internal tool our GTM team built on one Postgres database. 30 minutes, then your questions. youtube.com/watch?v=9ZHnGlX-…

AI-native GTM Ops: Account Observatory with Scale-to-Zero Postgres

Xata is a managed Postgres company. Our product lets a team copy a ...

youtube.com
3
21,590
One organization's first week in Account Observatory: signed up, first branch the same day, then instance hours and a payment method. We built the tool to spot the customers who don't get this far, and reach out before they give up. When a cohort teaches us something new, we update the picture on a branch and ship it through a pull request. Graham walks through the whole loop tomorrow at 8:30am PT. Free on YouTube, recording included. youtube.com/watch?v=9ZHnGlX-…
Xata Workshops episode 1, Account Observatory: how our GTM team built an internal tool on real customer data. Graham Thompson, Head of GTM. Thursday September 24, 8:30am PT.

ALT Xata Workshops episode 1, Account Observatory: how our GTM team built an internal tool on real customer data. Graham Thompson, Head of GTM. Thursday September 24, 8:30am PT.

1
4
40,911
Xata 🦋 retweeted
Tudor Golubenco
@tudor_g
Sep 22
Replying to @barbinbrad @planepowers @turbopuffer @e2b @ClickHouseDB @rocicorp
@xata for Postgres with CoW branching. We built it from the start with BYOC in mind.
1
2
191
Our GTM team built an internal tool to stay customer focused as a PLG-first company. Account Observatory pulls PostHog, Pylon and Clarify into one Postgres database, so decisions about onboarding come from real customer behavior. Changes ship from a database branch through a pull request, live tool untouched. Thu Sep 24, 8:30am PT, Graham walks through it. Free on YouTube, recording included. youtube.com/watch?v=9ZHnGlX-…

AI-native GTM Ops: Account Observatory with Scale-to-Zero Postgres

Xata is a managed Postgres company. Our product lets a team copy a ...

youtube.com
1
3
119,117
Need production data to debug a slow query? Normally, you have to: • Isolate the data • Debug the query • Validate the fix • Deploy the fix With the Xata MCP server and Codex, you can do all of this just by talking to an agent. Branch your Postgres database in seconds, no matter how large it is, and let AI assist you with solving slow query issues. Watch how it works 👇

This video is larger than Cloudflare's 512 MB cache, so it can't be played through. More donations are needed to cover a larger cache. Donate

4
1
7
476
Setup for Codex, ChatGPT and the other supported clients: xata.io/docs/platform/mcp The server URL is api.xata.tech/mcp

MCP Server - Xata

Connect Cursor, Claude, VS Code, and other MCP clients to Xata

xata.io
1
144
Coding agents write and run SQL now. The same connection that lets one fix a query lets it drop a table. Yours can work against real production data without working against production, and without seeded data that looks nothing like production. Read more: xata.io/blog/introducing-the…
2
2
8
676
more replies
With 78.7% of the rows tied on the value we sort by, the query wasn't deterministic. Which rows appeared on a page could change whenever the query plan changed. And it did, as soon as the agent ran ANALYZE. That is not in the schema, and it is not in seeded data either, because nobody seeds 79% of a table at one value on purpose. It deleted its branch on the way out. None of that was in the repo, and the repo is all an agent usually gets.
1
99
You only need the URL: api.xata.tech/mcp Any MCP client that speaks Streamable HTTP can connect, over OAuth in the browser or an API key for CI. Nothing to install locally. Claude Code: claude mcp add --transport http --scope user xata api.xata.tech/mcp then run /mcp to sign in. Works with Claude Code, Cursor, VS Code, Zed, Codex and any MCP client that supports Streamable HTTP: xata.io/docs/platform/mcp
84
Xata is coming to Azure. Branch-native Postgres. A copy-on-write branch of an existing database in seconds, whether the parent is 1GB or 1TB. Xata branches only incur costs for changed data plus compute while awake. A sleeping branch is basically free. Join the waitlist and we will tell you the moment it is ready. xata.io/get/azure
2
3
3
570
Xata 🦋 retweeted
Tudor Golubenco
@tudor_g
Aug 15
The security research done by @mdisec is incredibly valuable to @xata and the whole Postgres ecosystem. Tons of security fixes in various extensions and core Postgres have been merged lately thanks to his research. I am very grateful for our collaboration!
Mehmet INCE
@mdisec
Aug 14
I went looking for a managed-Postgres provider. Instead, I found a vulnerability in a 4-star PostgreSQL extension available everywhere! and turned it into code execution at @neondatabase, @supabase, @xata and more. Part 1/6 | Extension Risks Are Real mehmetince.net/part-1-6-syst…
1
2
17
3,310
pgp_sym_decrypt with the wrong key throws "Wrong key or corrupt data". It does not hand back garbage bytes. That is the PGP format's integrity check, and it is a useful property if you are encrypting columns with a different key per tenant. A query that picks up the wrong tenant's key fails loudly, instead of returning plausible nonsense that nothing downstream is checking. Read about it here: xata.io/blog/multi-tenant-by…
1
1
385
Finding a slow query on a Postgres branch, without leaving the terminal. xata branch query-insights ranks that branch's statements by cost, flags the slow ones, and prints the command to inspect any of them. Logs and instance metrics are one command away.
1
1
2
345
xata branch query-insights active reads pg_stat_activity, so it shows what is executing right now, with each query's state and wait event. Currently running queries are the one part of this with no console page.
1
1
118
Query Insights is live in the console too, on every branch, with any statement whose slowest run passed one second highlighted. A walkthrough that goes from a slow query in the console to the statement in your terminal: xata.io/docs/tutorials/find-…

Find and fix slow queries on a Xata branch - Xata

Use query insights, branch logs, and instance metrics to find slow PostgreSQL queries, understand why they are slow, and confirm the fix worked.

xata.io
1
87
If you're giving every coding agent and every PR its own Postgres branch, you're not clicking those into existence, you're scripting them. So the CLI output has to be readable by a script, or an agent. Now it is. Piped output is clean plain text, and xata branch list --json is the reliable path for anything automated. When branches are getting spun up by scripts and agents, parseable is exactly what you want.
3
1
7
839
Load more