11–20 of 105 posts
If you send through Cloudflare Workers using MailChannels, the sending is free with no cap.
Especially in startups, this is super annoying process. Say I want to test out a feature with 100 random users who have done XYZ before. Right now I have to do a SQL query, export that to a CSV, import to MailChimp, send.
I see a lot of security concerns with this. Many, if not all databases are not public accessible, nor should they ever be. Asking people to open their database up to you, sketchy and dangerous.
Earlier quoted context omitted.
Very legitimate concern and one I've been thinking about a lot. Honestly, I think the best way to address this is to just go open source, which I'm totally open to. I think once I've validated the idea a bit and know it's something people are interested in, I'll focus on this issue and come up with a solution (whether it's open sourcing or something else)
Going open source will not solve your problems. The issue is that youre asking customers to open database access to you/your company. The reason why the method youve chosen isnt already out there is because of all the implications it has. You better have one hell of a security team to ensure youre locked down tighter than a ducks ass. Look at how many data breaches there have been, even in the past year. The solution…
Having said that, it's totally understandable that some orgs won't want do open up their db. The idea with going open source would be that they can host the platform in their VPC so that their data is never leaving the premises.
Not against having an SDK or API at all, but I would need to think about would work because the whole syncing issue is one that I'm focused on addressing here.
If you send through Cloudflare Workers using MailChannels, the sending is free with no cap.
Woah cool! I actually hadn't heard of this. Would be cool if I can integrate this into the platform. Been thinking of adding other backends like Sendgrid and Resend.
https://support.mailchannels.com/hc/en-us/articles/456589835...
Could you explain why this was such a problem?
It would seem like this (API to submit data) is the sensible way to balance the cost against the security concerns raised in the other comment.
Does mean engineering and sync issues which your solution does address in an interesting way.
Earlier quoted context omitted.
Going open source will not solve your problems. The issue is that youre asking customers to open database access to you/your company. The reason why the method youve chosen isnt already out there is because of all the implications it has. You better have one hell of a security team to ensure youre locked down tighter than a ducks ass. Look at how many data breaches there have been, even in the past year. The solution…
Definitely taking all the security measures I can, but you're right, things can go wrong. I do encourage (and would like to enforce) that db credentials provided should have very limited read access to only the tables/columns that the user wants to query. Having said that, it's totally understandable that some orgs won't want do open up their db. The idea with going open source would be that they can host the platfor…
That being said, self hosting doesnt solve all issues.
You, and whoever uses this product, will need MANY IPs because of blacklisting and throttling limits applied almost worldwide to all mail servers. Theres a reason why the marketing spam hosts have their own /24 or /25 and have 80% of them cycling through usage as a mail sender.
Im not knocking your want to have something better than MailChimp and the like, but i feel like you didnt really dig into the real underlying tech and security before you went to work on this.