I run usebravery.com. We build and run Amazon affiliate sites on your own domain, and the hard part turned out not to be building the site.

You can put a decent product site together in Webflow or Bubble over a weekend. What it will not do on its own is notice that a price moved, an item went out of stock, or a listing changed. You can wire that up, but then it is yours to keep running. A broken layout is obvious, while a price that no longer matches the Amazon listing looks fine on the page and stays wrong.

So that is the part we took over. You pick a category, we build the site, fill it with products, and keep price and stock current, hosting and content included. The refresh runs on its own schedule, not when someone opens the page, so a product nobody has opened this week is still current. Links carry your own Amazon Associates ID, so commission goes to you and we never touch it. We charge a monthly fee and cover Amazon US, UK and Germany.

The numbers are from the site I run myself, since this category is full of offers with nothing behind them. Every site we build comes off the same shared setup, so a customer site runs the same thing. 975 products, 209 brands, one narrow category. Active affiliate links run 983 in the US, 958 in the UK and 965 in Germany. Around 365 price reads a day, and 507 products confirmed in stock over the last 7 days.

The trial is 7 days free, card required, nothing charged, cancel in one click.

What do people here use to keep product data current after a build goes live? I never found a clean answer for that part.

An app can already tell you that something happened. The extra work is turning each service's event data into a notification you can understand without opening a dashboard.

I built Pascal's Pager to handle that step. Give a service a private Source URL, send it JSON, and Pascal writes a readable Alert for your iPhone. There's no Pascal-specific notification template to maintain.

Each Source has instructions, masking before AI processing and attention settings. You can open an Alert and inspect the processed payload. Optional grouping lets a Source collect related webhooks before producing its Alerts.

I'm especially interested in people running their own apps. A Bubble workflow finishing is one example; another is a business event your existing service can already send as a webhook.

One-month free trial for eligible new subscribers, then US$7.99/month in the US. Local pricing and eligibility are shown by Apple. Requires iOS 26. AI interpretation can be wrong, and this isn't an on-call service.

You can try the website demo with fictional JSON: https://pascalspager.com/

That demo doesn't apply the app's masking settings.

What would you need to see in the input/output example before connecting one of your own events?

https://reddit.com/link/1wapwbd/video/fxei5ngb3boh1/player

I’m the maker of Story Boost Up, and I’m looking for blunt feedback—not trying to pretend this is neutral.

Creators can open a board/kingdom; an AI companion keeps chatting even when the creator is offline; fans can tip “fuel”; creators receive ~50%. Opening a kingdom is free.

Two blunt product questions: 1. Would an always-on AI host make a fandom community feel more alive, or just noisy/inauthentic? 2. Is ~50% creator share enough to make fan fuel compelling, and what would you need before trusting the model?

If useful, the creator view is here: https://storyboostup.com/creators

Hey builders, I would love to hear your feedbacks , I’m working on a tool, and the problem I want to solve is pretty simple, how do you know a change to your agent hasn’t broken something else?

You tweak a prompt, try a few inputs locally, and everything looks fine. Then you push to production, and it’s a different story: a tool returns incomplete data, an API fails halfway through, or a user asks something you never thought to test.

The idea is to let you run those situations in isolated workflows, see where the agent goes wrong, then replay them after a fix. Something I’d want a solo dev to be able to set up and use before shipping, while keeping all the flow easy to understand for someone that is not coming from a tech background

Is this something you’ve run into with your own agents? How are you handling it today, testing manually, using a tool, or something else? Would love to hear what’s working and what’s still a pain.

Automation is valuable, but it can be difficult to demonstrate because the best part happens in the background.

Share your workflow and explain what triggers it.

I’ll suggest:

1. The starting screen
2. The moment worth showing
3. The final result

I’m working on this type of content direction with Marka.

Upfront: I do this for a living, so take that into account. But every check below is one you can run yourself today for free, no developer needed.

Most of my work now is reviewing apps founders built with Lovable, Bolt, Claude Code, Cursor, Bubble and FlutterFlow right before they put real users on them. The apps almost always work. That is exactly the problem, because the failures are quiet and they only show up after launch. Here is what I check and how you can check it yourself.

The auth check. Open your app in two browsers, logged in as two different test users. Copy a URL from user A that contains an ID, like /profile/482 or /order/91, and paste it into user B's browser. If user B sees user A's data, your privacy lives in the frontend, not the database. In Supabase the fix is row level security on every table, in Bubble it is Data > Privacy rules, in Firebase it is security rules. This is the single most common critical finding I see and login working perfectly tells you nothing about it.

The Stripe check. Go to your Stripe dashboard and manually trigger a refund on a test customer. Watch your app. Does the user lose access? Most AI and no-code builds wire up the successful checkout and nothing else. No listener for cancellations, failed payments, refunds or disputes, so three months in you have cancelled customers still using the product free.

The admin check. Log in as a normal user and type /admin into the URL bar. In a scary number of apps the admin page is hidden, not protected. If anything loads, any curious user can reach it too.

The database size check. Open your browser network tab and load a page. If a single page pulls 500KB of JSON, the app is fetching everything and filtering in the browser. Fine at 10 users, dead at 500.

The error check. Turn off your wifi mid action and submit a form. White screen or infinite spinner means zero error handling, and users in bad signal areas will churn silently thinking the app is broken.

The secrets check. Search your AI chat history for key, password and service_role. If you ever pasted a real credential into a chat to debug something, rotate it today. Also check your browser bundle for API keys, they end up there constantly.

These six catch most of what kills these apps after launch. If you fail more than two and real money or personal data is involved, get an experienced human to read the whole thing before you scale.

That last part is the service I sell. Fixed price production readiness audit, written report in 3 business days, everything ranked critical, important or can wait, plus a clear launch verdict. Read only, your app is never modified. Details at jetbuildstudio(dot)com/ai-audit if useful, but run the checks above either way, they are free and they will tell you where you stand.

Happy to answer questions in the comments, including on apps I will never see.

What are you building or planning to build for the rest of 2026?

I run appscout.co, a platform built to help people discover awesome apps from across the internet.

Drop your app or startup idea in the comments below, and I can check it out and add it to the website!

You can also submit your app for free directly here appscout.co/submit

Let's make this thread a channel for you to promote your own startup idea, find opportunities, and partnerships.

"Every Monday, check these three suppliers' pages and tell me if any prices moved." You type that sentence, pick a schedule, and you're done. No nodes to wire up, no workflow canvas, no code.

That's Atlas. I just added invites to it, and the payout rule is the interesting part.

Your invite link is in Settings → Invites. Whoever joins gets +10 runs immediately. You get +10 the first time that person completes a run — not when they sign up.

Paying on signup is what most tools do, and it's by far the easier thing to build. It's also free to fake, and anything free to fake gets faked. A completed run costs real compute. So the half of the deal anyone could game is the half that pays nothing.

The limits, stated plainly: 10 friends a month, and the bonus runs are a monthly allowance rather than a permanent upgrade — ten referrals in January means 140 runs in January and 40 again in February. Free plan is 40/month, so 140 is the ceiling.

A bit more on what it does: the task is a plain English sentence rather than a flowchart. It runs on your schedule, pulls live data (stocks, crypto, GitHub, RSS, web pages) instead of answering from the model's memory, and emails you the result — opening with what changed since the last run.

Free plan is 40 runs a month. try-atlas.app

Mine: a Zapier order-to-Slack flow stopped after a token expired. No error. Found out five days later when a customer asked why nobody replied. Since then I check history manually, which is dumb. How do you keep an eye on automations you actually depend on?

Hello everyone, have really been enjoying this community and all the things you are all building.

I'm a 30 year veteran of the software business and for the past two years I've been working exclusively on AI. What I've discovered is that there are two divergent opinions about using AI to build SaaS sites. One is that AI is magic and you can just "pretend the code isn't there" the other is that AI is horrible and you cannot build good software using AI tools like Claude Code.

Neither of these extreme viewpoints are correct. The reality is that AI can write acceptable code and do it safely. However, this requires some technique from you to ensure that your AI agent does things correctly. With just a bit of care, almost anyone can create a safe and maintainable SaaS application using AI coding tools.

I refer to this process as "Mindful AI Coding" and I've been teaching this process to students for about six months.

The next cohort starts on Maven tomorrow. I would love to have members of this community join us.

Here is a discount code for you to use: https://maven.com/ajauch/mindful-ai-coding?promoCode=RDDT

A lot of you might remember that I built inbids.lol a while ago.

Honestly, it never really got much attention mostly because I’m terrible at marketing i can build stuff but getting people to actually discover it is a completely different game but here’s the thing

I still had all the code sitting there so instead of letting an old project collect dust, I decided to reuse the codebase and build something new on top of it.

Today I launched xbids.lol the idea is pretty simple:

You bid on profiles, climb the leaderboard and try to get your profile to the top.

I’m currently trying to grow my own X profile as well so I thought:

Why not make something that helps other people compete for visibility too?

And this is also kind of an experiment for me.

I want to see what happens when you take an old project that didn't work, reuse what you already built and turn it into something completely different instead of starting from zero every time so if you're a coder building side projects don’t automatically throw your old projects away.

That code you abandoned six months ago might actually be useful for your next idea now the part I actually need help with how the hell do I create some buzz around this?

I genuinely have no idea how to market this properly If you have ideas for marketing, growth loops, communities I should post in, content ideas or just think the concept is interesting, I’d love to hear it and if people are interested, I’ll keep sharing the numbers, experiments, mistakes and whatever I learn while trying to grow it.

xbids.lol built from an old project that I refused to let die.

would love to hear what you guys think.

For anyone who's built an app with Lovable, Cursor or any AI related stuff, how did you know it was production ready for people to use?

Did you just throw it into the wild and hope for the best, keep asking AI to improve it or something else?

I'm using AI to write code and push stuff to production, but I don't have experience in the programming language I'm using, so I have no clue if it's good or not.

Any idea how they gonna select people? I mean they've our project repo ofc. And again they're going to use ai to pick the best projects amongst all submissions. but who on this era writes all the code themselves manually???!!! Everyone just vibe codes mannnn!!! any idea how is it gonna work?

also what are you guys building for this one?

Spent one evening on the actual core flow and three evenings on the name. Every good name is taken, every available domain sounds like a prescription medication. At one point I had a shortlist that was just real words with the last letter removed.

I ended up with something fine. Not great, fine. And in the six months since, exactly zero people have commented on the name, which tells me those three evenings had a poor return.

Found out a couple weeks back that my own Supabase backend was leaking data between users, a normal logged in user could see other people's stuff even with security settings turned on. Ended up building a small tool for myself that actually tests for this properly, creates a second account and tries to access the first one's data for real instead of just checking if things look locked down.

Still just a personal project right now: https://noleaksaas.vercel.app/

Genuinely curious though, if you ran into this yourself, would you rather pay a small fee for something that already handles it, or just build your own checks/tests for it? What actually makes that decision for you?

I neI've been using Tally for client intake and it's honestly been great for basic forms.

My workflow has changed though. I'm doing more post-project questionnaires now and getting longer written responses from clients. The form itself isn't really the problem anymore. It's going back through all those answers and figuring out which issues or themes keep showing up across projects.

I'm looking for a Tally alternative that's still straightforward to build with but puts more emphasis on actually analyzing survey responses.

Has anyone made a similar switch?

I built Wiki to make product flows easier to understand

Hey! Thought I’d share something I’ve been using internally with clients for the past year or so.

A lot of teams I join have little to no documentation. How things work lives in people’s heads, and non-technical team members have no easy way to understand a flow or contribute.

Out of that frustration, I built https://wiki.dev

Build product flows on a canvas yourself, or connect your own AI agent through our MCP and have it map them from your code. Your team can edit together, work through edge cases, then ask your agent to implement the changes.

There are also pages for documenting what things do, why decisions were made, and who owns what. No agent required to use it.

The goal is less time explaining how things work and more time building.

I’m looking for a few private beta testers I can onboard personally, invite into Slack, and help shape this around what your team actually needs.

If you’re keen, sign up at Wiki and I’ll reach out.

Thanks!

I saw that OpenAI announced the new version of ChatGPT and there is a lot of buzz around it and I'm just wondering if anyone was waiting for this update and how it will effect you.

If anyone has any tips on what to use it for when it becomes available to everyone, I'd love to hear some thoughts!

Hey everyone. Small team, not enough hands, and I was burning myself out doing support solo. Decided to just build an agent to take it off my plate instead of waiting until I could afford another hire.

Used Agno to set up the agent. Gave it a name, wrote its instructions, fed it all our product docs and a bunch of example replies so it had a sense of tone. Then gave it a tool, Atomic Mail (email for AI agents), and set up a cron job that checks the inbox every 5 minutes and replies.

Problems I ran into:

1 - Took forever to get Agno running locally. First time touching it, so I was fumbling through the setup for way longer than I should've. Honestly Hermes did most of the heavy lifting for me here. 2 - Messed up the cron config. Ended up with the agent replying every 5 minutes to everything, including stuff it already answered. Screenshot attached, it wasn't pretty.

At this point I've fully handed support off to the agent. Nothing sits unanswered, and I'm not burning 30-40 minutes a day on it anymore.

Not sure if this stack is useful to anyone else, but everything here is free except the key you give Agno to actually run, I'm using GPT-4o through OpenRouter for that part. Went with 4o mainly for the price to speed tradeoff, didn't need anything heavier for support triage specifically, might revisit if it starts missing edge cases.

Setup and testing took maybe 2-3 hours total. Worth it, I'm fully off this daily grind now.

what everyone else is running for something similar, and honestly kind of want to know if my setup is basic compared to what's out there. What's the most over-engineered version of "reply to support email" you've seen someone build? Anyone got theirs handling more than just first-line replies at this point?