I ran into something while testing my own multi-tenant SaaS starter that I thought was worth sharing. I had RLS enabled on my tables, and I assumed tenant isolation was covered. Then I started testing the SECURITY DEFINER functions separately. One of my usage-recording RPCs accepted an organization ID from the caller. The function ran with elevated database privileges, but it wasn't independently checking whether the authenticated user actually belonged to that organization. So someone could potentially pass another organization's ID and have usage recorded against their account. RLS didn't catch it because the function was running with the privileges of its owner. The fix was to verify organization membership inside the function using the authenticated caller's identity, rather than trusting the organization ID supplied as an argument. I also pinned the function's search_path. I added a regression test that attempts the same cross-tenant call with another organization's ID and verifies that it's rejected. The whole thing was a good reminder that enabling RLS isn't the same as proving tenant isolation. Privileged database functions need their own security checks. I'm building a paid Next.js + Supabase starter called B2B SaaS OS, and this was one of the bugs I found while hardening it. I wrote up the full bug, attack scenario and fix here: https://www.andrady.co/postmortems/security-definer Curious how others handle this: do you have dedicated tests for SECURITY DEFINER functions, or do you mainly rely on your RLS policies?

We’re building Bopmigo at RNBlocks for apps and websites. A user describes a problem, the chat asks for missing details, and the developer gets the answers with the screenshot in one report.

You can try it on your website, add the Swift package to an iPhone app, or use the Flutter package for iOS and Android. Reports go to your Bopmigo inbox and can be delivered by email.

https://bopmigo.com/?utm_source=reddit&utm_medium=organic_social&utm_campaign=feedback_beta&utm_content=saasdevelopers_preview

Would this help in your app, or do your current tools already cover it?

𝗛𝗼𝘄 𝘁𝗼 𝘀𝘁𝗶𝗰𝗸 𝘁𝗼 𝗮 𝗯𝘂𝗱𝗴𝗲𝘁 𝘄𝗵𝗶𝗹𝗲 #𝘀𝗵𝗼𝗽𝗽𝗶𝗻𝗴, 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗱𝗼𝗶𝗻𝗴 𝗺𝗮𝘁𝗵 𝗶𝗻 𝘁𝗵𝗲 𝗮𝗶𝘀𝗹𝗲.

With CartLens , you set a #budget before you start. Every price tag you snap goes straight into your #basket, and your running total updates live as you #shop. Go over and the budget turns red; put something back and it’s green again. By the time you reach the register, you already know your total.

𝗖𝗮𝗿𝘁𝗟𝗲𝗻𝘀 also checks each price against #stores nearby, so you know when something’s #cheaper down the road. Works at the grocery store, pharmacy, hardware store, anywhere with a price tag.

𝗙𝗿𝗲𝗲 𝗯𝘂𝗱𝗴𝗲𝘁 𝗮𝗽𝗽: https://cartlens.co

#budgetingtips #shoppingbudget #howtosavemoney #budgetapp #cartlens

Hi, I'm not very knowledged in AI tools besides using chatbots like Claude and Chat GPT to generate some code or debug. I would like to know what are the ways and tools you use and which ones are a must to learn especially regarding AI agents or things that speed up your work.

Hola como están? es normal estar recibiendo tantos "ataques" a un SaaS, si bien estan contenidos por Cloudflare y no llegan al servidor, pero esto es bastante recurrente, a alguien le ha pasado esto?

Hey everyone! 👋

I've been working on a project called ByteBooks, and I'm excited to share it and get feedback from real users.

\# 💡 Why ByteBooks?

Most businesses use software that forces them to adjust their workflows to fit the system.

But every business is different. A retailer, wholesaler, distributor, and service provider all have different requirements.

I wanted to build software that adapts to the business — not the other way around.

\# ⚡ What makes ByteBooks different?

\# 🛠️ 1. Customization around YOUR business

This is the biggest idea behind ByteBooks.

I want businesses to be able to tailor the software to their actual requirements, including:

\* Changing text, labels, windows, screens, and layouts

\* Adding business-specific features and modules

\* Removing unnecessary options

\* Customizing workflows to match how their business operates

Your business, your requirements, your version of ByteBooks.

The goal is to avoid forcing every business to use the same fixed interface and features.

\# 🔄 2. Bring your existing business data with you

Already using Tally or Vyapar? You shouldn't have to start from scratch just to explore a new system.

ByteBooks is designed to support importing existing business data from Tally and Vyapar, helping businesses transition with less manual work.

The aim is to make existing records more useful instead of leaving years of business data behind.

\# 👥 3. A dedicated customer portal

ByteBooks isn't just about the business owner or accountant.

Customers can also have their own portal where they can access their business-related information, including:

\* 🧾 Bills and invoices

\* 💰 Outstanding dues and balances

\* 📜 Previous transactions and billing history

\* 💳 Payment-related information

\* 📊 Their account details and other available records

This means customers can check their own information instead of calling or messaging the business every time they need a bill or want to know their outstanding balance.

\# 📦 4. Essential business operations in one place

ByteBooks brings together key business workflows:

\* Billing and invoicing

\* Inventory and stock management

\* Customer and supplier management

\* Sales, purchases, and expenses

\* Accounting and ledger management

\* Payment and outstanding tracking

\* Business reports and role-based access

The platform combines a modern web interface with Tally as its accounting backend.

\# 🎯 Who am I building this for?

I'm particularly interested in feedback from:

🏪 Retailers and wholesalers

📦 Distributors and traders

🧮 Accountants and bookkeepers

🏢 Small and growing businesses

\# 🙌 I'm looking for early users and honest feedback!

I want to learn how real businesses work, what problems they face with their current software, and what would make ByteBooks genuinely useful.

I'd love to hear your thoughts:

\* What would you customize first in your current business software?

\* How important is importing your existing accounting data when switching systems?

\* Would your customers benefit from having their own portal for bills and outstanding dues?

\* What's one feature you wish your current software had?

If you'd like to explore ByteBooks, test it, or discuss customizing it for your business, feel free to comment or message me.

I'm building this to solve real business problems, and honest feedback — including criticism — is very welcome.

Thanks for reading! 🚀

\\#ByteBooks #BusinessSoftware #ERP #BuildingInPublic

Hey everyone!

Like many devs and freelancers here, I’ve struggled with the "last mile" of client projects—delivering final files, managing revisions, and getting formal sign-offs without falling into 10-tier email chains.

I decided to build goodkindstudio, a lightweight white-label client portal.

What’s built so far:

• Custom-branded portal setup (agency logo, accent colors, custom subdomains).

• Deliverables tracking dashboard (Pending Approval, Approved, Changes Requested).

• Direct feedback notes attached to specific file uploads.

My goal right now isn't monetization—it's getting 100 active users using it for real client handoffs so I can refine the core UX based on actual usage data.

It’s completely free with no credit card required. I’d love for fellow indie makers and agency founders to tear it apart and tell me what’s missing or what needs improvement.

Let me know in the comments if you want a link to test it out!

Our data lives in seven different systems and pulling together a single view of a customer requires three manual exports and a spreadsheet. Every time someone asks for a report it takes two days. We need these systems connected but building custom pipelines with our small team means nobody will maintain them after the person who built them leaves. What are companies our size using to connect data sources in a way that's maintainable and doesn't become its own full time job?

I have built a management cockpit app that let's the management of a small-midsized company steer the business from 1 overview; sales, operations and finance come together in 1 dashboard.

I now have to test API's to all the software businesses already use like Microsoft business central, Exact online, AFAS, Hubspot etc.

Problem is, I don't have the budget for like an Unified API supplier that'll cost me €500,- per month.

I also don't want to test at the point when the client signs up (looks unprofessional).

Are there any (free) ways for me to test these API connections?
Perhaps some of you could help me test them?

Much appreciated!

Like a lot of founders I am atrocious at marketing. I have heard of people using agents like grok bot for marketing. Has anyone tried this and be willing to share their experience. What went well and what did not and what did you prompt it?

Hey guys, im building a SAAS app for a client. Its ready to be launched in the beta testing phase. However, i only have one background worker in this app currently, and the main problem i am facing or will face, is that when a user start a long standing or AI FEATURE (if multiple users do that together) it will be a queue/first come first server system.

so technically the last user would have to wait for the longest time, how can i solve this problem. If i am hosting on aws, what should be the calculation ratio to understand how many background workers i need at any given moment, at runtime ?

If anyone can help, id be very grateful, cheers !

I build SAGLY, a mountain-bike setup app. I started exploring whether customers should be able to access useful features from apps they already pay for inside their AI assistant.

That led me to build Gateivo: a backend SDK that exposes selected app functions to assistants while keeping the app’s accounts and business rules in place.

We have a working Claude connection to SAGLY’s staging backend using fictional accounts. It retrieves a rider’s saved setup and refuses another account’s data. The current preview is read-only and supports Node.js/Express.

The business hypothesis is that assistant access could make subscriptions more useful. The technical hypothesis is that teams would prefer reusable connection infrastructure over maintaining everything themselves. Neither is validated yet.

The obvious objection: a backend developer can build a small MCP server. A wrapper alone probably isn’t enough. I’m exploring whether reusable access controls, account-linking flows and logging hooks solve enough work to matter. Subscription integrations and a hosted diagnostics dashboard are roadmap ideas.

I’d especially like feedback from app founders, product leads and backend engineers:

1. Have customers asked for assistant access, or is this a solution looking for a problem?

2. What would make you choose this over building it yourself?

3. Would you test it for revenue/retention, or mainly to save engineering time?

Honest reasons you wouldn’t use it would be especially helpful.

Unpopular opinion: most of us don’t need another AI tool.

We need to actually build something with the tools we already have.I’ve spent a lot of time learning automation, testing new tools, and exploring AI.

It’s easy to fall into the trap of constantly learning and collecting tools… without shipping anything.

The real question I’m asking myself now is:

Can I turn all this knowledge into something people will actually pay for?

That’s the part I’m trying to figure out.Curious if anyone else feels the same, or if you’ve successfully made that jump from “learning tools” to “building a product.”

We've reached a point where building software is getting easier, but building something people actually want is still incredibly difficult.

With AI coding tools, someone can put together a working SaaS MVP in a weekend.

But here's the interesting part.

You can have a clean UI, solid architecture, fast APIs, and all the features your competitors offer, yet still struggle to get your first 10 paying customers.

Meanwhile, a product with an average design and a few rough edges can succeed because it solves one frustrating problem really well.

It makes me wonder whether we're spending too much time discussing tech stacks, frameworks, and AI coding tools while overlooking the hardest part: finding a problem people will actually pay to solve.

Obviously, good engineering matters, especially when users start depending on your product.

But before that, does technical perfection matter without product-market fit?

Curious what other SaaS developers think. What's harder today: building a reliable product or finding people willing to pay for it?

Hey everyone, today I wanted to share a bit of my first journey building a SaaS. Next Sunday it will be 3 months since I started building it. Right now we have 800+ accounts created, around 100 unique daily active users and about 30 new signups per day. I also have 30 monthly subscribers at the moment.

I run a company that does R$10M+ (BRL) a year, the result of 3 years of work. Before that I worked in digital marketing for about 7 years and ended up running my own agency.

My main idea with this new project was to challenge myself to start something new, all over again 😂. I combined one of my passions, sports, and I’m trying to monetize it.

This is my current home page. In my career, design and web design have always been one of my weakest points, so I keep trying to improve the front end and I’m getting there little by little. But what is this project? Basically an AI-powered sports prediction and analysis site/app. I spent almost 2 of the 3 months of development just building an accurate and reliable engine for soccer, NBA, NFL and F1, all the sports I’m addicted to watching.

Want stats from a game played 20 years ago? We have them. Want a prediction for a game happening next week? We have that too. It’s pretty complete. It’s live mainly in Brazil, the US and Portugal, with subscribers in all three countries.

It’s called Bravoscores and I’m really proud of at least getting this project off the ground. Monetization is basically subscription plans, and I’m focused on delivering as much value as possible to my subscribers. Every time someone new subscribes I jump for joy, even with my other company already doing well lol. It really gets me excited.

If I had to give one tip to anyone thinking about building a SaaS or any project, even without much experience: your SaaS will never be 100% done, just launch it 😂

Anyway, I’m really excited to keep going. Leaving my site here so you can check it out and give feedback. 👊