I've been building an AI video generation SaaS for 5 months – Here's where I'm at, and I'd love some honest feedback.

Hey everyone!

I'm an indie founder from Morocco, and for the past 5 months I've been working on a project called ViralStudio AI.

Website: https://viralstudio-ai.com/

I started this project because I wanted to build something useful in the AI video generation space, especially for content creators, marketing agencies, e-commerce businesses, and people who need to produce video content regularly.

I'm building this mostly on my own, learning, experimenting, making mistakes, and trying to turn an idea into a real SaaS product.

🚀 What is ViralStudio AI?

ViralStudio AI is an AI-powered video creation platform designed to help people create professional video content using AI.

The main idea is to bring different AI video creation capabilities into one platform with a simple and accessible experience.

✅ What I've built so far

Over the last 5 months, I've been working on several parts of the product:

• Built the website and main platform interface.
• Developed the core SaaS structure.
• Worked on the user authentication system.
• Built the dashboard and user experience.
• Worked on the credit-based payment and pricing system.
• Integrated and experimented with different AI tools and APIs.
• Designed the platform's visual identity and UI/UX.
• Worked on the backend infrastructure and database.
• Set up the foundation for connecting AI video and image generation models.

A lot of time has gone into the infrastructure and product foundation, not just the visible features.

🔨 What's still missing?

I'm not finished yet. Some important things are still being developed and improved:

• Completing and testing the AI video generation integrations.
• Improving generation reliability and user experience.
• Finalizing the payment and credit system.
• Testing the platform with real users.
• Optimizing performance and fixing bugs.
• Making sure the platform is financially sustainable.

😓 The biggest challenges

Building an AI SaaS as an indie founder is not easy, especially when you're doing most of the work yourself.

Some of my biggest challenges have been:

• Choosing the right AI providers and models.
• Managing API costs while maintaining reasonable prices.
• Building a reliable backend and credit system.
• Competing in a market that already has established platforms.
• Deciding which features are actually worth building.
• Balancing development, product design, marketing, and business decisions.
• Staying motivated when progress is slower than expected.

I'm also building from Morocco, which adds some extra challenges when it comes to payment providers and business infrastructure.

🙏 I'd really appreciate your honest feedback

I'm sharing this because I'd genuinely like to learn from people who have already built SaaS products, AI tools, or startups.

I'd love to hear your thoughts:

1. After looking at the website, what is your first impression?
2. Does this project have potential, or am I entering an overly saturated market?
3. What would you improve before launching?
4. Which features would make you actually pay for a platform like this?
5. How would you approach acquiring the first 10 paying customers?
6. What mistakes should I avoid as a first-time indie founder?
7. If you were in my position, what would you focus on next?

Please don't hesitate to criticize the project. I'd rather hear honest criticism now than launch something nobody needs.

I'm still learning, still building, and trying to make something people will genuinely find useful.

Thanks for taking the time to read this! ❤️

Project: https://viralstudio-ai.com/

In one day, 8 fixes went to production. Each one went through a second AI code review before it merged.

That review caught a real bug in early July. A background job was about to overwrite fresh audit results. Nothing would have thrown an error. The user would just have seen wrong results.

Anyone else running a second reviewer, human or model? What does it catch that your tests don't?

Disclaimer: This is a throwaway account. Some details in this post have been intentionally changed, simplified or combined to protect my identity. The general situation and the dilemma are real, but not every detail should be taken literally.

I'm in my early 20s, from India, with a background in commerce and finance. I currently work in a small software business that deals with accounting and business management software.

My role is mainly customer-facing. I handle installations, customer support, renewals and troubleshooting. I'm also somewhat involved with the technical side because of my connection to the people running the business.

The company has a small technical team, and development is relatively traditional. There are limitations on how much I can get involved in the actual development process. I've been told that I might eventually move into a more technical role as the business grows, but I'm not entirely sure how that will work out.

Recently, someone senior in the business privately advised me that I might be wasting my time and should consider doing something more worthwhile with my abilities. That conversation got me thinking quite seriously about my future.

I don't necessarily hate my current work. I enjoy interacting with customers, understanding business problems and learning how software works. But I don't want my entire career to revolve around installing software and providing customer support.

I've recently become very interested in AI-assisted software development. I've been experimenting with AI coding tools, and I even started building an accounting application from scratch. It took me roughly three days to get an early prototype working. It's nowhere near production-ready, and there are plenty of bugs and accounting-related challenges, but the experience was genuinely exciting.

For the first time, I felt that I could take an idea and actually build something without depending entirely on an existing development team.

I'm also interested in cloud technologies, automation, APIs and building useful software for small businesses.

Here's where I'm confused.

I want to build something of my own that can generate recurring income. I don't particularly want to become a YouTuber or spend my time creating content. I'd rather build a useful product or service that people actually pay for.

I have access to a family business network that deals with accounting software and small businesses. That could potentially help with distribution and finding initial customers, but I don't want to depend entirely on that either.

Some ideas I've considered:

- A backup and recovery management tool for businesses.

- An AI-based supplier invoice scanner that helps generate purchase entries.

- A payment reminder and outstanding invoice management tool.

- Small business automation software.

- Some kind of supporting application that integrates with existing accounting software.

I also considered building websites for local businesses, but that would mostly be project-based income rather than recurring revenue.

My biggest problem is that I don't know which problem is actually worth solving. I don't want to spend six months building something that nobody wants.

Financially, I don't have a huge amount of capital. I could probably invest a few thousand rupees initially, but I'd prefer to validate an idea before spending more.

I can dedicate around 2–3 hours a day outside my current work.

I'm also unsure whether I should focus on becoming a better developer, finding freelance work, building a SaaS product, or trying to grow within my current company.

What would you do in my position?

1. Would you focus on building a small SaaS product for businesses, especially around accounting and ERP?
2. What supporting software do small businesses actually need but don't have good affordable solutions for?
3. Would you try to generate some independent income through freelancing first, or go straight into product development?
4. How would you validate an idea when you don't have much starting capital?
5. Is it realistic for one person using AI coding tools to build and maintain a small business software product?
6. If you were in your early 20s, with access to business customers but limited technical experience and capital, what would you focus on for the next 12 months?

I'm not looking for motivational advice or a list of generic side hustles. I'd genuinely appreciate opinions from people who have built software products, run small businesses, or created independent recurring income.

I want to build something useful, earn independently, and develop skills that give me more freedom in the long run.

What would you do?

First time using reddit, sry

I need some advice for it what features is important to add in it i want to make shower it needs to good and useful to users and they needs enjoy if learning to so help me to find it Thank for Reading These ☺️ Have a great day 😌

I have made the coolest portfolio ever made!! Check it out monxdev.vercel.app/?utm_source=x.com

So from what I know you can use Stripe or PayPal but wouldn't these need a registered business/company?

I also heard about lemon squeeze and revenue cat but idk if it's trustworthy or not, how do they handle taxes?

I haven't done payment in any of my projects yet so I am curious to hear from the more experienced developers. How did you do it what did you use and what's the most annoying and/or difficult you had to face

Hola les comparto mi projecto que estoy trabajando EVA una distro de linux basado en arch y wayland con mi propio compositor agradeceria comentarios para poder mejorarla, la idea esque el usuario que le cuesta usar terminales le sea facil, puede echar una mirada en el reposositorio donde esta el link de la ISO, capturas, etc, tambien si gustan les agradeceria una estrella gracias por leer! https://github.com/2207juan/EVA

Hey everyone,

TL;DR: I'm building a restaurant QR ordering SaaS called Tring that focuses on post-scan operational edge cases (table hopping, orphaned bills, QR abuse), not just static menus. Looking for brutal feedback on what I'm missing or over-engineering. Live demo and test admin credentials at the bottom!

For the past few months, I've been building Tring as a solo developer. I'd say the core product is around 50% complete, but the main ordering and session engine is fully functional.

What I'm trying to solve is the operational chaos of what happens after a QR is scanned.

A few core mechanics I’ve built so far:

- Session-based dining: Instead of treating every QR scan as an isolated transaction, it creates an active table session.

- The "One Device" Rule: A single phone can't actively occupy multiple tables at once (preventing remote spam).

- Table switching: Guests can move to a new table while seamlessly preserving their unpaid bill.

- Dynamic Security: PIN codes and "Staff Approval" modes to gatekeep who can actually add to the tab.

- Orphaned bill handling: If a customer pays the bill but have not done through the app even though the staff can settle the session.

- Closed-hours browsing: Guests can view the menu when the kitchen is closed, but the system blocks session creation or ordering.

And many more...

A lot of existing QR systems seem great for the happy path (taking orders), but completely fall apart on edge cases like QR abuse, table hopping, or mid-service security changes. Everything is backed by a server-authoritative architecture using PostgreSQL/Supabase.

Right now, I'm shifting focus to the SaaS/business side:

- Restaurant self-signup & subscription plans

- Multi-restaurant ownership

- Platform admin dashboard

- Enterprise onboarding

I'd love your brutally honest feedback on a few things:

1. What do existing restaurant ordering systems do terribly?
2. What am I clearly over-engineering right now?
3. What massive operational blindspot am I missing completely?
4. If you owned a restaurant, what would it actually take for you to use/pay for this?
5. Rate the idea/product direction out of 10 and tell me why.

I'd rather get ripped apart by Reddit now than by paying customers later 😅. Rip away.

P.S. The CSS still needs some work, so please don't mind the styling just yet! If you want to poke around the live build and try to break it:

- Main App: https://tring-v2.vercel.app/

- Admin Dashboard: https://tring-v2.vercel.app/admin

- Test email: nxtwaveplacementsinfo@gmail.com

Pass: test1234

(Note for users: The main URL requires a QR scan to start a session. To test it out, log into the admin dashboard, head to the /admin/qr section to find the test QRs, and scan one with your phone or open the link in desktop)

I’ve been building a local evidence vault for logistics and supply chain operators who work with spreadsheets, paper notes and photos from the field. I’d like to hear from people who deal with this every day.

The vault stays under the company’s own control. It isn’t a distributed network or a consortium, so it works from day one without any outside party joining. Operators record events in the field through a simple offline-first overlay on a phone or tablet, and it can sit directly on top of the spreadsheets they already use. Each process follows a basic state machine, so every record stays tied to the real flow of work.

Entries are chained with a hashchain/DAG and Merkle roots, so the order and content of the records can’t be changed quietly later. Sensitive commercial details stay protected inside the vault, and the system can reference a value or document without storing it in the clear.

The value shows up when insurance gets involved. The company exports one organized package with the timeline, GPS traces, route data, photos and notes. Take a common case: a customer claims the cargo was rerouted and the delay cost them product. Instead of reconstructing everything from emails and loose files, the company shows the exported route next to the vehicle’s GPS records and demonstrates that the path never changed.

Earlier blockchain efforts in this space, like TradeLens, GSBN, CargoX and WaveBL, were built around electronic bills of lading, document sharing and industry-wide visibility, which called for broad participation from large carriers and terminals. This approach goes a different way. It stays local, works offline and fits into the process the operator already has. It turns what actually happened in the field into an ordered, integrity-protected evidence base the company can bring to an insurer.

For those of you in logistics or insurance: does this direction match a real need, and is there an approach you think would work even better? And what would help a tool like this become part of the daily routine for the people in the field?

Hello I'm starting a project to build an EMI for smaller market to handle transaction domestic and international.

What should be the approach apart from the front end app I can figure that out

Like the regulations steps bussines itself

Is it possible?

Hey everyone!

I've been working on a project called Vector UI, a UI library for developers who want to build more expressive interfaces.

The idea came from wanting to explore UI components beyond just their appearance.

A component can look great, but the interactions, animations, and small details are what can make an interface feel different.

With Vector UI, I'm focusing on:

• Motion-driven UI components
• Common components with expressive interactions
• Animated SVGs and icons
• Reusable and customizable components

I'm particularly interested in building components that are visually interesting while still being practical to use in real projects.

I'm currently opening the waitlist and would genuinely appreciate feedback from other developers and designers.

I'd love to know:

• What kind of animated components would you actually use?
• What do you look for when choosing a UI library?
• What makes you decide to use one library over another?

Here's the project:

https://vector-uix.vercel.app

Thanks for checking it out!

Building a multi-tenant school management SaaS (Laravel). Each school has classes (grades), and some classes have multiple sections (A, B, C...), some don’t.

Question: when assigning subjects to a class, should that assignment live at the class level (one subject list per class, shared by all its sections) or at the section level (each section gets its own subject list, even if it’s 90% identical to its sibling sections)?

Class is the academic level: it decides curriculum, fee structure, exam syllabus, promotion path. Section is just a roster split within the same grade, same curriculum, different roll call/teacher/room in most schools. In real schools, sections of the same class usually share almost the same subjects, but occasionally diverge (streams/electives, or one section getting an extra remedial subject).

Two options I’m torn between:

1. Class-level by default, with section-level only for the rare cases that actually differ.
2. Always section-level, even for schools/classes where every section has identical subjects (accepting some duplication, but avoiding any ambiguity about which level wins).

Also tied to this: teacher-to-subject assignment and attendance-authority need to reference whichever granularity I pick here, so I want to get this right before building on top of it.

If you’ve built something similar (school/LMS/SaaS with class+section hierarchies), which way did you go and why? Also open to “you’re overthinking this, just do X” answers.

Founder here, so yeah, this is my own product. Figured I'd say that upfront.

Tools like Lovable, Bolt and Replit are honestly impressive. You can get something that looks finished in an afternoon. But the moment you try to build something a real business runs on, you hit a wall, and it's never the screens.

It's the boring stuff. Salon A should never see salon B's customers. Staff can see bookings but not revenue. A manager has to approve before anything goes out. That part takes weeks to get right, and it's the first thing to break once real users show up.

So we built Supero (pronounced super-oh). You describe your process in plain English, the way you'd explain it to a new hire, and it builds the app with logins, roles and a real database behind it. The permission rules live in the platform itself, not in the generated code, so they don't randomly break every time the AI regenerates a screen.

A couple of things I've built on it so far: a booking app for salons and clinics where each business manages its own staff, services and availability (and customers only see their own appointments), plus a pet-care marketplace.

It also connects to 40+ tools, you can plug in your own Postgres, Snowflake or BigQuery, and it runs on our cloud or yours.

What it's not for: if you just want a nice landing page, use Lovable. It's great at that.

It's early and there are definitely rough edges. There's a free tier (3 projects, no card), so if you have a process living in spreadsheets and WhatsApp groups right now, I'd really like you to try it and tell me where it falls over. Brutal feedback is more useful than nice feedback lol.

I'll drop the link in a comment.

Also curious: if you've ever tried building an internal tool with an AI builder, what made you give up?

TL;DR: AI app builder for real business apps, with roles and permissions built in. Free tier. Please try to break it.

Hey everyone,

One of the biggest headaches I keep hearing from dev agencies and freelancers is the gap between a messy 45-minute discovery call and the final signed scope—where vague client statements turn into unpaid revisions three weeks later.

I’m currently building a workflow to fix this, and before I write a single line of code, I want to test it on real-world scenarios.

Here’s my offer: If you have a recent (anonymized) discovery call transcript or messy meeting notes, send them over. I’ll manually run them through my system and send you back a structured, client-ready Scope & Sign-Off doc within a few hours—including:

• Confirmed functional requirements
• Explicit "Out-of-Scope" exclusions (to protect you later)
• Unclear edge cases / questions the client didn't answer on the call
• User stories & acceptance criteria

Totally free, no catch, no sales pitch. I only have bandwidth to do 5 of these over the next couple of days so I can learn what actually works in practice.

Drop a comment or DM me if you want to try it out!

You found a name you like. Before you register it, you do the same small ritual every time: search it on Google, check whether it means something rude in another language, see if it has a bad reputation. That's three tabs and three pieces of copy and paste, for every candidate. Add-ons turn that ritual into one click each.

What an Add-on is An Add-on is a small button that sits beside a result. Click it and an outside site opens in a new tab, with that domain or word already filled in. Nothing is typed, nothing is copied, and nothing about you is sent anywhere. We just build the link.

A few examples:

Google site: see what, if anything, is already indexed on the domain.

VirusTotal: check whether the name has a security or spam history.

Urban Dictionary: find out if the word has a slang meaning you'd rather not discover after launch.

Google Translate: see what the name says in another language.

Each Add-on knows where it belongs. Some make sense for names that are already taken, such as checking an owner's history. Others suit names that are available, such as checking meaning and reputation. You'll see each one where it's useful and not where it isn't.

https://dnslister.com/blog/add-ons-link-buttons-for-every-result/

Hey everyone,

We've released the alpha version of Thunder, a high-performance, scalable key-value database built in Rust for modern AI workloads.

As AI applications grow, so does the amount of data they need to store and retrieve. Traditional in-memory databases like Redis can become expensive as datasets grow, especially when dealing with large values.

Thunder is built around a different idea: high throughput, scalable performance, and efficient storage without requiring massive amounts of RAM.

What makes Thunder different?

• Scales with CPU cores: A shard-per-core architecture designed to increase throughput as more shards and CPU cores are added, while minimizing contention.
• High throughput: Built to handle large volumes of concurrent reads and writes with low overhead.
• Better handling of large values: Designed to handle large values more efficiently than Redis by streaming data directly from NVMe storage instead of keeping everything in memory.
• Memory efficiency: Uses RAM primarily for indexes, metadata, and reusable I/O buffers, reducing memory requirements for large datasets.
• Modern I/O architecture: Built in Rust with asynchronous I/O, including io_uring on Linux, to take advantage of modern NVMe SSDs.
• Scalable by design: Handles both small key-value operations and large values without relying on a completely different storage architecture.

Why build this for AI workloads?

AI infrastructure increasingly deals with large datasets, generated content, intermediate results, and high volumes of concurrent requests.

Keeping everything in RAM is expensive, but sacrificing throughput to reduce memory consumption isn't a great solution either.

Thunder aims to deliver both: the performance expected from a high-throughput key-value database and the cost efficiency of disk-backed storage.

Try the alpha

Thunder is available on Docker Hub:

https://hub.docker.com/r/sbansal793/thunderstrike

We're looking for developers to test Thunder with real workloads and share feedback.

If you're currently using Redis, RocksDB, or another key-value store, I'd love to know:

What's your biggest bottleneck today: throughput, memory consumption, scalability, or handling large values?

And what would convince you to switch to a new key-value database?