Frequently Asked Questions

We have built Login.sh under highest security standards, so all your data remains secure. Also, our application is running on infrastructure certified with security certifications like ISO 27001, 27017 and 27018, and SOC 1, 2 and 3.

We also enforce full encryption in all in/out communications, and access to all company data (including public keys distributed over your infrastructure), is made through authenticated endpoints.

We are running on Erlang/Elixir, which ensures that our core is prepared for demanding concurrency levels. We use managed infrastructure in one of the best providers available, so your public keys will be available whenever you request it.

Short answer: yes!

Long answer: You can use our web interface from any device that runs a browser. Also, we provide public keys in OpenSSH format, so you can use it wherever you have an SSH server and an Internet connection.

We believe we provide enough security measures to provide this kind of service, so we recommend automatic deployment of authorized public keys when available (docs).

However, if you don’t feel comfortable with automatic deployments and you want to do them on-demand, you can do that way easily. It just won’t update the authorized keys automatically after a change.

Sure you can! We are currently offering integration over an HTTPS authenticated endpoint, so you can integrate it anywhere you want.

We are working on some plugins and libraries for well-known ops tools like Ansible or Capistrano, so stay tuned!

It means that we are still testing some features and preparing some improvements until we reach the stable release.

Until we get out of the Beta the service is free to use, and we promise that there will be a generous free plan for solo-developers and small teams.