frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Setting up a free *.city.state.us locality domain

https://fredchan.org/blog/locality-domains-guide/
291•speckx•3h ago•82 comments

Open Source Resistance: keep OSS alive on company time

https://ossresistance.com/
136•mikemcquaid•3h ago•53 comments

A History of IDEs at Google

https://laurent.le-brun.eu/blog/a-history-of-ides-at-google
64•laurentlb•4d ago•33 comments

Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

https://www.tryardent.com/
28•vc289•1h ago•14 comments

S-100 Virtual Workbench

https://grantmestrength.github.io/S100/
51•rbanffy•2h ago•9 comments

Xs of Y – roguelike that names itself every run. Written in 4kLoC

https://github.com/nooga/xsofy
68•andsoitis•3d ago•28 comments

The Emacsification of Software

https://sockpuppet.org/blog/2026/05/12/emacsification/
50•rdslw•11h ago•5 comments

Reverting the incremental GC in Python 3.14 and 3.15

https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014
136•curiousgal•3d ago•42 comments

Linux gaming is faster because Windows APIs are becoming Linux kernel features

https://www.xda-developers.com/linux-gaming-is-getting-faster-because-windows-apis-are-becoming-l...
23•haunter•2d ago•11 comments

Leaving GitHub for Forgejo

https://jorijn.com/en/blog/leaving-github-for-forgejo/
410•jorijn•5h ago•221 comments

The US is winning the AI race where it matters most: commercialization

https://avkcode.github.io/blog/us-winning-ai-race.html
64•akrylov•4h ago•169 comments

An idiot's guide to lead optimisation for proteins

https://magnusross.github.io/posts/protein-lead-optimisation-1/
97•magni121•2d ago•8 comments

New stainless steel can survive conditions for hydrogen production in seawater

https://www.sciencedaily.com/releases/2026/05/260510030950.htm
243•HardwareLust•2d ago•107 comments

Heritability of human life span is ~50% when heritability is redefined

https://dynomight.net/lifespan/
51•surprisetalk•1d ago•28 comments

I moved my digital stack to Europe

https://monokai.com/articles/how-i-moved-my-digital-stack-to-europe/
695•monokai_nl•6h ago•460 comments

Preserving Fisher-Price Pixter

https://dmitry.gr/?r=05.Projects&proj=37.%20Pixter
168•dmitrygr•2d ago•39 comments

Restore full BambuNetwork support for Bambu Lab printers

https://github.com/FULU-Foundation/OrcaSlicer-bambulab
619•Murfalo•20h ago•279 comments

Substrate (YC S24) Is Hiring a Technical Success Manager

https://www.ycombinator.com/companies/substrate/jobs/T2fMBhD-technical-success-manager
1•kunle•6h ago

Haiku

https://www.haiku-os.org
109•tosh•1h ago•50 comments

Twin brothers wipe 96 government databases minutes after being fired

https://arstechnica.com/tech-policy/2026/05/drop-database-what-not-to-do-after-losing-an-it-job/
67•jnord•19h ago•23 comments

Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model

https://github.com/cactus-compute/needle
590•HenryNdubuaku•1d ago•172 comments

Deterministic Fully-Static Whole-Binary Translation Without Heuristics

https://arxiv.org/abs/2605.08419
273•matt_d•13h ago•64 comments

Nailing jelly to a wall: is it possible? (2005)

https://greem.co.uk/otherbits/jelly.html
46•microsoftedging•4d ago•17 comments

Web Server on a Nintendo Wii

http://wii.sjmulder.nl/
83•adunk•3d ago•31 comments

Using OR-Tools CP-SAT for Scheduling Problems

https://atalaykutlay.com/or-tools-cp-sat-for-scheduling-problems.html
60•akutlay•7h ago•22 comments

Kraftwerk's radical 1976 track

https://www.bbc.com/culture/article/20260511-kraftwerks-radical-1976-track-radioactivity-became-a...
218•tcp_handshaker•19h ago•190 comments

Kickstarter is forced to ban adult content by payment processors

https://kotaku.com/kickstarter-is-the-latest-platform-seemingly-forced-to-ban-adult-content-by-pa...
229•stalfosknight•2h ago•175 comments

50K Tahoe residents need power as utility eyes redirecting lines to data centers

https://fortune.com/2026/05/12/lake-tahoe-data-center-49000-residents-power-source/
87•cdrnsf•2h ago•83 comments

Cost of enum-to-string: C++26 reflection vs. the old ways

https://vittorioromeo.com/index/blog/refl_enum_to_string.html
50•sagacity•9h ago•54 comments

How to make your text look futuristic (2016)

https://typesetinthefuture.com/2016/02/18/futuristic/
459•_vaporwave_•21h ago•58 comments
Open in hackernews

Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

https://www.tryardent.com/
28•vc289•1h ago
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 gotten dramatically more capable at handling complex engineering tasks. But without access to a realistic sandbox at the DB layer for testing, they ship garbage that can take down production databases. I spent over a year building an AI Data Engineer that failed for this exact reason. Evan spent the last 12 years in data engineering and hit this wall building agents at his last company.

Ardent was built to make it possible for coding agents to get near instant access to production-like sandboxes so they can test their work. To do this we write a replication stream out of the target DB, scaling with kafka onto a read replica with copy on write enabled and autoscaling compute (we currently prefer neon as a primary branching engine due to their implementation of these properties).

Our replication stream uses logical replication + ddl triggers to enable usage on any hosted postgres DB since most platforms do not allow physical replication which is traditionally used for creating replicas.

This provides a few primary benefits:

1. Does not require a platform migration to a DB provider like neon, allowing strong separation of production and development concerns. 2. Minimal impact on the production database while allowing clones to spin up in <6s, even at TB scale with copy-on-write

Security matters a lot with cloning production so we run a proxy layer to generate custom postgres URLs and route all connections to allow more granular access control to clones, prevent credential leak, and follow a split plane architecture to allow full data residency on your cloud through BYOC.

We also support anonymization through the ability to register SQL that runs on branches before they are returned. This has been used for PII redaction and branch modification.

Our goal is to make every data infrastructure platform “cloneable” in one place so agents can fully test the impact of their changes on production like data environments without risk.

Here's a demo of it: https://youtu.be/5S1kwPtiRU0

We’d love to understand how you work with coding agents on the DB and if you try Ardent (it's free to get started) what worked, what broke and what’s missing.

Comments

znnajdla•1h ago
“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•17m ago
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.

nilirl•58m ago
Hi, site looks beautiful!

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

xnx•37m ago
Ardent adds extra dependencies and cost.
vc289•25m ago
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

jagged-chisel•12m ago
> A true read replica won't let you write!

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

cphoover•57m ago
How many people are giving an LLM Agent full read access to their production data? That seems nuts to me.
jedberg•47m ago
I'm much more worried about people who give full write access to their agents! But at least this solves that problem.
cphoover•9m ago
Jedberg... Wow an internet legend replied to me! ><

> I'm much more worried about people who give full write access to their agents! But at least this solves that problem.

Yeah it goes without saying that write access would be crazy... But, it seems like people don't really care about the fact that they are just giving their private data to companies like Anthropic, OpenAI and Google.

> Branch anonymization Branches default to a full copy of your production data.

<-- This doesn't seem a safe default to me...

Perhaps a data policy should be required to be in place before a branch can be cloned... The default configuration giving the LLM full prod data access by default, is a bad standard to set, I think.

jedberg•4m ago
> Jedberg... Wow an internet legend replied to me!

Hey, I put on my pants the same way you do: by having my staff hold them up while I jump into them.

> But, it seems like people don't really care about the fact that they are just giving their private data to companies like Anthropic/Open AI and Google.

This isn't quite as risky as it seems. All of them have a TOS that says if you pay them enough money they won't train on your data. But you're right that there are probably a lot of people who aren't on those plans sharing private data.

> > Branch anonymization Branches default to a full copy of your production data. > <-- This doesn't seem a safe default to me...

Agreed, and I'm sure it will cause trouble if you don't also bring along with the copies the internal controls around access logging.

But also, for smaller companies, this isn't an issue since they don't have SOC2 and the other compliance needs yet. So it's probably a sane starting place for Ardent at this time. Most small startups let everyone in the company access the full database anyway.

> Perhaps a data policy should be required to be in place before a branch can be cloned... The default configuration giving the LLM full prod data access by default, is a bad standard to set, I think.

Or at least an easy way to copy it from the database you're branching from.

jedberg•49m ago
Looks interesting, curious what your moat here is. What prevents Supabase/Neon from doing this? Actually don't they already do this? How does this differ from the branching Neon and Supabase already offer?
vc289•30m ago
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 full clone of the DB.

Neon does support copy on write branching natively and autoscaling compute but you make certain performance tradeoffs. A lot of the folks we've talked to that use RDS or Planetscale are reliant on things like query latencies supported by that platform's specific architecture but also want the ability to test on branches. We let you get the best of both worlds (branch but leave your DB where it is and freely choose your production environment based on prod concerns)

Supabase does have branching but they do not branch the data so you can't test any interactions that rely on the data. You can restore from backup as an option but this slows down based on data size since you're actually moving data as opposed to copy on write.

Longer term we want to be the place you branch all your data infra. So expanding to S3, Snowflake, MySQL etc.

For now though we're focusing on just postgres and getting it right!

fmajid•28m ago
Doesn't look open-source. If you are interested in having a Neon or git-like branching for PostgreSQL experience, have a look at Xata, which is based on ZFS like Delphix was:

https://github.com/xataio/xata

eugercek•2m ago
If you use xfs (+`file_copy_method=CLONE`) you can do this with Postgres 18.

`CREATE DATABASE clankerdb TEMPLATE sourcedb STRATEGY=FILE_COPY;`.

But Ardent can be useful for many, because cloud providers uses heavily restricted Postgres. And many use Aurora, which doesn't event let configure the `long_line_prefix`.

But if cloud providers add file_copy_method=CLONE compatible managed pg ...

ref: https://boringsql.com/posts/instant-database-clones/