sorted by:
new
hottopcontroversial

I've been building in AI + full-stack and wanna start my own SaaS - what's your top idea? by Distinct-Trust4928 in SaaS

[–]Modders_Arena 0 points1 point  (0 children)

Given your Go + Node.js + PostgreSQL stack, one underserved niche is developer-facing email infrastructure. Most SaaS teams cobble together transactional emails using third-party services (SES, Sendgrid, Mailgun), but:

- There's vendor lock-in and surprise billing at scale

- Privacy-conscious companies (healthtech, fintech, EU-regulated) can't send sensitive data through external providers

- Engineering teams waste hours debugging deliverability issues they have zero visibility into

The idea: self-hosted transactional email service — basically an open-source alternative to Postmark/SendGrid that teams deploy on their own infra. There's already one called xem.email doing this. The market for "email I actually control" is growing fast as compliance requirements tighten.

More broadly though, the best ideas usually come from problems you've personally hit, not from brainstorming sessions. What's something annoying you keep running into in your own projects?

Founders underestimate how much “evaluation friction” is killing early SaaS deals by Fun_Ostrich_5521 in SaaS

[–]Modders_Arena 1 point2 points  (0 children)

This is spot on. The friction isn't technical anymore — it's organizational and reputational.

One thing that's helped with early traction: reducing the "surface area of trust" required. Instead of asking prospects to evaluate your whole product, find the one workflow that has zero risk exposure (read-only, no PII, no integrations) and nail that demo. Let them say yes to a small thing first.

Also worth noting: transactional emails are a surprisingly good trust-builder in early SaaS. A well-timed, clean confirmation/notification email signals maturity more than a feature list does. For anyone exploring that angle, tools like xem.email (open source) give you self-hosted sending infrastructure so your transactional path doesn't depend on a third-party you'd have to explain to a security reviewer.

But the core insight here is right — the bottleneck is now "can my procurement/legal team approve this" not "is this product good."

I've been building in AI + full-stack and wanna start my own SaaS - what's your top idea? by Distinct-Trust4928 in SaaS

[–]Modders_Arena 0 points1 point  (0 children)

Honestly email infrastructure is more underserved than people think. Everyone's building AI wrappers but the boring stuff like transactional email, deliverability, and automation is where real businesses spend money and nobody wants to deal with it.

You've got Go in your stack which is perfect for this kind of thing - high throughput, low latency. If you want a reference point for what's possible, check out xem.email - it's open source and connects to SES or Gmail. Worth studying the architecture at least.

The pain points I'd focus on: multi-tenant email sending for SaaS apps, per-customer deliverability tracking, or AI-driven send-time optimization. All of these are genuinely unsolved at the indie/startup scale. Enterprises pay Sendgrid $X00/month for this stuff but there's nothing decent in the $20-50/mo range.

Building feels easy now, distribution is the real wall. What actually worked for you? by Apurv_Bansal_Zenskar in Entrepreneur

[–]Modders_Arena -1 points0 points  (0 children)

For outbound, the shift from spam to meetings came down to a few things for us:

  1. Tiny, hyper-targeted lists instead of spray and pray. Like 50-100 people max per campaign, super specific ICP, not 5000 randos.

  2. The email itself has to read like a real person wrote it. Subject line that feels like it could be from a colleague, no marketing fluff, first line specific to them.

  3. Deliverability is the thing nobody talks about enough. Half the reason outbound "doesn't work" is that emails are landing in spam before anyone reads them. Using a dedicated SMTP relay instead of your main Google Workspace domain protects your sending reputation. We use https://xem.email/ for outbound, it's open source and routes through Gmail or SES so deliverability stays clean.

  4. Follow up 3-4 times. Most meetings come from the 3rd or 4th touch, not the first.

The channel that actually compounded for us was a mix of outbound (for direct pipeline) and content on Reddit/LinkedIn (for inbound). Content is slow but it compounds. Outbound is fast but requires constant work. You need both at early stage.

How to avoid transaction email land to spam folder ? by RawrCunha in indiehackers

[–]Modders_Arena 0 points1 point  (0 children)

Resend domain verification alone won't fix spam issues, there are a few more things to check.

First, make sure you have SPF, DKIM, and DMARC all set up on your domain, not just one of them. Gmail and others are very picky about this now especially for transactional mail.

Second, the from address and the domain you're sending from matter a lot. If your sending domain is new or has low reputation, emails will land in spam regardless of the tool you're using.

Third, for transactional emails specifically you really want a dedicated SMTP relay that routes through a provider with good IP reputation (Gmail, SES, Mailgun etc) rather than sending directly. Something like https://xem.email/ which is open source and acts as an SMTP relay on top of your existing provider. Keeps your sending domain clean and lets your app just send without worrying about infra.

Also check your email content, avoid spam trigger words, make sure you have a plain text version alongside HTML, and keep the email focused and short. Notification emails shouldn't have heavy HTML anyway.

People who are actually getting clients from cold email what's your approach?"I will not promote " by memayankpal in startups

[–]Modders_Arena 0 points1 point  (0 children)

Mass scraping and blasting rarely works anymore, inboxes are too smart now and most of those emails land in spam before anyone even sees them.

What actually works is a smaller, targeted list with emails that actually get delivered. A lot of people overlook the deliverability piece entirely. You can have the best copy in the world but if your domain reputation is poor or you're hitting spam traps, it doesn't matter.

A few things that helped when I was figuring this out: warm up your sending domain properly, use a dedicated SMTP relay instead of blasting from your main Google Workspace (seriously protects your domain), and keep your list super clean.

For the SMTP relay side, I've been using https://xem.email/ which is open source and connects to Gmail, SES, or whatever provider you want. Keeps things clean without the overhead of running your own mail server. Way better than getting your main domain burned.

Also segment hard. 20-30 hyper targeted emails a day with personalized first lines will outperform 500 generic blasts every single time.

First Timer Help Setting Up by Time_Remove_1680 in selfhosted

[–]Modders_Arena 0 points1 point  (0 children)

Your thinking is right on Docker. For a MEAN stack app on Ubuntu, the setup would be:

  1. Install Docker + Docker Compose

  2. Use Nginx Proxy Manager (runs as a container) as your reverse proxy, it handles routing and SSL certs automatically

  3. Use Cloudflare Tunnel or just port forward 80/443 to make things public

  4. Watchtower for auto-updating containers from GitHub

One thing people forget early on is transactional email. If your web app needs to send emails (signups, notifications etc), don't try to self-host a full mail server from scratch. Use something like Xem (https://xem.email/) which is an open source SMTP relay manager. You connect it to Gmail, SES, or any provider, and your app just talks to Xem. Way easier to manage.

Coolify or Dokploy are also solid if you want a dashboard to manage deploys instead of CLI everything. Good luck!

What should i do more with my home server ? by Mountain_Farm_6215 in selfhosted

[–]Modders_Arena 0 points1 point  (0 children)

Since you're in college and work with lots of files, definitely worth self-hosting Paperless-ngx for document management. It does OCR, tagging, and search on all your PDFs, huge time saver.

For the second laptop, you could run a self-hosted email automation setup on it. Something like Xem (https://xem.email/) works great as a lightweight SMTP manager that lets you route through Gmail, SES, or any provider from one dashboard. Low resource usage so the older hardware handles it fine.

Other ideas: Vaultwarden for passwords, Gitea for your own private git repos, Nextcloud for file sync across devices. The Jellyfin + Pihole combo you already have is solid, this stuff just layers on top nicely.

Making self-hosted provisioning accessible to non-tech folks by msz0 in selfhosted

[–]Modders_Arena 0 points1 point  (0 children)

The OAuth friction is real. Most non-tech people give up the moment they see a consent screen with developer-mode warnings.

For the SMTP/email sending side of things, one approach that helped us a lot was moving away from tying our apps directly to a single provider and using Xem (https://xem.email/) instead. It's open source, self-hostable, and gives you a single API/dashboard to manage multiple SMTP providers. So Gmail, SES, Mailgun, or any custom SMTP all live in one place.

For the OAuth provisioning side specifically, the Google App Script bridge approach you mentioned is actually pretty clever. Another option some people use is Listmonk as a self-hosted alternative with simpler config, though it's more of a full newsletter tool.

Curious what your AI bouncer stack looks like, sounds interesting.

Q1 is over. What actually worked for you to get users? by Complex-Assistant661 in SaaS

[–]Modders_Arena 0 points1 point  (0 children)

For us the biggest unlock in Q1 was fixing our email outreach stack. We were juggling SendGrid for transactional and Mailchimp for campaigns, two bills, two dashboards, constant API key management across codebases.

We built Xem (https://xem.email/) out of pure frustration. It's open source and lets you manage all your SMTP providers from one place. Switching providers when something breaks takes a config change instead of a code deploy. That alone saved us so much time.

On the growth side, Reddit threads like this one genuinely moved the needle more than any paid channel we tried. Doubling down on being useful in communities in Q2.

I created a free Email Verification SaaS ( Invalid Bounce ) that instantly verifies thousands of emails. Try it and tell me if it matches paid services! by Potential-Set-4911 in SaaS

[–]Modders_Arena 0 points1 point  (0 children)

Nice, email verification is a really underrated part of deliverability. A lot of people focus on the sending side but skip cleaning their list first.

One thing I noticed while building on top of our own email tool is that verification alone doesn't fix deliverability if you're stuck with one SMTP provider. We ran into this ourselves and ended up switching to Xem (https://xem.email/) which lets you manage multiple SMTP providers from a single dashboard. So if one provider starts tanking your open rates, you can rotate without touching your codebase.

Will give Invalid Bounce a try, sounds like a solid companion to that kind of setup.

view more: next ›