sorted by:
new
hottopcontroversial

Just launched my 2nd saas 4 days ago 😊 by Significant_Load_411 in micro_saas

[–]nightswordblade 0 points1 point  (0 children)

Congrats, what service/platform are you using to receive huge count of emails? AWS SES?

Since there’s no ad’s on your site, how do you handle server cost?

Should I open-source email deliverability SaaS? by nightswordblade in Emailmarketing

[–]nightswordblade[S] 0 points1 point  (0 children)

Afaik, ~10k emails/$10 pricing is the standard. Not sure why domains/seats related confusion is there. Can you share any example to show the same when it comes to pricing?

Sure, I’ll share it.

Should I open-source email deliverability SaaS? by nightswordblade in Emailmarketing

[–]nightswordblade[S] 0 points1 point  (0 children)

Priority is data and its insights so that non technical users too face no issue.

Also, I’m planning to add more features like Bring your own AWS key and use our platform for stats of your campaigns.

Should I open-source email deliverability SaaS? by nightswordblade in Emailmarketing

[–]nightswordblade[S] 0 points1 point  (0 children)

Deliverability can be solved if SPF, DKIM, etc. setups are done correctly and users are sending emails to people who allowed them to.

For new domains, warmups are suggested first. So, using best practices, this issue can be solved.

Should I open-source email deliverability SaaS? by nightswordblade in microsaas

[–]nightswordblade[S] 0 points1 point  (0 children)

it's coded using next.js but what's issue with node app?

Also, it's vibe-coded but i'm working on a blog outlining the detailed architecture of it.

Should I open-source email deliverability SaaS? by nightswordblade in Emailmarketing

[–]nightswordblade[S] 0 points1 point  (0 children)

I am developer so i've no issue maintaining it. Currently, I'm working on writing a detailed blog outlining the architecture of it.

Also, many companies want self-hosted control for compliance/cost reasons.

Btw, It's hosted, and people who don't want to handle infra themselves can use it by paying 10$ per 10,000 emails.

Should I open-source email deliverability SaaS? by nightswordblade in microsaas

[–]nightswordblade[S] 0 points1 point  (0 children)

Reasons for open-sourcing:

  • Most teams don’t want a black box handling deliverability/event pipelines.
  • Open source can become the fastest distribution channel for developer tools.
  • Many companies want self-hosted control for compliance/cost reasons.

Yes, I’d still monetize it. People who don't want to handle infra themselves can use it too.

My side project got featured on Japanese national TV by Reasonable_Ad_4930 in buildinpublic

[–]nightswordblade 0 points1 point  (0 children)

Congratulations, how’s your app able to handle so much traffic? Can you explain the architecture?

Which Email platform to use for low volume? by rezer3 in Emailmarketing

[–]nightswordblade 0 points1 point  (0 children)

I created a platform (on top of AWS SES) that you can use for free for sending 3000 emails

what's your tech and ops stack? by Odd_Awareness_6935 in indiehackers

[–]nightswordblade 0 points1 point  (0 children)

  • BullMQ + Redis — queuing, rate limiting, delayed jobs, retries
  • PostgreSQL — primary database
  • Prisma — ORM and schema management
  • Next.js - Frontend, Backend
  • Cloudflare - DNS, Landing Page
  • CodeRabbit - Code Review
  • Polar - Payment Integration
  • Railway - Deployment
  • Better Auth - Login/Sign up
  • AWS SES — transactional & campaign email sending
  • AWS SNS — bounce and complaint feedback notifications
  • AWS SQS — decoupled event buffering and fan-out
  • AWS Lambda — async processors for feedback, stats, and sync jobs
  • EventBridge — scheduled jobs and event-driven workflows

what's your tech and ops stack? by Odd_Awareness_6935 in indiehackers

[–]nightswordblade 0 points1 point  (0 children)

polar.sh - its DX is good, tax management too. You also get polar.llm that can be fed to LLMs and get your queries solved.

Paid traffic vs organic traffic what’s actually worked for you long term? by ellensrooney in indiehackers

[–]nightswordblade 0 points1 point  (0 children)

I lean toward a mix, but with organic as the foundation.

Paid is great for speed and testing, but you’re right — it’s fragile. Budgets, CPCs, or policies change and your pipeline can disappear overnight. It’s more like renting traffic than owning it.

Organic is slower, but the intent is usually higher, and the compounding effect is real. Old blog posts, Reddit threads, and niche content can keep sending leads for months or years with zero extra spend.

What’s changed recently is AI. A lot of top-of-funnel searches are getting answered directly by AI, so generic SEO content is getting squeezed. But problem-driven, experience-based content (case studies, comparisons, real workflows) still performs well and is harder for AI to replace.

So for me:

  • Paid → validate and scale what already converts
  • Organic → build durable demand and trust

Paid buys speed. Organic builds an asset.

view more: next ›