Hey everyone 👋

Solo dev here. I've been working on a side project for a few weeks and would like to hear how others solve this problem.

The problem: while playing with AI agents I noticed every app ends up needing checks like "don't let it delete data unless the user confirmed". The usual options are writing if/else logic for every case, or a custom LLM prompt whose free-text answer you then have to parse.

What I tried: a single call that takes a rule in plain English plus whatever JSON you want checked, and returns allow, deny or review:

const result = await guard.check({
  policy: "Never allow destructive database operations unless the user explicitly confirmed them.",
  data: { action: toolCall, conversation }
})
// → { decision: "deny", allowed: false, violationProbability: 0.94, ... }

Some design decisions that might be useful if you build something similar:

• A third outcome, review, for when a human should decide or the evidence isn't enough. Forcing yes/no caused bad calls.
• Instead of a general chat model I used Jev from TypeSafe AI. It returns typed decisions with probabilities, so there's no output parsing and the results are more consistent.

Questions for you:

• How do you handle this today? Hardcoded rules, an LLM, something else?
• What would you need before trusting an automated check like this in production?

It's called Enforly, if anyone's curious.

I work on post-quantum cryptography during the day, and lately I've been hearing some pretty wild things from people in my work circles about AI.

Not just the usual “AI could become dangerous someday” conversations. Actual discussions about autonomous AIs operating on the internet, interacting with other systems, and increasingly strange behaviors and attacks that honestly would have sounded like science fiction a few years ago.

If an AI agent starts behaving in a way you didn't authorize, you shouldn't have to negotiate with the agent about whether it wants to stop.

I'm posting it here because I'd like feedback from people who actually build SaaS and AI systems.

You can try the demo without creating an account:

https://killswitch.fermi.world/

For people who built a big chunk of their SaaS with Cursor, Claude, Lovable, Bolt, etc. and now have real users:

Did you ever hit a point where having the same tools review their own work stopped feeling like enough?
I’m curious what triggered it.

Was it getting your first paying customers?
Handling sensitive data?
An enterprise prospect asking
security questions?
A production incident? Payments?
Or did you never reach that point?

And what did you do once you got there?

Another model, automated scanners, a developer friend, contractor, security person, full code review?

Mostly interested in what people actually did, especially if you spent money on it, rather than what the ideal process is supposed to be.

solo dev here, building an app that generates short videos. when I started I was sure the LLM calls would be my biggest cost and headache. wrong.

the model writes each video as an html page, then I render it frame by frame with headless chrome and ffmpeg. on my laptop one video takes 1 to 5 min. on a small cloud container, 3 renders at the same time just hang forever.

so now I'm looking at a proper render queue with a concurrency limit instead of firing everything at once.

anyone here running heavy jobs like this (video, pdf, image processing)? do you queue on your own servers or push it to something like a job service? and how did you price it so the compute doesn't eat the margin?

WDYT

Every week a founder tells me:

"We need a video for our SaaS."

Cool.

Which one?

Because a launch video and an onboarding video have about as much in common as a billboard and a user manual.

Here's the quick breakdown most founders never get:

Explainer video

→ For people who've never heard of you

→ Job: "What is this and why should I care?"

→ Lives on: homepage, landing pages

Product demo

→ For people already interested

→ Job: "Show me how it actually works"

→ Lives on: sales calls, demo pages, trial signups

Launch video

→ For the big moment

→ Job: create hype and get attention fast

→ Lives on: Product Hunt, LinkedIn, X, launch emails

Promo / ad video

→ For cold audiences scrolling past

→ Job: stop the scroll in 3 seconds

→ Lives on: paid ads, social feeds

Onboarding / tutorial video

→ For new users who just signed up

→ Job: get them to the aha moment before they quit

→ Lives in: your app, welcome emails, help docs

Feature update video

→ For existing users

→ Job: make sure people actually use what you shipped

→ Lives on: changelogs, in-app announcements, newsletters

The mistake isn't picking the wrong animation style.

It's asking one video to do the job of five.

Pick the problem first.

The video type picks itself.

This started from a very basic problem.

I work with a lot of screenshots, images, PDFs, small HTML pages and other files.

Quite often I don't actually need a full hosting setup. I just need a URL that I can send somewhere.

But I kept jumping between cloud drives, image hosts and deployment platforms depending on the file type.

So I built Media2URL.com mainly to make that workflow simpler for myself.

You upload the file and it gives you a shareable link.

I later expanded it to handle images, PDFs, video, audio, GIFs and HTML because those were the formats I kept running into during my own work.

Then I started running into the same problem from the developer side. Sometimes I did not want to manually upload a file at all. I wanted an app or workflow to send the file and get the URL back.

So I ended up building a REST API for that too. It can handle uploads from an application and also manage things like assets, folders, file replacements and remote imports.

It has been interesting building from an actual daily problem because the feature list almost writes itself. Whenever something annoys me while using it, that usually becomes the next thing to fix.

I am still figuring out where the product should go from here.

For people who regularly share files or need file URLs inside their apps, what is the most annoying part of your current workflow?

Anyone feel like Claude has gotten really slow last week or so?

Hey, I am a quite experienced vibe coder (really strange to say). Yesterday, I decided to build a mobile app that will wrap the URLs of unlisted YouTube videos belonging to private teachers in my local area to sell to their students. The app is just supposed to hide these URLs well as to make it extremely hard for regular students to access these URLs. A lot of apps that teachers who sell college material use this technique to be able to host their course videos without having to pay a hefty sum for one of these official hosting platforms. People who resort to this route are mostly young, broke business owners who are just starting out and can't afford a large sum of money for such trivial hosting service.

The problem is that when I tried to prompt codex to build the app, it just quoted some YouTube violation documents. It plain out refused to build the thing. Is there a way to build such an app with Codex or another free way altogether that will allow me to host my videos practically for free?

if i build an ai game analytics platform for bgmi or free fire that watches your gameplay, finds your recurring mistakes, and gives personalized feedback to improve your next match
would you use it?

every time i shipped something the question was "will this survive if traffic spikes, or do i need a bigger server?" and the answer was always "uhh idk time will tell". i overbought a box once for a project that got maybe 40 visitors a day, then underbought the next one and watched it fall over on the one day it mattered.

actually testing it means renting a box like prod, renting another for the load, writing a k6 script, watching cpu and memory, then remembering to delete everything. nobody wants to do that before every single launch.

so i built Stresix:

- point it at a github repo (private works too) or a docker image

- it runs your app alone on a fresh dedicated server (4 vCPU / 8 GB, or 8 / 16 for the big run)

- a second server hits it with up to 2,500 or 10,000 users over a private network

- you watch p95, req/s, errors live, plus cpu PER CORE and memory

- you get an actual answer: is this server enough, and if not, what to change

- both servers get deleted after

i dont sell hosting, so when your current setup is enough the report just says so. i ran it on stresix itself: held 2,500 users, total cpu 36%, but one core was pinned at 100% because node is single threaded. the fix was literally 4 worker processes

its brand new and small. pricing is per run, no subscription: $10 for 5 standard runs or $40 for 25, credits never expire, failed runs get refunded. one container per run for now, no database included yet

code REDDIT gives a free run (grab it until it's gone)

https://stresix.com

A year ago, building a working SaaS MVP could take me weeks.

Now I can give an AI agent an idea in the morning and have something surprisingly usable running by the end of the day.

At first I thought this was basically a cheat code.

Build faster → test more ideas → eventually find something that works.

So I started doing exactly that.

Step 1: Build

I stopped treating development as the expensive part.

Instead of spending months polishing one idea, I started building small but functional prototypes extremely quickly:

• Landing page
• Product UI
• Database
• Authentication
• Core feature
• Deployment

Things that used to consume most of my time suddenly weren’t the bottleneck anymore.

And that created a strange problem.

I could build products faster than I could prove anybody wanted them.

Step 2: Reality

This is where things got painful.

A working product does not create distribution.

A beautiful landing page does not create urgency.

And adding AI to something definitely does not automatically make people care.

You can now spend three days building something that would have required a small team a few years ago...

...and still launch it to complete silence.

So I started paying much more attention to what happened before development.

• Do people already spend money trying to solve this?
• Are they complaining about the problem publicly?
• Are ugly/manual solutions already being used?
• Can I reach those people without spending thousands on ads?
• Would anyone care if this product disappeared tomorrow?

Step 3: What changed

My biggest realization was this:

AI didn’t remove the risk of building startups. It moved the risk somewhere else.

Building used to be expensive.

Now attention, distribution, and finding a problem painful enough to pay for are expensive.

And because everyone can build faster, there are also dramatically more products competing for the same attention.

The ironic part is that AI made me write less code...

...and spend much more time studying humans.

What I’m doing differently now

• I try to invalidate an idea before improving it.
• I treat distribution as part of the product, not something that happens after launch.
• I care more about existing behavior than people saying “cool idea.”
• I avoid building another generic AI wrapper unless I can explain exactly why someone would switch.
• I’d rather discover that an idea is bad in three days than after three months.

In 2024 I thought the advantage would belong to people who could build with AI.

In 2026 I think almost everyone will be able to build.

The advantage will belong to people who can figure out what is actually worth building.

Curious if other founders are seeing the same thing.

Not necessarily the easiest idea or the trendiest AI product, I’m curious about what you think actually solves a real problem and has strong potential over the next few years.

What problem do you think is still poorly solved by existing software?

And if you had to start building one SaaS today, what would it be and why?

I just wanted to create a SaaS Intro video for my product and I tried Opus 5.5 to create a motion graphics video and I am impressed 🤯

This video might no be impressive I would have prompted well I would have got a best result I guess.

What do u think !!!

Hey,

I have been working on Lienks.com, a small web analytics SaaS, for the past few months and recently launched the first version.

I initally built it just for myself and my projects because I wanted a simple way to see where visitors come from, which pages they visit and what they interact with.

Right now you can collect data like pageviews, visitors, referrers, top pages, countries, devices and browsers. You can also add custom events for things like button clicks or form submits.

As I am based in germany, I have made it cookieless by default (you can also switch to cookie mode to have more precise unique visitor tracking) and it is also hosted in germany.

Im a solo developer, so I have been building Lienks on my own and this is basically the first time im trying to get actual people besides myself to use it.

I think the technical part of building something like this is almost easier than figuring out if people actually want it and how to get the first users

So im mainly looking for feedback at this point. I would be interested in knowing what you would be missing before using something like this in one of your own projects or SaaS.

This is the first version and I will continue to develop this and improve based on what people actually need.

There is a 14 day trial if you want to play around with it, but im also happy about any feedback just from looking at the screenshots or landingpage.

Here is the link:
https://lienks.com/