Les PROBLEMES de SaaS qui commence à marcher | Lumail 10k$ #3

Les PROBLEMES de SaaS qui commence à marcher | Lumail 10k$ #3

The PROBLEMS of a SaaS that's starting to take off | Lumail $10k #3

Title history
  • Les PROBLEMES de SaaS qui commence à marcher | Lumail 10k$ #3 — observed on 20261101-0039 UTC (YouTube)

by Melvynx · View the channel on PSI

Applied Sciences & Engineering Economics & Finance KJBusiness and ManagementKJHEntrepreneurship
🎙 Melvynx 👥 67K 📅 September 7, 2026 ⏱ 23 min 👁 16K 📄 expert opinion 🧭 2026-11-01
Available in: English (current) Français

Keywords

LumailInngestAWS SESHatchetTanStack

Summary

This is the third episode of Melvynx’s series on scaling his email SaaS, Lumail, to €10k MRR. The video focuses on the problems encountered during a week of intense technical work. The main issues include a sudden $295 bill from Inngest due to excessive job runs caused by a client’s bug, and a severe AWS SES bounce incident where a user sent 14,000 emails to their own address, triggering a deliverability alarm. To address these, he implemented stricter email security measures, including automatic bounce detection and account blocking. Additionally, he faced significant problems with Next.js, such as high memory usage and slow builds, leading to a complete migration to a TanStack-based stack. He now self-hosts his orchestration using Hatchet instead of Inngest, and runs his own CI on a Hostinger VPS. The new architecture includes a Redis database, a SMTP bridge, and uses Neon for the database. He shares cost breakdowns and explains how his new self-hosted approach reduces per-user costs and improves stability. The episode concludes with a call to subscribe and a brief promotion of his AI Builder Club.

181 words

Critical Evaluation

Value of the Information & Strength of the Argument

The value of this video lies in its transparency about real-world SaaS scaling challenges and the concrete solutions applied. It offers practical insights into cost management, security hardening, and architectural decisions. The argumentation is based on personal experience, with specific numbers (e.g., $295 Inngest bill, 14,000 bounces, 3% CPU usage) that support his claims. However, the reasoning is largely anecdotal and not backed by comparative studies, and there is a promotional angle for his own products, which slightly biases the presentation.

Scientific Rigor, Source Quality, Title Accuracy

The video lacks scientific rigor in the strict sense; it is a developer vlog sharing experiential knowledge. Sources cited in the description are solely Melvynx’s own links (blog, courses, GitHub, etc.), with no external references to authoritative documentation or studies. The title/content alignment is good: the video thoroughly covers problems and solutions. No third-party sources are provided to corroborate the claims, but the technical details are consistent with common practices in the industry. The adequacy of the title is rated positively.

177 words

Title / Content Match

The title points to problems encountered when a SaaS scales, and the video indeed presents several significant problems (billing, bounces, crashes) and solutions, making it adequate.

Quality & Reliability

7/10

The video provides concrete details on costs, technical issues, and architecture changes, but remains subjective and includes promotional content. The experience is real, yet generalizability is limited.

Chapters

Cited Sources

Contribution & Novelties

The video provides an insider’s view on scaling an email SaaS, with concrete examples of unexpected costs and technical failures. It demonstrates a migration path from a managed orchestration service (Inngest) to a self-hosted one (Hatchet), along with a shift from Next.js to TanStack, highlighting the trade-offs and benefits of self-hosting in terms of cost and control. This is original in its transparency and actionable details.

Pour aller plus loin :

  • TanStack — The framework used for the migration; official docs and resources.
  • Next.js — The framework they moved away from; useful for comparison.
  • AWS SES — The email service involved in bounce issues; documentation on deliverability.
  • Neon — The serverless Postgres database utilized; relevant to their architecture.

118 words

Radar Profile

The radar profile shows high scores for information quantity and technical depth, indicating a content-rich and technically detailed video. Quality and reliability are moderate, reflecting the subjective and experience-based nature. The overall balance suggests it is valuable for developers facing similar scaling challenges.

Reliability 6/10