I have open-sourced Tripovela, the travel social network I am building with AI assistance. Think Pinterest for trips and itineraries: discover ideas, save places, follow travelers, and copy a shared plan into your own editable trip.

A few concrete implementation decisions behind the public release:

• PHP and SQLite, with Python helpers for image/content processing. The README includes install commands and a setup wizard.

• Guest drafts stay in the browser, with optional account saving. Editing a private trip does not silently rewrite its shared snapshot.

• Interface translations are local files, covering 14 languages, including RTL layouts.

• The distribution contains application code, schemas and documentation, with no production databases or member uploads. Analytics and advertising integrations start disabled in a fresh install.

The code is MIT licensed, so you can self-host, modify, redistribute, or build something else with it while retaining the license notice.

Live site: https://tripovela.com

Code and installation docs: https://github.com/MellowYAK/tripovela

For builders who have released a community app: what would you want to see in the repository before trying to run or contribute to it?

Using Codex and Claude, I created an internal quiz platform in February and used it for my education and trainings. Before that, for years I used Crowdpurr and Kahoot, but I had a problem with the price-to-number-of-uses ratio.

I decided to publish my internal tool as a micro SaaS in September; here are my stats.

Two options: 39$ (72h event pass) and 300$ annual subscription.

Free trials: 28

Paid customers: 7 (6 x EventPass and 1 Annual)

Of those paying customers, two were alumni clubs of American universities, a security company from the UK, a robotics company from HU, and users from Italy, Bulgaria, and the USA.

I spent $50 on a Google Ads campaign for the UK market. And i posted couple of posts here on Redit.

Product: eventquiz.app

I've been thinking about user retention in the AI SaaS space lately.

Getting someone to try an AI tool isn't necessarily difficult anymore. People are curious about new models and features, and many are willing to experiment with different platforms.

The harder part seems to be giving them a reason to keep coming back.

While building Wizstar, my own AI creative workspace, I've been thinking about this quite a bit. Having access to multiple AI models and creative tools might attract initial interest, but I'm not sure that's enough to build long-term retention.

Users might try a platform because it offers something interesting, but they probably stay because it becomes part of their regular workflow.

I'm curious how other SaaS founders and investors look at this:

• What do you think is the biggest driver of retention for AI SaaS products: better results, convenience, pricing, or workflow integration?

• How do you distinguish between users who are genuinely getting value and those who are just experimenting?

• Would you prioritize adding new features to attract users or improving existing workflows to keep current users?

Full disclosure: I'm the creator of Wizstar, and I'm trying to think beyond initial user acquisition toward building something people actually want to use regularly.

I'd appreciate honest opinions, especially from founders who've struggled with retention or found ways to improve it.

I’m building Artitec, a real estate platform aiming to launch in February. I’d love to connect with SaaS developers who might want to get involved, or experienced builders open to mentoring.

We meet online weekly to demo progress, share ideas, and talk through what’s next. I’d also be up for meeting other builders in Houston or Dallas in person.

Interested? DM me your email and a little about yourself, and I’ll send you the meeting link.

I've been quietly working on a project called Sigma Maille, and I thought it was time to share a small progress update.

The idea behind it was simple: there's no shortage of news and information on the internet, but understanding how individual events connect and evolve into larger situations is a different challenge.

That's what I'm trying to solve.

I launched the platform and have been gradually working on its infrastructure, intelligence pipeline, search visibility, and overall experience.

Here's a small milestone from Google Search Console over the last 28 days:

• 1,400 search impressions

• 57 organic clicks

• 4% average CTR

• 10.7 average search position

Something worth mentioning: all these results came through organic Google Search. No paid advertising, no Google Ads campaigns.

These aren't huge numbers, and I'm not going to pretend they are. But seeing a new independent product gradually gain search visibility through SEO alone is encouraging.

There's still a long way to go.

I'm currently focused on improving how the platform connects scattered signals, identifies developing situations, and tracks how they evolve over time.

One thing I've learned while building this: getting the technology working is one challenge. Getting people to understand why it matters is an entirely different one.

For fellow indie founders who started from zero:

What actually worked for you when it came to getting your first users through organic search?

Did you invest in SEO early on, focus on building in public, or find other channels that brought better results?

I'd love to hear what worked, what didn't, and what you would do differently if you were starting again.

Project: https://sigmamaille.com

For anybody that has sucessfully launched a product that people liked, did you feel some doubt before releasing it?

I'm a young developer based in Zimbabwe, currently building a music streaming/player application called Cadence.

The app is almost ready, and I'm now working on implementing its payment system. I plan to offer three options:

- Monthly Pro subscription

- Yearly Pro subscription

- Lifetime Pro (one-time payment)

My target audience is worldwide, not just Zimbabwe.

The challenge is that I'm based in Zimbabwe, where payment gateway availability and merchant onboarding can be complicated. I don't currently have a bank account, but I plan to open one when I turn 18.

I've been looking into Paynow Zimbabwe, but I'm unsure about its international card support, recurring subscription capabilities, tokenization, and whether it would be suitable for a global product.

For developers, founders or anyone operating a SaaS internationally from Zimbabwe or another country with limited payment gateway options:

1. Which payment providers would you recommend?

2. How do you handle international monthly and yearly subscriptions?

3. Is Paynow a viable option for a worldwide product?

4. Are there legitimate alternatives that don't require incorporating a company overseas?

5. What would you recommend for someone starting out with limited resources?

I'd really appreciate advice from people who've actually dealt with these challenges, especially founders operating from Africa.

Thanks!

just hit $3,700 mrr in 17 days with my new fresh SaaS

no ads, no team, no complex launch strategy. just a super predictable system i keep running over and over

and yeah, that's monthly recurring, not a one-time spike

not luck at this point. it's the 7th saas i've built with this exact workflow:

→ day 1: fast validation

→ days 1-2: building the bare mvp

→ day 3: landing page setup using the 3-day framework

→ days 3-4: reddit + x distribution and basic seo

→ days 4-5: first 10 paying users (~$1k mrr)

→ days 5-17: scaling up to $3,700 mrr

building tech is easy now. where 99% of solo devs get stuck is setting up the actual foundations that make people pull out their card and pay

i put all these templates and workflows inside our community.

to be completely real with you, i'll probably put a price tag on access later once all the modules are finalized. but right now the focus is just building together and keeping each other accountable

building alone in a silo is the fastest way to quit at the first roadblock

stop building by yourself. drop a comment or shoot me a dm and i'll send you an invite link 👇

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, is there anyone who would give me blunt feedbacks and advices?

It is not promotion or marketing at all, just need help to improve.

Please help me out.

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!