The Deployer documentation
Getting started

Creating an account & signing in

Your Deployer account keeps your projects, connected accounts, and deployments in one place. Signing up takes a minute: continue with Google or GitHub, or use an email address and a password. This page walks you through creating an account, the ways to sign in, verifying your email, and resetting a forgotten password.

Continue with Google or GitHub

The quickest way in. On the log-in or sign-up screen, choose Continue with Google or Continue with GitHub, approve the request on their page, and you are signed in. If you have no account yet, this makes one. It reads only your name and a verified email address from Google or GitHub: signing in never gives The Deployer access to your repositories. (Connecting a repository host is a separate, explicit step on Connections.)

An account made this way has no password. It does not need one to sign in, but a few things ask for a password as an extra check (viewing or replacing a saved credential, creating an API key). Choose Set a password on your Profile page and we email you a link.

Already have an account with that email?

Then you are asked to sign in the way you did before, and connect Google or GitHub from your Profile page. We do not attach a Google or GitHub account to an existing account just because the email address matches: an account that holds your cloud credentials deserves more proof than that. Connecting one from Profile asks for your password, and your authenticator code if you use one, because a connected account can sign in without your password.

Connect or remove a sign-in method

Profile shows Sign-in methods: the Google and GitHub accounts that can sign in to this account, with Connect Google and Connect GitHub to add one and a bin to remove one. The connected account's email address does not have to match yours. You can't remove the only way you have of signing in.

If you reset your password

A password reset also disconnects the Google and GitHub accounts connected to the account, because a reset is what you do when you suspect someone else got in, and a connected account is a way in that survives a new password. Connect the ones you want again from Profile.

If you use an authenticator app

Signing in with Google or GitHub still asks for your six-digit code afterwards. Google and GitHub prove who owns your inbox; the code proves you hold your phone.

Create an account with a password

  1. Open The Deployer. On the welcome screen, choose Create an account.
  2. Enter your name (this is just how we greet you).
  3. Enter your email address — use one you can check, since we may send a confirmation link.
  4. Choose a strong password and type it again to confirm.
  5. Click Create account.

The strong-password requirement

For your security, new passwords must be strong enough. As you type, the app shows a live strength indicator so you can tell when your password is good to go. A few simple tips:

  • Make it reasonably long.
  • Mix upper- and lower-case letters, numbers, and symbols.
  • Avoid obvious words, your email, or things like password123.

If the password isn't strong enough, the Create account button stays disabled until it is.

Verify your email (if required)

Depending on how your copy of The Deployer is set up, you may need to confirm your email before you can log in.

  1. After signing up, you'll see a "Check your inbox" screen.
  2. Open the email we sent and click the verification link.
  3. Return to The Deployer and log in.

Didn't get the email? First check your spam or junk folder. You can also click Resend verification email from the "Check your inbox" screen. If you try to log in before verifying, the app will let you know and offer a resend link right there.

If email verification is turned off in your setup, you'll be logged in straight after signing up — no inbox step needed.

Log in

  1. On the welcome screen, choose Log in (or "Already have an account? Log in").
  2. Enter your email and password.
  3. Click Log in. You'll land on your Projects page.

If your password is refused

After four wrong passwords in a row, that device can't try your account again for 15 minutes — even with the right password. It stops someone guessing their way in. Waiting it out works, and so does resetting your password with the link below.

Two-factor sign-in

Once your account is connected to a cloud provider or a code host, signing in takes a six-digit code from your phone as well as your password. Your password now protects the ability to spend money in your cloud account and read your private repositories, and a password on its own is one thing to lose.

The same applies to everyone in a shared workspace, because a team member works with the same connected accounts the owner does.

Setting it up

You'll be taken to the setup screen the first time you sign in after connecting something. It takes about a minute:

  1. Open an authenticator app on your phone. Google Authenticator, 1Password, Bitwarden and Authy all work.
  2. Choose add an account and scan the QR code on screen.
  3. Give the device a name, type the code your app is showing, and click Turn it on.

Can't scan it? Click Can't scan it? Enter a setup key instead and type the key by hand. If you're reading this on the same phone, tap add to authenticator app and it fills everything in.

Nothing is switched on until that code matches, so you can't lock yourself out during setup.

You can also set it up any time from Profile, before you connect anything.

Your registered device

Profile shows which authenticator is registered, what you named it, when you added it and when it last signed you in. Rename changes the name.

Getting a new phone

Click Change device on Profile. It asks for your password and a code, then shows a new QR code to scan with the new app.

The authenticator you have now keeps working right up until the new one is proved, so there's never a moment where you can't sign in. Your recovery codes aren't affected either, so the set you saved stays valid.

Already lost the old phone? A recovery code works in place of the current code, which is exactly what they're for. This works even on accounts that aren't allowed to turn two-factor off.

Recovery codes

When you turn it on you get eight recovery codes. Save them somewhere that isn't your phone. Copy them or download them as a file. Each one signs you in once, and that's what gets you back in if you lose the device.

They're shown only once, because we store nothing that can recreate them. Profile tells you how many you have left, and you can issue a fresh set whenever you like, which retires the old ones.

Lost your phone and your recovery codes? Email us and we'll verify who you are.

Turning it off

While your account is connected to a cloud provider or a code host, two-factor sign-in stays on. Disconnect those first if you want to turn it off. Changing to a different phone or app is always available, connected or not.

Either way, turning it off asks for your password and a current code, because a logged-in browser is exactly what someone who got that far would already have.

Reset a forgotten password

Locked out? No problem.

  1. On the login screen, click Forgot password?.
  2. Enter your account email and click Send reset link.
  3. Open the email we send and click the link to choose a new password (it must meet the same strong-password rule above).
  4. Log in with your new password.

For privacy, the app gives the same friendly confirmation whether or not an account exists for that email — so a stranger can't use this to discover who's registered. Just check the inbox for the address you entered.

A note on your privacy

Your login protects your projects and, importantly, your connected cloud and GitHub accounts. The Deployer encrypts your credentials, and cloud credentials are used by the deployment engine rather than placed in AI prompts. Once you're in, head to Connecting your accounts to link GitHub and a cloud provider, or jump straight to the Quick start.