5 ms·

Nice that somebody is finally offering this as an service. But the service is full of deal-breakers (for me at least): > Any given email address can only be ve

Nice that somebody is finally offering this as an service. But the service is full of deal-breakers (for me at least): > Any given email address can only be verified a certain number of times each month. How many times? > If you subscribe to emauth pro for $4/month, you can make 512 verifications per month 512 verifications for $4/month is a big ask. Auth0 and Firebase have bigger free tiers, not 100% sure though. > If you need more verifications than this (for example if you want to use emauth for a public app with many users), please contact sales at sales ... Before you start enterprise sales, some options which are bigger than 512 would be great and I am also not sure if this type of smaller service would justify any enterprise sales. However, let us know if anyone contacted you for some enterprise-y deals. > Also, in order to protect the email sender reputation for emauth, we aggressively blacklist ip addresses that repeatedly make requests to invalid email addresses. Makes sense but how long are these IP blacklisted? How many requests are required to blacklist an IP? Btw, this won't help OPs email reputation, just few dozens of bounces are required to get your domain on many blacklists. How did other people solved this problem? How did Medium worked around this problem in its early days? Biggest problem though: Integrating something like your service is easy but building processes around creates a light lock-in and getting the stuff out again is some work. Looking at your landing page which I like because it's light and subtle, it still gives the feeling that it's hobby project and nobody knows if you are still on the market next month or next year. Smaller problem: No custom domain possible (or is it?), so customer might miss that your email belongs to my service.

anderspitman 7y ago
Thanks for the feedback >> Any given email address can only be verified a certain number of times each month. > How many times? Currently 10. It's a mostly arbitrary number intended to be enough for adding simple authentication to things like family photo albums, where infrequent logins and longlived tokens are more acceptable. >> If you subscribe to emauth pro for $4/month, you can make 512 verifications per month > 512 verifications for $4/month is a big ask. Auth0 and Firebase have bigger free tiers, not 100% sure though. 512 is a complete shot in the dark. The unfortunate truth is there's no way to get a feel for a good number until you measure usage and/or get feedback. And no one is going to give you feedback until you hit the front page so... >> If you need more verifications than this (for example if you want to use emauth for a public app with many users), please contact sales at sales ... > Before you start enterprise sales, some options which are bigger than 512 would be great and I am also not sure if this type of smaller service would justify any enterprise sales. However, let us know if anyone contacted you for some enterprise-y deals. Don't disagree. But I have no data to make tiering decisions from and wanted to have at least some paid option right away. >> Also, in order to protect the email sender reputation for emauth, we aggressively blacklist ip addresses that repeatedly make requests to invalid email addresses. > Btw, this won't help OPs email reputation, just few dozens of bounces are required to get your domain on many blacklists. That's good to know, thanks. > Integrating something like your service is easy but building processes around creates a light lock-in and getting the stuff out again is some work. Looking at your landing page which I like because it's light and subtle, it still gives the feeling that it's hobby project and nobody knows if you are still on the market next month or next year. I'm no fan of vendor lock-in, believe me. I never would have made this if I didn't need it for my other products and services. Worst case maybe the free tier is useful for a few people. The service is trivial enough that you can implement your own fairly easily. I'm sure it's already been implemented a million times. And if it comes down to me no longer being able to run the service for some reason, I'll open source it. > No custom domain possible (or is it?), so customer might miss that your email belongs to my service. Not currently. You can customize the email text a bit to make it clear where the email originated from.

anderspitman 7y ago

Thanks for the feedback >> Any given email address can only be verified a certain number of times each month. > How many times? Currently 10. It's a mostly arbitrary number intended to be enough for adding simple authentication to things like family photo albums, where infrequent logins and longlived tokens are more acceptable. >> If you subscribe to emauth pro for $4/month, you can make 512 verifications per month > 512 verifications for $4/month is a big ask. Auth0 and Firebase have bigger free tiers, not 100% sure though. 512 is a complete shot in the dark. The unfortunate truth is there's no way to get a feel for a good number until you measure usage and/or get feedback. And no one is going to give you feedback until you hit the front page so... >> If you need more verifications than this (for example if you want to use emauth for a public app with many users), please contact sales at sales ... > Before you start enterprise sales, some options which are bigger than 512 would be great and I am also not sure if this type of smaller service would justify any enterprise sales. However, let us know if anyone contacted you for some enterprise-y deals. Don't disagree. But I have no data to make tiering decisions from and wanted to have at least some paid option right away. >> Also, in order to protect the email sender reputation for emauth, we aggressively blacklist ip addresses that repeatedly make requests to invalid email addresses. > Btw, this won't help OPs email reputation, just few dozens of bounces are required to get your domain on many blacklists. That's good to know, thanks. > Integrating something like your service is easy but building processes around creates a light lock-in and getting the stuff out again is some work. Looking at your landing page which I like because it's light and subtle, it still gives the feeling that it's hobby project and nobody knows if you are still on the market next month or next year. I'm no fan of vendor lock-in, believe me. I never would have made this if I didn't need it for my other products and services. Worst case maybe the free tier is useful for a few people. The service is trivial enough that you can implement your own fairly easily. I'm sure it's already been implemented a million times. And if it comes down to me no longer being able to run the service for some reason, I'll open source it. > No custom domain possible (or is it?), so customer might miss that your email belongs to my service. Not currently. You can customize the email text a bit to make it clear where the email originated from.