Hey HN,
First time building SaaS. Don't be too harsh, but I would appreciate your feedback. I have a strong technical background, but never had an opportunity to design as much as a landing page or think about product positioning. If you see something that's an obvious gap, please take a second to leave a comment.
Now, the product:
I use MCPs. I've worked in teams that use MCPs. Regardless of whether you are 1 or many, these are the issues that you will run into:
* random API keys in .env files * OAuth credentials that expire * no visibility of which MCPs are used * no controls over what data is being sent to MCPs
There are also nice-to-haves that you wish you've had:
* hosting/sharing private MCP tools * fixing context bloat
MCP gateways are designed to solve these problems. However, in my experience, they are expensive and hard to use. Everything that I've tried felt like it was designed by someone who can conceptualize the problem, but hasn't experienced it. Whereas I have seen it working for a big team and also trying to setup my own development environment. And that's Rayrun – an MCP gateway that solves hosting, data governance, secrets, OAuth rotation, and gives visibility across your organization. It's designed to be useful whether you are solo or a 500 people team.
I would truly appreciate you giving it a try and ask any questions or share observations.
If you are curious about feature parity with the existing MCP gateways, I've made a comparison matrix [https://ray.run/compare](https://ray.run/compare)
Comments URL: [https://news.ycombinator.com/item?id=49636609](https://news.ycombinator.com/item?id=49636609)
Points: 2