Cloptima puts your own rules in front of every AI call: a virtual key per app with its own policy, guardrails that mask data before it leaves, tool policy for agents, budgets that block, session replay, an edge gateway inside your network, and prices each call on an attributed ledger before the provider sees a token. Setup is one line.
Why I built it: AI calls go straight from app code to a model provider, while the rules a company actually cares about (what it may spend, which data may leave, which tools an agent may use) live in a policy document, not in the request path. So teams either slow down to review everything by hand, or ship and find out later. I wanted those rules to run on every call, before it leaves, without asking developers to rewrite anything.
What's in it today: a key per app, guardrails that mask data before it leaves (and can watch first before they block), tool policy for agents, budgets that block at the line, session replay, and an edge gateway that runs inside your own network. Setup is changing your client's base URL to get started, and then enrich with further attributions.
Feedback that would help most:
Where would this get in your way? A wrong block costs you more than a missed one, so tell me where the defaults feel heavy.
What would you need to see before you put production traffic through a gateway?
If you run agents: which tool or session controls are missing?
It's free to try, no credit card, and for launch day: sign up with Google or Github and get $20 in credits, 100 slots open today.
If you'd like a feature added in the product, I would love to hear it, pls do Hyper Ship new request.
The watch-before-block option is a useful way to introduce a new rule. Seeing the requests it would have stopped, with the reason for each, would make the decision to enforce it easier.
About Cloptima on Product Hunt
“AI Gateway, Guardrails & LLM FinOps”
Cloptima launched on Product Hunt on November 6th, 2026 and earned 59 upvotes and 4 comments, placing #48 on the daily leaderboard. Cloptima puts your own rules in front of every AI call: a virtual key per app with its own policy, guardrails that mask data before it leaves, tool policy for agents, budgets that block, session replay, an edge gateway inside your network, and prices each call on an attributed ledger before the provider sees a token. Setup is one line.
Cloptima was featured in Developer Tools (522.6k followers), Artificial Intelligence (483k followers) and Security (3k followers) on Product Hunt. Together, these topics include over 234.4k products, making this a competitive space to launch in.
Who hunted Cloptima?
Cloptima was hunted by rahul agarwal. 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 Cloptima stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
rahul agarwal
Hi Product Hunt 👋 I'm Rahul, Founder of Cloptima.
Why I built it: AI calls go straight from app code to a model provider, while the rules a company actually cares about (what it may spend, which data may leave, which tools an agent may use) live in a policy document, not in the request path. So teams either slow down to review everything by hand, or ship and find out later. I wanted those rules to run on every call, before it leaves, without asking developers to rewrite anything.
What's in it today: a key per app, guardrails that mask data before it leaves (and can watch first before they block), tool policy for agents, budgets that block at the line, session replay, and an edge gateway that runs inside your own network. Setup is changing your client's base URL to get started, and then enrich with further attributions.
Feedback that would help most:
Where would this get in your way? A wrong block costs you more than a missed one, so tell me where the defaults feel heavy.
What would you need to see before you put production traffic through a gateway?
If you run agents: which tool or session controls are missing?
It's free to try, no credit card, and for launch day: sign up with Google or Github and get $20 in credits, 100 slots open today.
If you'd like a feature added in the product, I would love to hear it, pls do Hyper Ship new request.