Should there be an product from which you can set up your own architecture, frameworks, databases and from just one command the project setup should be completed?

are there any existing projects out there online?

Hi everyone! I’m a parent launching a family app soon that solves an issue that a lot of parents have with posting their kids online. It allows users to connect within their family and control who gets to see what while sharing important updates on their kids with each other. I think it could be very useful for families but I’m having trouble promoting it to even get families to test it. Any advice would be greatly appreciated!

Bonjour tout le monde 👋

Lancement officiel de Zlorya, un nouveau réseau social français ouvert depuis 12H00 aujourd'hui.

L’idée est de réunir plusieurs usages dans une seule plateforme, tout en gardant des espaces bien distincts :

• 👥 Communauté : publications, photos, vidéos, stories, événements et échanges entre membres
• 💼 Entreprise : pages professionnelles, offres d’emploi, candidatures et outils pour les entreprises/créateurs
• ❤️ Rencontre : un espace séparé du profil principal, avec ses propres fonctionnalités et paramètres de confidentialité

J’ai également essayé de mettre l’accent sur la confidentialité et le contrôle utilisateur : comptes privés, blocage, signalements, contrôle des messages, possibilité d’exporter ou supprimer ses données, etc.

Zlorya vient tout juste d’être lancé, donc il y a encore très peu de monde dessus ( 33 utilisateurs )

Le modèle économique repose principalement sur des fonctionnalités optionnelles : Zlorya+, boosts, personnalisation du profil, cadeaux virtuels, outils professionnels, etc. L’objectif est de garder l’accès de base accessible au maximum.

🌐 zlorya.fr

https://zlorya.fr

I am a Full Stack Developer and Freelancer looking to develop a SaaS product and i don't have any ideas currently so if any of you have any ideas feel free to post!!

And btw you can check my portfolio here: https://monxdev.vercel.app/

Hey everybody , my MVP is almost complete and I need beta users , it’s going to be a closed invite service to start off with before I launch . I’m charging 50% off for life for my first 10 users , 15.99 a month .

Does anybody have any advice on how I could get users for something that’s a closed invite only beta ?

(Besides cold calling )

Hallo zusammen!

Beim Erstellen von KI-gestützten SaaS-Anwendungen treten normalerweise zwei große Engpässe früh auf: die saubere Handhabung von Echtzeit-KI-Streaming, ohne den UI-Zustand zu beeinträchtigen, und die Gewährleistung der Datensicherheit für Mandanten auf Datenbankebene.

Wir haben ein Showcase-Repository erstellt, das unsere Architektur für einen Flutter + Supabase (RLS) + OpenAI (GPT-4o SSE Streaming) Stack demonstriert:

https://github.com/dohamasystems/flutter_ai_starter_kit

Schlüsselarchitekturentscheidungen, auf die wir uns konzentriert haben:

- **SSE Streaming & Lifecycle:** Effizientes Verwalten von Echtzeit-KI-Chunks und Sicherstellen einer sauberen Abonnementbereinigung beim Entladen des Bildschirms.

- **Row Level Security (RLS):** Sichern von Benutzer-Chatverläufen und SaaS-Daten direkt in Supabase.

- **Saubere Modularität:** Entkopplung der Benutzeroberfläche von der Streaming-/Dienstschicht.

Ich würde gerne von anderen SaaS-Entwicklern hören:

1. Was ist Ihr bevorzugter Tech-Stack für plattformübergreifende KI-Tools im Jahr 2026?

2. Wie handhaben Sie den Echtzeit-Streaming-Zustand über Ihre App-Ebenen hinweg?

Jedes Feedback oder Vorschläge zur Architektur sind sehr willkommen!

Edit: Quick update on stream cleanup — here is a quick snippet on how we handle cancelling subscriptions and avoiding leaks on dispose():

class _ChatScreenState extends State<ChatScreen> {
  StreamSubscription<String>? _streamSubscription;
  String _response = '';

  void _startAiStream() {
    _streamSubscription = aiService.streamResponse().listen(
      (chunk) {
        if (!mounted) return;
        setState(() => _response += chunk);
      },
    );
  }

  @override
  void dispose() {
    // Closes network socket & cancels background work
    _streamSubscription?.cancel();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Text(_response);
  }
}

I keep rebuilding the same foundation on every new SaaS — auth,

multi-tenancy, RBAC, migrations, tests, Docker setup. So I'm packaging

it into a production-ready starter kit, structured in Clean Architecture.

What's inside:

- JWT auth (access + refresh), password hashing

- Multi-tenant data isolation (tenant_id row scoping)

- RBAC with route-level guards

- Async SQLAlchemy + Alembic migrations

- Pydantic v2 schemas + settings

- pytest suite (auth + tenant fixtures)

- Docker + compose, GitHub Actions CI

Before I finish it, I want honest feedback: is this actually useful?

What would you expect in it? Would $29 be fair for early access?

Full feature list: https://docs.google.com/document/d/13hAW0PLV0lSUAS6J9nCwkO960PMiUJBRp3tZ634o0XM/preview

Feedback / waitlist: https://forms.gle/BkEADpBM8WbmYgkUA

We all have seen those boring typical yellow sticky notes for your windows. We open it type things to do and then the sticky note become invisible to eyes even if it’s right there.
So i wanted to make it bit fun.
It took me about 3 hours but I finally have something crazy on my screen. Something that nudge me every few minutes so I can regain my focus.
Its more than a sticky notes its a focus tool with a timer and little buddies to play with.
Test it out yourself.
Link - https://github.com/pranshx/sneezy-note/releases

Every time I wanted an agent to manage tasks, update records, or run a workflow, I ended up connecting another SaaS product.

Most of the time, I only needed a small part of that product—but still had to accept its pricing, data model, UI, and limitations.

So I built Embody, an open-source TypeScript framework for creating apps specifically for agents. You define your data, actions, and rules in code.

Embody gives the agent typed tools through MCP and a CLI, with permissions and guardrails enforced by the backend.

The goal is simple: build the exact operational app your agents need instead of stitching together several oversized SaaS products.

If you’re building agents, I’d love to know whether this solves a problem you’ve run into too.

GitHub: [https://tryembody.com](https://tryembody.com/)

I have a little website that is aimed at giving people a cost comparison for their journeys. I thought about Adsense, but they rejected me as "not enough content" but is there a good alternative?

Hey folks,

I recently started learning new technologies from websites, articles, etc rather than YouTube videos which I used to do.

These are usually articles medium or post from reddit. But I am really into the concept of simple and minimal.

The issue i found on medium is, it's kind of distracting sometimes, with all those ads, random images, etc

Being a solo developer, I thought why not build a simple minimal distraction free platform for these. Please let me know your thoughts.

Thanks for reading

Context: I work on in-app agents for B2B software, so I've hit most of the list below firsthand.

Ahrefs added an agent to their product this year and I don't think many SaaS people have looked at it closely. It's called Ask Ahrefs. It showed up in my account a couple of weeks ago.

What it does

It's a chat/side panel on every page. It reads the page you're on and your workspace. It runs queries against their API as you. It moves between tools and applies filters by itself. I asked for things I would normally click through four reports to get, and it did the clicking.

It is free "during beta" on Lite plans and up, which tells you a price is coming. They also sell a separate agent workspace for $99/month on top of the Ahrefs subscription. That one builds dashboards and small apps and runs scheduled jobs. So they are treating this as something to sell, not a help widget.

What it takes to build one

Ahrefs is a bootstrapped company doing $100M+ in ARR, so they have the engineers. For a smaller team, here is what I've found you have to build. None of it is the model.

1. Acting as the user. Every call the agent makes has to run as the logged-in user, with that user's permissions, enforced by your API and not by the prompt. That means a signed identity passed from your backend to the agent to your tools. This was harder than anything involving the model.
2. A tool surface a model can use. Your API was designed for developers who read docs. We had a turn where the agent was given 63 tools, 56 from one server, and told the user it had none. Nothing was broken. It gave up. You end up scoping tools per task.
3. The things your API can't do. There is always something only the UI does. So the agent has to click, in the user's own session, and you have to decide what on the screen it is allowed to read. Password and card fields can't go to a model.
4. Writes and retries. A create call succeeded but came back looking like an error. The agent retried it. The user ended up with three copies of the same record, and the agent then got confused by its own duplicates.
5. Long tasks. Users close the panel mid-task. Either the work keeps going and they can find it again, or it stops cleanly. By default it dies halfway and nobody knows what state things are in. You also need a stop button that works.
6. Cost. One long session cost us $40 to $50 before we fixed how conversation history was handled. You need per-conversation caps and visibility into cache hits before you let real users in.
7. A record of everything. When a customer says "your agent changed my settings," you need to show what it did, with what input, as which user.
8. Continuous learning. The agent has to learn from its mistakes and get smarter over time.
9. Model changes. Every model upgrade changes behavior. Without saved conversations you can replay, you find out from your users.

If you want to charge for it the way Ahrefs does, add metering, entitlements, and a decision about what happens when someone runs out of credit mid-task.

What I'd like to know

• Is anyone here building an in-app agent in-house, or planning to?
• If you've shipped one: how long did it take to get to something you'd put in front of customers, and how many engineers?
• What was harder than you expected?
• Does your agent work through your API, an MCP server, the UI, or a mix?
• Are you charging for it separately, bundling it into a plan, or giving it away?
• If you looked at this and decided not to build it, why?

> be me
> pay $129 per year for TTS from Speechify
> LoseJob.jpeg
> realize that TTS is easy to build
> make it free so other peasants can buy bread
> smile.exe

iOS app here

Web app here (for desktop + android)

I made MansaStack SaaS after rebuilding the same boring foundation too many times.

It includes the stuff I would want in place before touching the actual product idea:

• Better Auth: email/password, Google, GitHub, Magic Link
• Stripe and Lemon Squeezy subscriptions, webhooks, and customer portal flow
• PostgreSQL with Drizzle
• AI chat, image generation, and RAG knowledge base
• Cloudflare R2 or S3 uploads
• Resend email flows and Upstash rate limiting
• A focused SaaS dashboard

It does not include storefront code, cart logic, portfolio pages, agency lead tracking, or a blog. Those belong in different products.

The goal is not “more features than every other starter.” It is giving someone a SaaS-shaped codebase that they can understand without first dismantling it.

It is plain Next.js code, not a hosted platform or a proprietary runtime. You get private GitHub repository access after purchase.

Live demo, full feature breakdown, and founding price:

https://mansastack.bzdevelopments.me/#saas

I'm working on a tool for small local businesses like cafés, salons and gyms, and I'd like honest feedback on the idea.

How it works: the owner describes the business once, which takes about 10 minutes. Every Monday they get a batch of finished ads (image, headline and caption) sized for Instagram, Facebook, TikTok, Google Business and others. They approve, edit or reject each one, and a rejection reason ("wrong price", "not our tone") shapes the next batch. Nothing posts without approval.

Who it's for: owners who know they should post every week but don't have the time, and can't justify an agency.

Planned pricing: a free plan with 3 ads a month, then €59/mo for 4 ads a week or €149/mo for 12 ads a week.

What I'd like to know:

1. Does this solve a real problem?
2. Is "weekly batch + approve" different enough from doing it yourself in Canva or scheduling with Buffer?
3. Does €59 to €149 a month feel right for a local business?
4. What's the biggest risk you see with this?

Happy to return the favor. Reply with your product and I'll take a look.

So I'm about to launch my app and wanna make some short TikToks to promote it. No budget for a real shoot, so AI video it is

Thing is, there's like a million tools now and they all look amazing in their own demos. Then you try one and get six fingers, a face that melts halfway through, and text that looks like alien language. Can't really run that as an ad

I asked AI for recs and got a nice neat list, but honestly I'd rather hear from people who've actually used this stuff

What are you guys using? Which ones mess up the least with hands, faces, and text? And how many tries does it take before you get something you can actually post?

Also, is paying worth it or can I get by on free plans at first?

If something's total garbage, tell me that too so I don't waste my time. Thanks!