opensend.cc
The open source email platform that runs on your server
174 followers
The open source email platform that runs on your server
174 followers
opensend.cc is an open source email platform that runs on your server. It sends through your own AWS account, so your domain, your data and your sender reputation stay yours. You get a REST API and SDK, SMTP, templates, broadcasts, automations, audiences, webhooks and logs. One command installs it. No per-email pricing, no feature gates. Already on Resend? Change two lines and keep your code.
@kamal_panara Congrats on the launch, Kamal! "Every product sends email, but almost none of them own it" is a great way to put it. Good luck today! 🚀
@fedulovelena Thank you Helen!
@wahjobsonline yes it does both, sending & receiving. and it uses AWS SES, so IP reputation is handled by AWS SES. that's the main reason why we use AWS SES.
@kamal_panara OPensend walks you through that or you're on your own with AWS support?
@wahjobsonline opensend.cc has setup wizard so it walks you through the AWS SES setup.
nice product! do u have any timeline for when u'll release the paid hosted version?
@luca_ardito Cloud version is expected to be released by first week of November.
@kamal_panara thanks for the reply!
"your domain's reputation is in someone else's hands" is the line that'll actually land with anyone who's done cold outreach at volume - we send a lot of it for Dial and the shared-sender-pool anxiety is real, one other customer on the same platform burns a bad list and your deliverability takes the hit too even though you did nothing wrong. since this runs through your own AWS account, does switching over mid-campaign mean starting warmup from zero on the new sending domain, or is there a way to carry over an existing SES reputation/history if you're migrating off another provider
@galdayan
Great question, and you're right about the shared-pool problem.
Short answer: you don't start from zero if you keep your sending domain. Gmail and Outlook judge your domain mostly by the domain itself (the one your DKIM signs with), not by which provider sent the mail. So if you move the same domain to opensend.cc, the reputation you've built moves with it. SES gives you new DKIM keys, but they sign for the same domain.
What doesn't carry over is the provider-side history. A new AWS account starts in the SES sandbox, and you request production access and sending limits from AWS. Those limits grow as your account builds a clean record.
On shared pools: by default SES sends from AWS's shared IPs. Those are well policed, but they're still shared. What opensend.cc adds is a separate SES tenant per team, so one team's bad list can't pause anyone else's sending. If you want IPs nobody else uses, SES offers dedicated IPs, and its managed option warms them up for you.
Mid-campaign, I wouldn't flip everything at once:
Add the SES DKIM records next to your current ones (both work at the same time).
Shift a small share of volume first, then grow it over 1–2 weeks.
Watch bounces and complaints. SES reviews accounts at 5% bounces or 0.1% complaints, and opensend.cc suppresses bounced and complaining addresses for you.
Happy to help you plan the move for Dial.