News for hackers. Stuff that matters.
Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by nilirl on Wednesday May 13, 2026 @01:17PM (#48124733)
Hi, site looks beautiful!

How does this compare to managing our own read-only replica with anonymized data?

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by vc289 on Wednesday May 13, 2026 @01:49PM (#48125126)
A true read replica won't let you write! So if you need to test something like a backfill and see if anything goes wrong you wouldn't be able to quite as easily.

We'd let you instantly clone prod + user defined auto-anonymization so you can test writes. The architecture also somewhat takes the place of an existing read replica if you want to use it like that to make it more cost efficient.

Also since we're using copy on write for the clones they're incredibly storage efficient and the autoscaling compute helps minimize cost on clones by minimizing excess compute uptime

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by jagged-chisel on Wednesday May 13, 2026 @02:02PM (#48125295)
> A true read replica won't let you write!

I mean, they said "read-only" ...

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by xnx on Wednesday May 13, 2026 @01:38PM (#48124977)
Ardent adds extra dependencies and cost.