Saasufy mentions (26)

• GitHub is the wrong shape for this new world

  This is a good article. I've been working on such infrastructure to facilitate safe vibe coding with a focus on simple access control and analytics. https://saasufy.com/ I think this is spot on but the new abstractions are yet to be popularized but I'm seeing some clear patterns arise. This is something I spend a lot of time thinking about because the new abstractions must fit within existing paradigms to provide... - Source: Hacker News / 4 days ago

• Cloudflare Drop

  This is neat. I've been dreaming of something like this to host frontends connected to my backend platform https://saasufy.com - Because it's built with WebSockets, it doesn't have CORS limitations so I can literally make Claude Code create an index.html file on my computer's file system, then open it directly from the file system by double-clicking it (served via file:// protocol) then, when I'm happy, I can grab... - Source: Hacker News / 25 days ago

• Better Models: Worse Tools

  When building agent integration for my serverless backend https://saasufy.com/, I decided to use skill markdown files curl commands inside instead of building out MCP tools. The curl command is just so popular, models are really good at using it. Also I like that curl is for bash and my platform requires JSON payloads; it makes the separation clear to the agent. I find it to be very reliable. - Source: Hacker News / 29 days ago

• Show HN: Write SaaS apps where users control where their data is stored

  I've been working on a similar product. Started working on it 14 years ago and pivoted it to vibe coding. https://saasufy.com/ I'm thinking to open source it but I want to see some traction before doing that since I don't want to open source then someone else takes my code and I get nothing out of it. - Source: Hacker News / about 1 month ago

• AI demands more engineering discipline. Not less

  This is why I built https://saasufy.com/ - Vibe coders shouldn't trust themselves with backend security. Unfortunately, it's extremely difficult to get right. There's a lot to think about; - Schema validation with appropriate size limits on all possible fields. - Authentication. - Access control. - Backpressure management. - Ensuring that the actions of one user doesn't throttle another user, e.g. Using async... - Source: Hacker News / about 2 months ago

CodeBlinks mentions (0)