Creating your account

Signing up#

Go to cloudpilot.in and register. You can use:

• Email and password, or
• Google, or
• GitHub.

Signing up creates your organisation as well as your account, and makes you its Owner.

If you were invited by someone else, use the link in your invite email instead — that puts you in their organisation with the role they chose. Signing up separately would create a new, empty organisation of your own, which is a common first-day mistake.

Verifying your email#

Email sign-ups get a verification link. Verify before you rely on the account: password resets and security notifications go to that address.

If it has not arrived, check spam, then use the resend option on the login page.

Signing in from a new device#

When you log in from a device CloudPilot has not seen before, it emails you a code and asks for it. Existing devices are not challenged every time.

This is why a working email address matters. If you have lost access to the inbox, a new device cannot be verified.

Signing in with an SSH key#

CloudPilot also supports signing in with an SSH key instead of a password. You add a public key to your account, and at login CloudPilot gives your browser a challenge that only the matching private key can sign.

It is worth setting up if you already manage SSH keys: there is no password to phish, and revoking a key ends that route immediately.

Add and revoke keys from your profile.

Forgotten password#

Use Forgot password on the login page. The reset link goes to your registered email and expires — request a new one rather than reusing an old link.

If you signed up with Google or GitHub, you do not have a password. Sign in the same way you signed up.

Staying signed in#

Sessions refresh in the background, so you are not asked to log in constantly. Sessions are revocable: signing out ends that session rather than leaving a token valid until it expires on its own.

Next#

• Core concepts — what an organisation, server and project actually are
• Quickstart — connect a server