Michał Ordon
62d7c44efc
* feat: add REDIS_KEY_PREFIX env var for Redis ACL namespace isolation Adds optional REDIS_KEY_PREFIX env var that prefixes all Redis keys (BullMQ queues via `prefix` option, cache/lock/rate-limit keys via `redisKey()` helper). When unset, behavior is unchanged (BullMQ defaults to "bull:", cache keys are unprefixed). This enables self-hosters using Redis ACL multi-tenancy to restrict useSend to its own key namespace (e.g. `~usesend:*`). 16 files changed across env schema, Redis module, 9 BullMQ queue/worker files, and 5 direct Redis key operation sites. * docs: add REDIS_KEY_PREFIX to self-host assets and fix docker run example Add REDIS_KEY_PREFIX env var to docker/prod/compose.yml, .env.example, .env.selfhost.example, and self-hosting docs. Fix missing trailing backslashes in standalone docker run example. * fix(redis): disable ioredis ready check and BullMQ version check Redis ACL blocks INFO command (in @dangerous category). ioredis uses INFO for ready check, BullMQ uses it for version detection. Without these flags, BullMQ workers fail to initialize and silently stop processing jobs. - Add enableReadyCheck: false to ioredis connection - Add skipVersionCheck: true to all 5 Queue + 5 Worker constructors * fix(redis): add skipVersionCheck to remaining BullMQ job queues Add skipVersionCheck: true to Queue and Worker constructors in all 4 job files (campaign-scheduler, cleanup-email-bodies, usage-job, webhook-cleanup) to match the pattern already used in service files. This prevents BullMQ version mismatch errors when using REDIS_KEY_PREFIX with Redis ACL namespace isolation.
The Open Source sending infrastructure.
Learn more »
Discord
.
Website
·
Issues
About this project
As most of email products out there, useSend also uses Amazon SES under the hood to send emails. We provide an open and alternative way to send emails reliably and cheaply with a great dashboard. You can also use useSend manage contacts and send bulk emails(newsletter, product updates etc). We will take care of the subscriptions.
Currently we only support emails, but we plan to expand to other sending protocols like SMS, push notification and even whatsapp.
We are currently in beta!
Features
- Add domains
- Transactional Mails
- Rest API
- Dashboard (Delivered, opened, clicked, bounced)
- Marketing email
- SMTP support
- Schedule API
- Webhook support
- BYO AWS credentials
Community and Next Steps 🎯
We're currently working on opening useSend for public beta.
- Check out the first source code release in this repository and test it.
- Tell us what you think in the Discussions.
- Join the Discord server for any questions and getting to know to other community members.
- ⭐ the repository to help us raise awareness.
- Spread the word on Twitter.
- Fix or create issues, that are needed for the first production release.
Tech Stack
- Next.js - Framework
- Prisma - ORM
- Tailwind - CSS
- shadcn/ui - Component Library
- NextAuth.js - Authentication
- tRPC - API
- hono - Public API
- Redis - Queue
Email editor
Check out the editor code for here. Editor is possible only because of the amazing tools and libraries.
- jsx-email - converts editor content to html
- maily.to - useSend email editor is greatly inspired from maily.to
- tiptap - editor core
Local Development
Follow our detailed guide to run useSend locally
https://docs.usesend.com/get-started/local
Docker
We provide a Docker container for useSend, which is published on both DockerHub and GitHub Container Registry.
DockerHub: https://hub.docker.com/r/usesend/usesend
GitHub Container Registry: https://ghcr.io/usesend/usesend
You can pull the Docker image from either of these registries and run it with your preferred container hosting provider.
Please note that you will need to provide environment variables for connecting to the database, redis, aws and so forth.
For detailed instructions on how to configure and run the Docker container, please refer to the Docker Docker README in the docker directory.
Self Hosting
Checkout the self-hosting guide to learn how to run useSend on your own infrastructure.
Self Hosting with Railway
Railway provides the quickest way to spin up useSend. Read the Railway self-hosting guide or deploy directly:
Star History
Sponsors
We are grateful for the support of our sponsors.
Other Sponsors
