simple-login

This version is more complete and contains more technical details on our decision: https://simplelogin.io/blog/we-left-aws/

The ses pricing does not match our pricing unfortunately. We do give instructions on how to use SimpleLogin with SES in our doc at https://github.com/simple-login/app/blob/master/docs/ses.md though.

Absolutely! We also feared that it’s going to be hard to scale without all the aws features like rds, load balancer, s3, etc but we discovered better & easier to use tools for each need since we left Aws.

We have studied that option but the price exceeds an early, bootstrapped startup budget unfortunately.

Another feature of SimpleLogin is self-hosting and we don’t want to be dependent on a specific cloud.

The database does not have high i/o need and we don’t store much data so a self managing a database is doable.

ses pricing is not sustainable for our pricing model that offers unlimited forwards/replies.

We should have pointed this out in the article. Btw we know pretty well aws.

SimpleLogin team here, this is actually another error due to the bounce email (note the <>). Do you remember where you created this alias? Would be great if you can send us details to hi@simplelogin.io or open up an issue on Github. Thanks!

Disclaimer: I'm the founder of this service.

I wouldn't trust a closed-source solution to be the privacy-focused identity provider. And with "Apple Search Ads", Apple could also be considered as an advertising company.

I have actually started out to create a privacy-focused SSO solution named "Sign In with SimpleLogin" [1] before "Sign in with Apple" was announced. The solution is from the beginning meant to be open source and even self-hostable. It's superior than "Sign in with Apple" in several ways:

- The dev experiences is far better

- The random email part is customized

- Name, avatar could also be customized

If you visit the home page, you would notice that it's talking mainly about the email alias part as the SimpleLogin button is not implemented on popular websites yet, which hopefully will come soon.

[1]: https://simplelogin.io/developer

True. As soon as we start receiving spams on an email address, we would know immediately which website has sold our email address.

Good question! There are 2 reasons that you can count on SimpleLogin:

- The running cost is low enough for us to keep the service running almost "forever". Even when SimpleLogin doesn't earn enough money to pay our salaries (the biggest cost), we'll keep SimpleLogin running as a side-project as we and a lot of our family/friends use SimpleLogin.

- The code and hosting instructions are open so anyone could deploy SimpleLogin on their server and migrate all their aliases there. The migration is actually not too complex as it mostly consists of changing the DNS and re-import your existing aliases. Making sure that SimpleLogin can run on an inexpensive and simple server is part of our design rules since the beginning so you don't need complex infrastructure to deploy SimpleLogin for yourself.

> Do you have any plans on how to sustain in the long-term?

Our revenue comes mainly from the premium subscription. We are also considering to create products derived from SimpleLogin technology but targeted at business.

Thanks for letting us know. We just made some changes in our email server IP, the emails should not be put in Spam now.