Hello, indiehackers!
I want to introduce you to sentfrom.io, an email platform that enables developers to send emails from their customers' domains. We're still building the platform, but we'd love to hear your feedback and thoughts in the meantime!
After trying to implement custom sending identifies into an existing product, we found that the existing email infrastructure products didn't facilitate this functionality - so we've set out to change that.
Your customers' branding is important to them - so why not empower your platform to send your emails with their domain?
How are we going to solve this problem?
We want our product to integrate with all platforms, to ensure that you can keep an in-app experience.
With our API, you'll be able to add custom domains with a single request. After adding this domain, we'll tell you what DNS records your customer will need to add to enable you to send emails. Once that's complete, we'll let you know and you'll be able to send your existing emails with the domain!
Have a look at our landing page for a code snippet example.
How can I help while you build the product?
Any feedback is appreciated, but if you're really keen to try the product - feel free to purchase the product now on the website! (We'll give you 30% for the first month)
As we're still building our product, we want to make sure we get it right. Our promise is that, if you're not happy with the product or change your mind we'll give you a full refund - no questions asked.
Interesting idea. Isn't verifying an email via a verification link easier for customers? What Amazon SES offers.
I'm pretty sure it's better to verify the domain via DNS, but for some customers that can be complicated.
https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html
You're right, verifying with an email would be easier! But as you've already agreed, it's not the best method. It's definitely can be a complicated process to add these records, and for most, it's not something they might manage. Our goal is to try to simplify this process as much as possible for the customer, and over the long term would like to build integrations with the common DNS providers so that they can "Login with GoDaddy" and get prompted to add the records.
Using AWS SES identities would be exactly how I would go about it without something like SentFrom, it'd be able to complete the task. I use Amazon SES currently for a few other projects, and I get about 5% of daily emails getting flagged as SPAM. The DMARC reports always show the same thing as the AWS SES Sending Server IP being on a blacklist from other customers. This could definitely be resolved with a dedicated IP, but just not the best experience (Likely also a bit of bias here!)
Checked our Tolt, and it's a really good idea! I look forward to the upcoming launch.
Totally makes sense. The "Login with GoDaddy" feature would be great! I've seen some apps have integrations with domain registers like that, and it really helps in UI!
Thanks for checking out Tolt, really appreciate it!
The landing page is pretty good. I feel like it's missing a footer, the end of the page just sort of awkwardly ends with "our promise". Subjective, but it does feel like something was left out.
Thank you for the feedback!
You're absolutely correct, it was needed - have now added one in :)
Would this require any DNS changes for the domain? If not, how do you prevent emails from going to junk or spam?
Yes, this would require DNS changes to ensure that ensure emails are delivered. When you add your customers' domain via the API, you will receive the records that the customer will need to add. We will then tell you either over a webhook, or API check to inform you of the status of the verification. Once complete you'd then be able to send emails with that domain!