Viewing profile — vc289
vc289
HN member- Joined
- Tue, Dec 13, 2022, 10:01 PM UTC
- HN karma
- 68
- Public activity
- 18 items
- HN profile
- View on Hacker News ↗
About vc289
Recent public activity
-
comment
Comment #48141954
Totally makes sense. We do offer a pure PAYG tier (starter) that scales completely dynamically to workload But seems like this may be less about the absolute price but more about t…
-
comment
Comment #48138839
It does clone the data. It uses copy on write to clone so data size won't slow it down since it's a metadata operation instead of actual data movement It clones the entire DB so it…
-
comment
Comment #48130893
We have ways to scrub PII/manipulate the data on the clone per branch. It's called branch hooks and lets you register SQL to be run against the branch after it's created but before…
-
comment
Comment #48129503
We've got docs on how we did it :) https://docs.tryardent.com/architecture But essentially we get around the restrictions of the original DB by replicating into a different postgre…
-
comment
Comment #48126226
>> I'm sure it will cause trouble if you don't also bring along with the copies the internal controls around access logging Yep! Agreed. We've tried to combat this with the "branch…
-
comment
Comment #48125239
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 a…
-
comment
Comment #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 insta…
-
comment
Comment #48125063
We enable branching on any postgres DB through our architecture. So if you're on RDS, Planetscale, etc you can keep your DB where it is but also get the ability to branch with a fu…
-
story
Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration
Hey HN! We’re Vikram and Evan from Ardent ( https://tryardent.com ). We're building database sandboxes for you and your coding agents. In the last two years coding agents have gott…
-
comment
Comment #47915735
It's fundamentally impossible to stop an agent from performing a destructive action through instruction Llms are just too creative. They will explore the search space of probable p…
-
comment
Comment #46627128
Not true for the db layer :) Look into copy on write branching. We built this natively into our AI Data Engineer ( https://tryardent.com ) so it could make modifications to databas…
-
comment
Comment #46627002
If you're on postgres happy to have you try what we built at Ardent ( https://tryardent.com ). Our agent makes instant copies of your db for the agent to operate on so there's 0 ri…
-
comment
Comment #46626981
Also, lots of people here have said to give it fine grained, read only access. This works if you want a copilot experience but doesn't allow you to fully let the agent do write-sty…
-
comment
Comment #46626954
We solved this exact thing for the database layer (postgres for now) with https://tryardent.com You can't trust any agent to be perfect with a real db so unless you find an infra l…
-
story
Show HN: Ardent – An AI Data Engineer
Hey HN! We’re Vikram and John, founders of ArdentAI ( https://www.ardentai.io/ ). We built ArdentAI to tackle the pain points of data engineering—time-consuming pipelines, manual t…
-
comment
Comment #42436112
[dead]
-
comment
Comment #41990541
It would be interesting to consider branchable DBs as part of the migration cycle, especially for forward and backwards time skips. While not dealing with that kind of scale yet, o…
-
comment
Comment #41968179
I'm building an AI Data Engineer @ Ardent AI. It's an autonomous AI Agent that can perform data transformations in your databases (mongodb,postgres,supabase for now) from plain eng…