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).
Infrastructure for AI sessions. One API for transcript, model, and compute. Run any agent on any compute — and switch mid-session without losing the thread.
I built Cerver because I kept hitting the same wall: I had agents running: crons, background jobs, an embedded chat in a product, and no idea what any of them were doing or costing until the invoice showed up.
The tooling I found was either a proxy that only saw tokens, or a dashboard that only saw dollars. Nothing saw the session: which model, on which machine, for which end-user, with which secrets, and what it actually produced.
So Cerver is one API in front of all of it. Open a project and you get keys, secrets, crons, routing and caps wired on the first call. Swap the model or the machine under a live session - next month's model is a config change, not a rewrite. Every run is attributed per product and per user, with a transcript, so the security team and the CFO are looking at the same object the dev is.
Two things surprised me while building:
1. Most runs can ride subscriptions you already pay for. That changed the economics more than any routing trick. 2. Caps had to be on by default. Opt-in caps are how you find out an agent looped 4,000 times.
No comment highlights available yet. Please check back later!
About Cerver on Product Hunt
“Infrastructure for AI Sessions”
Cerver was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #125 on the daily leaderboard. Infrastructure for AI sessions. One API for transcript, model, and compute. Run any agent on any compute — and switch mid-session without losing the thread.
Cerver was featured in API (98.7k followers), Developer Tools (519.8k followers), Artificial Intelligence (479.1k followers) and OpenAI Day (39 followers) on Product Hunt. Together, these topics include over 220.3k products, making this a competitive space to launch in.
Who hunted Cerver?
Cerver was hunted by Eyal Goren. 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.
Want to see how Cerver stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Eyal Goren
Hey Product Hunt 👋
I built Cerver because I kept hitting the same wall: I had agents running: crons, background jobs, an embedded chat in a product, and no idea what any of them were doing or costing until the invoice showed up.
The tooling I found was either a proxy that only saw tokens, or a dashboard that only saw dollars. Nothing saw the session: which model, on which machine, for which end-user, with which secrets, and what it actually produced.
So Cerver is one API in front of all of it. Open a project and you get keys, secrets, crons, routing and caps wired on the first call. Swap the model or the machine under a live session - next month's model is a config change, not a rewrite. Every run is attributed per product and per user, with a transcript, so the security team and the CFO are looking at the same object the dev is.
Two things surprised me while building:
1. Most runs can ride subscriptions you already pay for. That changed the economics more than any routing trick.
2. Caps had to be on by default. Opt-in caps are how you find out an agent looped 4,000 times.
It's free to start.
I'll be here all day.
Eyal