Launching today
MonoCloud for Startups
One identity layer for your customers, APIs, and agents
232 followers
One identity layer for your customers, APIs, and agents
232 followers
MonoCloud is one identity layer for your customers, your APIs, and your agents. Most tools stop at a login box. We go past login into authorization and accountability: decide exactly what every user, service, and AI agent can access, prove what it did, and revoke it in an instant. Fine-grained Cedar authorization, passkeys and SSO, API protection, M2M, and mTLS with certificate-bound trust, all on one platform. Startups get the full platform free for one year.
honestly the one free year for startups is kind of a big deal, but what really stands out is the mTLS with certificate-bound trust. most platforms treat that as an enterprise add-on and bury it in pricing. shipping it on day one for early teams shows you actually thought about the security stack instead of bolting it on later.
@kervangamz80440 Thanks, that was a deliberate choice. Certificate-bound tokens make a stolen token useless without the key, and that shouldn't be something you only get once you're big enough for an enterprise tier. The free year for startups includes it, so early teams can build on cert-bound trust from the start instead of retrofitting it later.
How does pricing work after year one? Curious if startups that grow during the free period end up sticking or if the jump to paid feels steep.
Vishal — the step-up-before-high-risk-action line caught me. If an AI agent, not a human at a keyboard, is the one about to trigger something like a payment or a live bid submission, can step-up auth even work — or does that whole model assume there's a human around to re-verify?
@medal411 Sharp catch. Classic step-up does assume a human is there to re-verify, so re-prompting a fully autonomous agent for a passkey doesn't make sense. Two things cover the agent case instead. When a human should sign off, you use human-in-the-loop consent, pausing the agent before the sensitive action and requiring a fresh approval. When it's genuinely autonomous with no human, you don't step up at all, you gate the action with policy, a Cedar rule that decides whether that agent, with that scope, is even allowed to trigger the payment, rather than re-verifying someone who isn't there.
MonoCloud for Startups
Hey Product Hunt! 👋 Riya here. I do product marketing at MonoCloud, and I am one of the makers.
Most of my week is spent talking to founders about auth, and I keep seeing the same arc. In the beginning nobody wants to think about it, so they drop in a login box, ship, and move on.
Six months later, those same people are drowning in it.
A customer wants SSO.
A security review shows up with forty questions.
Their services need to talk to each other safely. And their AI agents are now acting on behalf of users with no real control over what they can reach.
The reason it keeps happening is that most identity tools were built for one slice of the problem.
The easy ones stop at the login screen.
The enterprise ones are powerful but slow and expensive to adopt. So teams end up owning the hard middle themselves, which is the exact part they have no time to build.
MonoCloud covers all of it on one platform, your customers, your APIs, and your agents, from your first user to enterprise scale. Not just who signs in, but what every user, service, and agent is allowed to do afterwards, with the ability to prove it and pull it back in an instant.
All of it is live today, not a demo or a waitlist. Ten design partners across SaaS and AI companies are already building on it.
👉 If you are a startup, you get the full platform free for a year, every feature, no gates. Apply here: MonoCloud for Startups - Free for One Year 👈
And if identity is central to what you are building and you want to shape where this goes, we are opening a few more design partner spots. Leave a comment or reach me on LinkedIn (link in profile).
I will be here all day and would genuinely love to know how you are handling identity for your AI agents right now, and where it falls apart first. That is the conversation I care about most.
This is the unglamorous part that makes agent work production-safe. Small teams often start with one all-powerful service key because it ships fastest, then the second or third automated process turns that shortcut into real operational risk. Per-agent identity plus fast revocation is the boring layer that lets you delegate without pretending the risk disappeared.
@krekeltronics Exactly this. The one all-powerful key is where almost everyone starts because it ships fastest, and it stays invisible right up until the second automated process has to share it. Scoped identity per agent plus revocation you can actually trigger is what makes delegating feel safe instead of just hoping. Well put.
the one year free offer for startups is honestly such a smart move, basically lets you build the whole stack without cobbling together five different auth tools.
EverTutor AI
Congrats on the launch identity is one of those problems that only looks simple until you have to build it yourself Really Building authentication and identity is never as straightforward as it seems Excited to see products taking a fresh approach here Congratulations to the team and hope you have a fantastic launch
MonoCloud for Startups
@suryansh_tiwari2 thank you so much. it always looks like a solved problem until you're actually in it 😄 really appreciate the support!