91–100 of 105 posts
Major problem with this is that your customers should ideally never expose their databases for public access.
Earlier quoted context omitted.
Emails are sent using your own AWS SES account, which will handle all of that. No real concern of people sending spam because they would be damaging their own SES reputation.
This is only true if you are using dedicated IPs with SES (~$30/month each). However, SES is pretty good at managing IP reputation even for the shared IP service, and I haven't had any issues in over 10 years of building systems on top of it.
If I have SES and MJML and the SQL query - why not just run this on my app server? Why pay you to hit the SES API with my markup? I don't quite get it.
- stores the templates
- selectively runs campaigns and tracks open rates etc
- create campaigns, see how many users are in there, have a safeguard before you hit "send"
- actually a nice interface.
Let's assume the "open my database to the internet" is not a dealbreaker, then this tool gets your development cost of 1-8 weeks (depends on how big the code base is) down to a 19 USD / m. Depending on where you hire / how much your time is, your opportunity cost of several thousand dollars for the feature are now much smaller.
I think there's a niche but strong case for this.
[edit: typo]
Earlier quoted context omitted.
This is only true if you are using dedicated IPs with SES (~$30/month each). However, SES is pretty good at managing IP reputation even for the shared IP service, and I haven't had any issues in over 10 years of building systems on top of it.
But have you had issues when sending SES emails to Outlook/Hotmail clients? For some reason those clients block emails coming from SES
Typically via ReturnPath. It’s basically a scam, but everyone pays for it.
However. I don't think we'd have paid for this as a SaaS service. These sorts of tools could be engineering or marketing led. We had some marketing-led tools that were fairly hands-off from engineering, but they didn't connect to our database. We happily paid for these services. However this would have been engineering led, and we'd have wanted to self-host given how it worked.
Just my 2c, but I'd either keep it engineering-targeted, open source it, and make money on support, or change tack a bit to target at the marketing folks.
And a feature request: "linting" emails. We ended up with manual checklists for things like: do all the links resolve, do they have tracking tokens, is the plaintext preview good, is there an unsubscribe link. Linting for these would be a great productivity boost.
Just want to chime in directly against the flow of negative comments re: security and say two things: 1) I too am exactly in your target audience and I'm psyched to check this out (I'm the solo tech operator of an ecom business and this will exactly scratch an itch I have) 2) I'll echo what I wrote in another comment: It is VERY HN to get concerned about exposing databases, and folks who are posting about the securit…
How hard is it to have an API with reasonable RBAC? Why does it NEED database access?