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

Comments URL: https://news.ycombinator.com/item?id=49636609

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=41811299

Points: 4

# Comments: 0

I thought that if I build a collection of the most polished tools that are pleasant to use, over time Google will start recommending them to more and more people. My goal was to invest upfront into developing domain reputation, so that when I launch my SaaS in the future, I am not starting from 0.

At first, it looked like this strategy is working. The first month I got roughly 1k unique visitors. Then it quickly grew to 4k uniques, and maxed out at 5k uniques after 5 months. But then (2023 November) some Google update launched and it was a downhill ride since. It wasn't all at once, but it slowly dwindled to about 800 uniques per month and seems to be stable at around that number. What's worse is that most users are direct users, i.e. coming from bookmarks. Increasingly, Google started to deprioritize results even for things that Rayrun was ranking #1.

I don't know what this means for long-term SEO strategy, but it was pretty devastating learning for me. I am not focused on building the product and don't invest much back into SEO play, but wanted to share this as a cautionary learning with others.

Comments URL: https://news.ycombinator.com/item?id=40018496

Points: 8

# Comments: 8

I am building something that would probably benefit from this, but with that price tag (solo indy dev) that's going to be a big ask! might be worth it, just no way of knowing without trying it first

https://www.reddit.com/r/programming/comments/17tccsc/comment/k8w5o26/?utm_source=share&utm_medium=web2x&context=3

I shrugged it off the first time it popped up, because in my eyes the person making the comment is more sour that I am impeding their ability to monetize the concept by making it open-source than they actually believe that I cloned their work.

However, the same user then started spamming my project users with their messages about this project being a clone of theirs without proper attribution and going as far as to double down by posting a new thread on /r/programming once again stating that it is a clone.

https://www.reddit.com/r/programming/comments/17w3toy/comment/k9etf1x/?utm_source=reddit&utm_medium=web2x&context=3

I saw this thread a few hours late, so by the time I got to respond everyone already had their pitchforks out. Bursting out a few responses in panic probably didn't help either.

Anyway, that's the context. The projects in question are https://github.com/zerostep-ai/zerostep and https://github.com/lucgagan/auto-playwright. I added a section to the documentation using every concrete piece of evidence I could think of to prove that these projects are as distinct as they possibly can be given the narrow scope of the problem and possible ways to implement it (https://github.com/lucgagan/auto-playwright#addressing-controversy).

I also think that, in retrospect, it would have been nice of me to acknowledge that their project was a source of inspiration for Auto Playwright. However, at no point did I copy their project, so the thought of LICENSE attribution did not even cross my mind.

I am trying to be cool head about this and think of what is the proper response. More importantly, I am trying to get a perspective from folks outside of the original debate to see if I am wrong with my actions.

Is copying parts of README enough to call for attribution to the original project?

Is copying error message enough to call for attribution of the original project?

Where is the line?

I still think this whole think exploded because I effectively released something that provides comparable functionality to a commercial solution that they are working and thats what spurred this debacle. However, I also acknowledge that I am struggling to reconcile dozens of people calling me "** code thief" in private messages and my sense of righteousness, which is why I would appreciate the insights.

Comments URL: https://news.ycombinator.com/item?id=38284100

Points: 1

# Comments: 4

I'm excited to introduce Auto Playwright, an open-source tool that revolutionizes web testing by integrating AI with Playwright. Imagine writing your web app tests in plain, simple English and having AI turn those instructions into automated tests!

Key Features: - AI-Driven Test Writing: Just write what you need in plain text, and let the AI do the rest. - Playwright Compatibility: Works with all browsers compatible with Playwright. - Open-Source: Dive into the code, contribute, and customize as you see fit.

How It Works: 1. Install `auto-playwright` via npm. 2. Set up your OpenAI API key. 3. Write tests using intuitive, plain-text prompts.

Examples: From testing a search function with a few lines of text to automating complex e-commerce cart tests – it's all made incredibly simple.

    test("auto Playwright example", async ({ page }) => {
      await page.goto("/");

      // `auto` can query data
      // In this case, the result is plain-text contents of the header
      const headerText = await auto("get the header text", { page, test });

      // `auto` can perform actions
      // In this case, auto will find and fill in the search text input
      await auto(`Type "${headerText}" in the search box`, { page, test });

      // `auto` can assert the state of the website
      // In this case, the result is a boolean outcome
      const searchInputHasHeaderText = await auto(`Is the contents of the search box equal to "${headerText}"?` { page, test });

      expect(searchInputHasHeaderText).toBe(true);
    });

Get Involved: I am building a community around Auto Playwright. Join us on Discord (https://ray.run/discord), contribute to the GitHub repo (https://github.com/lucgagan/auto-playwright), and stay updated with our newsletter (https://ray.run/newsletter).

Looking forward to your thoughts, feedback, and seeing how you use Auto Playwright in your projects!

Check out Auto Playwright on GitHub:

https://github.com/lucgagan/auto-playwright

https://en.wikipedia.org/wiki/Playwright_(software)

Thanks!

https://en.wikipedia.org/wiki/Draft:Playwright_(software)

It is highly demotivating to try to write a quality article for Wikipedia because someone can just reject your days of work in seconds and then leave it in draft forever.

By the looks of it, I am taking a slightly different approach than you. I am using LLM only to identify elements, but the actual generators are created using https://ray.run/browser-extension