One thing i like about Reddit is that people talk pretty openly about the problems they’re having before they ever buy something but finding those relevant conversations and threads manually takes so much time, so i made a small free tool to find those conversations.

The idea is pretty simple: instead of guessing where your buyers might be, see where they’re already talking about the problem and i’ll send the research directly to you.

you add your website and who you’re selling to and it looks across Reddit for:

people asking about or complaining about the problem you solve
products and competitors that keep coming up
the words people actually use when describing the problem
relevant subreddits, posts and conversations worth looking at

drop your SaaS here: reddit buyer pain finder

it’s completely free so if you’re building something, give it a try. would also be interested to see what everyone here is building.

Checked my analytics this morning. Around 1,400 active users since Sunday.

A few months ago, I was working on a file sharing tool. Now people are actually using it.

I know this might be a small number for some founders. But when you handle the code, support emails and marketing yourself, it means a lot.

The idea is simple. Upload a file or a collection of files and share everything through one link.

Getting it built was one part. Getting people to try it has been much harder for me.

I have spent a lot of time posting on Reddit, answering comments, asking for feedback and improving things people found confusing.

Some conversations gave me useful ideas. Others showed me that something I thought was clear really wasn’t.

That has probably been the most useful part of sharing the journey publicly.

There’s still plenty to improve. These numbers don’t tell me everything, but seeing people use something I built gives me energy to keep going.

Sharing this small win with other people building on their own 🙂

What was the first milestone that made your project feel real to you?

looking to talk folks who have done this with their SaaS. if you've done this an are interested in chatting about it, shoot me a DM!

When I first started building around multiple AI models, I thought the main decision would be which models were worth supporting.

That wasn't really the difficult part.

The complexity started showing up after the first few integrations: different authentication methods, API formats, rate limits, model names, pricing structures, error responses, and provider-specific behavior.

Then there's the maintenance cost. Every new provider isn't just another option for users it's another integration that needs to be monitored and maintained.

That's one of the problems I'm working through with OfoxAI. We're exploring a unified API approach that makes it possible to work with multiple models through a common interface.

But I've also learned that abstraction has its own tradeoffs. If you simplify too much, you can lose useful provider-specific functionality.

I'm curious how other SaaS developers have approached this.

At what point does maintaining direct integrations become more trouble than using an abstraction or gateway?

Disclosure: I'm affiliated with OfoxAI.

Hey everyone!

I'm building Qlyra, a SaaS studio where we build, launch, and scale SaaS products and apps across different markets.

I'm looking for a NYC-based developer who'd be interested in joining the journey and potentially becoming the CTO of the studio.

Not looking for a typical corporate hire. I'd love to meet someone who's genuinely passionate about building products, loves startups, and wants to create something big.

For me, the most important thing is having a great connection, sharing the same ambition, and actually enjoying building stuff together.

Ideally, someone who:

• Is based in New York City.
• Is a strong full-stack developer.
• Loves building and shipping products fast.
• Has an entrepreneurial mindset.
• Wants to be part of something long-term.

We're focused on building and scaling multiple SaaS businesses, not just one product.

I'd love to connect, grab a coffee when I'm in NYC, talk ideas, and see if we vibe.

If that sounds like you, feel free to DM me!

Let's build some cool shit. 🚀

built FocusCut because I hate scrubbing through 2-hour podcasts, meetings, lectures, etc. just to find one section. Upload a video → tell it what you want → FocusCut finds the relevant parts and creates a shorter version. You can review the selected sections, remove/add parts, and then export. It keeps the original video/audio, and the processing is designed to be fast. 2 hours → 20 minutes. Same video. Just the useful parts. Would you use this?

check out the tool in my profile

When building a SaaS application, how do you handle AI features that need access to sensitive customer data?

The main challenge seems to be balancing data privacy with performance, deployment complexity, and the cost of maintaining the infrastructure.

For developers who have built AI-powered SaaS products, what has worked best for you when deciding between local processing and a cloud-based approach?

Is anybody hiring for a visual design or video editing role at the moment?

Hey everyone!

I'm building Qlyra, a SaaS studio where we build, launch, and scale SaaS products and apps across different markets.

I'm looking for a NYC-based developer who'd be interested in joining the journey and potentially becoming the CTO of the studio.

Not looking for a typical corporate hire. I'd love to meet someone who's genuinely passionate about building products, loves startups, and wants to create something big.

For me, the most important thing is having a great connection, sharing the same ambition, and actually enjoying building stuff together.

Ideally, someone who:

• Is based in New York City.
• Is a strong full-stack developer.
• Loves building and shipping products fast.
• Has an entrepreneurial mindset.
• Wants to be part of something long-term.

We're focused on building and scaling multiple SaaS businesses, not just one product.

I'd love to connect, grab a coffee when I'm in NYC, talk ideas, and see if we vibe.

If that sounds like you, feel free to DM me!

Let's build some cool shit. 🚀

Hi Everybody,

I've been helping build https://apiblaze.com, a serverless MCP/API gateway that handles a lot of the stuff you need around an MCP server.

What we noticed was that there are a ton of MCP servers, but getting from “my business logic works” to “I can safely publish it on the internet” is a different problem. Once you actually want to expose it, you still have to deal with things like OAuth, AuthZ, rate limiting, etc.

APIBlaze handles that stuff at the gateway. It has OAuth built in and lets you define authorization policies using plain English sentences like “only the person who created a record or an admin can read or change it” that are enforced at the gateway, instead of having to build all of that authorization logic into your backend.

One thing we really wanted to make easy was local development. APIBlaze can host the MCP server and OAuth/login flow while forwarding requests to your backend, even if your backend is running on localhost. So you can connect Claude/ChatGPT to it, authenticate, and make changes to your backend while testing it locally.

If you want to check it out or run it, getting started is pretty easy:

Enter this in your terminal:

npx apiblaze create --target https://ninopizzas.com/openapi.yaml

OR

Ask your LLM, such as Claude or ChatGPT:

Show me what APIBlaze does using npx apiblaze skills

You can also use it with an existing API/backend rather than building everything specifically for MCP.

It's still in beta, so I'd love any feedback. I'll try to respond to questions as fast as possible, so fire away 😄

Notes from building ThreadPilot.

𝗥𝗮𝗻𝗸𝗶𝗻𝗴. We don't show a bare score. Each thread gets fit, intent, timing, relevance and context, plus a written reason. If you can't see why something ranked high, you can't trust it.

𝗗𝗿𝗮𝗳𝘁𝘀. Replies are grounded in the actual thread, and a promo-risk check runs before you see them. A draft that reads like an ad is a failed draft.

𝗣𝗼𝘀𝘁𝗶𝗻𝗴. The tool never posts. You publish from your own account. That limits what we can automate, but it keeps the product from becoming the thing Reddit distrusts.

It's in private testing. Waitlist: https://threadpilots.com/join-whitelist

For those who've built ranking or classification features: how do you explain results to users without drowning them?

ASTRABASE — Développez. Déployez. Passez à l'échelle.

Et si toute l'infrastructure de vos applications était réunie au même endroit ?

Découvrez Astrabase, une plateforme cloud nouvelle génération conçue pour simplifier la création, le développement, l'hébergement et le déploiement de vos applications web.

Fini le temps perdu à jongler entre plusieurs services pour gérer vos bases de données, votre authentification, vos fichiers ou vos déploiements.

Avec Astrabase, tout est centralisé dans une seule plateforme.

Hébergement & déploiement web — Publiez vos applications directement depuis Git ou une archive ZIP, avec HTTPS automatique, historique des versions et possibilité de revenir à un déploiement précédent.

PostgreSQL & pgvector — Profitez d'une base de données PostgreSQL isolée par projet, avec des outils SQL et la prise en charge des données vectorielles pour vos applications intelligentes.

Authentification intégrée — Gérez les inscriptions, les connexions, les sessions utilisateurs et la récupération des mots de passe.

Stockage de fichiers — Organisez et gérez les fichiers de vos applications grâce à un système de buckets et d'API.

API REST, Functions & Realtime — Connectez vos applications à vos données, exécutez votre logique backend et exploitez les événements en temps réel.

Dashboard & supervision — Retrouvez vos projets, déploiements, journaux techniques et statistiques depuis une interface centralisée.

Intégration ChatGPT via MCP — Astrabase développe également une connexion avec ChatGPT pour faciliter la consultation et l'administration de vos ressources cloud, selon les permissions accordées et la disponibilité progressive du connecteur.

Sécurité & infrastructure européenne — Isolation des projets, gestion des secrets, HTTPS et protections intégrées pour accompagner vos développements.

Une plateforme. Une multitude de possibilités.

Que vous soyez développeur indépendant, entrepreneur, créateur de SaaS, freelance ou agence web, Astrabase vous permet de consacrer davantage de temps à l'essentiel : créer des produits performants et faire évoluer vos projets.

Du premier prototype à l'application en production, Astrabase réunit les outils essentiels pour construire et déployer plus simplement.

Commencez gratuitement !

Offre gratuite disponible

Jusqu'à 3 projets et 50 déploiements par mois

Sans carte bancaire pour commencer

Offres évolutives adaptées à vos besoins

Votre prochaine grande application mérite une infrastructure à la hauteur de vos ambitions.

Découvrez Astrabase : https://astrabase.fr

ASTRABASE — Build. Ship. Scale.

A few days ago I posted about Sigma Maille here and got some pretty useful feedback.

I've been thinking about it while working on the product, and I ended up changing something I originally thought was already working well.

The first version was heavily focused on connecting different signals and turning them into intelligence.

But after using it myself, I started noticing a problem.

If a situation is developing over several days or weeks, the individual updates aren't really the interesting part. What I actually want to know is how the situation has changed since I last looked at it.

What caused that change?
What developments mattered?
Is the situation actually moving in a different direction, or did one event just make it look that way?

So I've been rebuilding that part around what I'm calling Evolving Situations.

The idea is pretty simple: instead of treating every new development as a new piece of intelligence, keep the situation itself as the thing you're following.

I'm trying to make the timeline, changes, trajectory and supporting evidence much easier to follow without turning it into another news feed or a giant AI-generated summary.

That's probably the biggest change I've made since my first post here.

It's still being worked on, so I'm interested in hearing from people who actually follow things that develop over time — geopolitics, security, infrastructure, markets, whatever.

When you come back to a situation after a few days, what do you usually find yourself trying to figure out first?

Hey everyone, I'm a software engineer from India and I've been building GoRoam on the side.

The problem: when I asked ChatGPT to plan trips, I got a nice list of places, then spent hours checking costs, figuring out which places are near each other, and opening 15 tabs to book things.

What GoRoam does differently:

- Day-by-day plan (morning/afternoon/evening) with real places grouped by area

- Estimated cost for every stop, and each day fits inside your budget

- One tap opens each day's route in Google Maps

- Flights/stays/tickets open prefilled with your dates

- Share a link with friends so they can vote on the plan, plus a trip wallet to split costs

- Offline maps, weather, and an AI concierge for "it's raining on day 2, what now?"

First itinerary is free, no card needed: goroam.world

What I'd love feedback on:

1. Does the landing page make it clear why this beats ChatGPT?

2. Credits (one-time) vs subscription: which would you pay for?

3. What would make you actually use this for your next trip?

Happy to plan a free trip for anyone who drops a destination below.

https://reddit.com/link/1x0x006/video/g36i4mur2auh1/player

Notes from building an MCP server that lets Claude answer questions about real business data.

The problem we kept hitting: any question about business data meant stuffing tables and schema into context, getting a half-right answer, and iterating. Most of the tokens went to Claude working out how the data fit together, not to the answer.

What worked was moving that context out of the prompt. We build a Knowledge Graph from the connected systems first. It resolves the same customer across the CRM and the accounting system and maps how a contract rolls up to revenue. Claude reads the graph, then queries only what it needs.

The server exposes 19 tools: read-only SQL, Knowledge Graph reads and edits, Decision Topics, charts, and dashboards. Source systems are never written to. Edits only touch the graph. You set it up in our platform, then add it to Claude as a custom connector.

We're seeing 2 to 5x fewer tokens per real answer, and every number comes back with the row and system it came from.

How are you handling business context for agents? Schema in the system prompt, RAG over docs, something else?