Sign up

Create an Eddytor Cloud account from the browser or straight from the CLI with `eddytor login`.

Signing up creates your user account, an organisation (named after your email's local part - alex@acme.com becomes alex; rename it any time), and its default workspace. You become the organisation's Admin and owner.

One email field serves both sign-in and sign-up: known addresses get a sign-in link, new addresses a confirmation email, and the response looks identical either way.

From the browser

  1. Open the Eddytor Cloud app and enter your work email.
  2. Check your inbox for "Confirm your Eddytor account" and open the link. The link is valid for 24 hours and single-use; requesting another is throttled to once per minute.
  3. Click the confirmation button on the page that opens - you land in the app signed in.

From the CLI

The CLI's OAuth device flow can complete sign-up too - you never need to visit the app first:

eddytor login
  1. The CLI prints a verification URL and an 8-character device code like WDJB-MJHT, and opens your browser to the approval page (code pre-filled).
  2. Enter your work email on the approval page.
  3. New address: confirm the "Confirm your Eddytor account" email as above. That also approves the waiting CLI session - eddytor login completes on its own and prints Logged in.
  4. Existing address: you get an "Approve your Eddytor CLI sign-in" email instead; its link is valid for 10 minutes.

Heads up

eddytor login --insecure is refused - the device-flow exchange carries your refresh token, and the CLI won't send it over an unverified connection. For self-hosted instances with a private CA, use EDDYTOR_CA_BUNDLE instead.

After signing up

  • Connect a bucket - see Connect Storage. You bring your own S3 / Azure / GCS credentials; Eddytor Cloud provisions no storage.
  • Invite your team - members join with the role you choose. Invites are additive: an existing Eddytor Cloud user keeps their other memberships and gains yours.
  • Mint API keys - see API keys. Keys are bound to the organisation and workspace they were created in.

Self-hosted installations ship with self-service sign-up disabled and provision accounts through an operator - see Self-host.

On this page