[znnajdla]

“Never impacts production data” is impossible to guarantee. Playing with real world data often has side effects outside of the database. For example if you store oauth tokens to external services in your DB (customer integrations) it’s easy to mess up your customers data through a bad API call (been there done that).

There is still value in carefully testing on your prod DB, but for that you could just easily maintain a read replica. I don’t see the need for a SaaS here.

[vc289]

One of the main things people use us for is ease of testing writes on a per dev/agent basis which would be difficult on a read replica!

On the real world data impact I absolutely agree. We added something called "branch hooks" which essentially let you define SQL to run against the branch before it's returned

This lets you essentially anonymize and modify the branch to scrub unintended external side effects.

It's something that we're still working on though and trying to design the right abstractions around because we want to get that part right.

[999900000999]

If it’s production data I probably don’t trust a random startup with it.

I’m very confused as to the target market here

[vessenes]

I’ll bite. You’re a dev at random mid size company and tasked with using this newfangled agentic tech to implement an intranet feature everybody wants and nobody else wants to build.

How do you get a staging and dev db together that’s going to let you test your migrations?

[999900000999]

Spin it up my self inside our VPC ?

I can only imagine this being fine for 1 person side projects.

[tommy29tmar]

[flagged]

[dang]

Your comments are getting classified by our software as LLM-generated and/or LLM-edited. It's impossible to be certain, of course, but if this is the case—can you please not do this? It's not allowed here - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079. We end up banning accounts that do this repeatedly and I don't want to ban you.

LLMs are amazing and we use them heavily ourselves - but not for modifying text that is to be posted to HN. Doing so leaves imprints on the language that readers are increasingly allergic to, and we want HN to be a place human conversation.