This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Chronos Gateway
The firewall between AI agents and your production data
AI agents have already wiped production databases. Chronos Gateway is how you let yours write to real customer data anyway. Every agent gets a run token, never your Postgres password, and a private copy of one customer's rows. Safe changes merge back in one transaction, every row checked against live data. Deletes and big changes stop and wait for a human, who approves in plain English. Your row-level security still decides what it can write. Self-hosted. Free. Postgres 12-18, Supabase, Neon.
Hi Product Hunt, Abhishek here again. On Friday we launched Chronos DB. The first thing almost every team asks us is whether they'd have to move their data into a new database. They don't want to, so this is the part that sits beside the Postgres you already run.
Your backend opens a run for one task and one customer. The agent gets a run token, not your password, and works over SQL or MCP in a private copy of that customer's rows. Columns you mark are masked, so it reads a hash or the last four characters instead of the real value.
When the agent is done, your rules decide. By default, up to 500 changed rows and no deletes are written to Postgres on their own, in one transaction, with each row checked against what's live. If someone edited a row in the meantime, the change stops and their edit stays. Anything outside the rules waits for a person, who sees "Remove lead Hooli" instead of a SQL log and approves from the console, a one-time link, Slack, or a widget in your own app.
Your app keeps reading and writing Postgres exactly as it does today.
Where it stands: it's self-hosted only, licensed BUSL-1.1 (not open source), and tested on Postgres 12 to 18, Neon and Supabase. RDS and Cloud SQL aren't tested yet.
If your agents write to customer data today, what's the change you'd least want them to get wrong?
About Chronos Gateway on Product Hunt
“The firewall between AI agents and your production data”
Chronos Gateway was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #69 on the daily leaderboard. AI agents have already wiped production databases. Chronos Gateway is how you let yours write to real customer data anyway. Every agent gets a run token, never your Postgres password, and a private copy of one customer's rows. Safe changes merge back in one transaction, every row checked against live data. Deletes and big changes stop and wait for a human, who approves in plain English. Your row-level security still decides what it can write. Self-hosted. Free. Postgres 12-18, Supabase, Neon.
On the analytics side, Chronos Gateway competes within Developer Tools, Artificial Intelligence, GitHub and Database — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how Chronos Gateway performed against the three products that launched closest to it on the same day.
Who hunted Chronos Gateway?
Chronos Gateway was hunted by Abhishek DG. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Chronos Gateway including community comment highlights and product details, visit the product overview.
Abhishek DG
Hi Product Hunt, Abhishek here again. On Friday we launched Chronos DB. The first thing almost every team asks us is whether they'd have to move their data into a new database. They don't want to, so this is the part that sits beside the Postgres you already run.
Your backend opens a run for one task and one customer. The agent gets a run token, not your password, and works over SQL or MCP in a private copy of that customer's rows. Columns you mark are masked, so it reads a hash or the last four characters instead of the real value.
When the agent is done, your rules decide. By default, up to 500 changed rows and no deletes are written to Postgres on their own, in one transaction, with each row checked against what's live. If someone edited a row in the meantime, the change stops and their edit stays. Anything outside the rules waits for a person, who sees "Remove lead Hooli" instead of a SQL log and approves from the console, a one-time link, Slack, or a widget in your own app.
Your app keeps reading and writing Postgres exactly as it does today.
Where it stands: it's self-hosted only, licensed BUSL-1.1 (not open source), and tested on Postgres 12 to 18, Neon and Supabase. RDS and Cloud SQL aren't tested yet.
If your agents write to customer data today, what's the change you'd least want them to get wrong?