Show HN: Loopletter: Open-source email marketing platform
Show HN (score: 6)Description
What’s inside:
- Full campaign builder (visual editor, reusable templates, optional Spotify-powered layouts)
- Audience management tooling (imports, segmentation, consent workflows, list cleanup)
- Queue-driven sending with AWS SES, BullMQ, and Redis — handles rate limits, retries, and
deliverability feedback
- Analytics dashboards with real-time metrics, campaign history, and basic attribution
- Infrastructure scripts for Supabase, AWS EventBridge/Lambda, and Upstash Redis so you can set
everything up from scratch
Tech stack: Next.js, React 19, TypeScript, Tailwind, Clerk for auth, Supabase (Postgres)
for storage, AWS SES + S3 for mail/asset delivery. The repo has docs, scripts, and a demo data
sandbox because we know email platforms can be boring to set up without real content.
Why open-source? Most tools in this space are either huge enterprise SaaS products or
very marketing/sales oriented. Independent artists have different needs (merch drops, tour
announcements, limited release windows) and usually lean on social platforms they don’t control.
Email still converts best for them, but standing up a full stack is painful. We’d love to see
small labels, agencies, and indie devs fork it, run it for their communities, or contribute
features.
I'm especially curious if this has potential to be something bigger.
Repo link: https://github.com/createdbymax/Loopletter-Open-source-email-marketing-platform
Production website: https://loopletter.co/
Happy to answer questions about the project, SES deliverability, or anything else related to
running email at indie scale. Thanks for taking a look!More from Show
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
No other tools from this source yet.