Getting started

Everything on Odel ends the same way: a URL you paste into an AI client. What differs is what sits behind it and how you got there. This page covers the part that comes first.

An account, by invitation for now

Sign-up is gated during the beta. If your email isn't on the list, creating an account sends you to the waitlist instead — name, email, and optionally what you'd want to build.

Once you're through, sign up with an email and password, or continue with Google, Apple, or GitHub. Using a provider doesn't give Odel access to anything of yours; it only proves who you are. Connecting a GitHub repository later, so Odel can build your code, is a separate decision made in the developer portal.

An organization, made for you

Odel doesn't hang things off user accounts. Modules, gateways, and secrets are owned by an organization, and your account comes with one the moment it's created — named after your username, owned by you, and permanently single-member.

That's why you'll see an organization selector on surfaces that look personal. Your own things live in your personal organization; anything meant for other people lives in a team organization you create separately. Which one is active decides whether you can add a third-party server as the organization's gateway — installing one for yourself always lands in your personal organization — and which vault a secret comes from.

Then one of three things

What you never have to do

No client ID to obtain, no client secret to store, and no API key pasted next to an Odel URL in a config file. A module's own credentials are configured once on Odel and injected when it runs, so they never reach your client, your shell history, or a file you might commit.

If a setup guide anywhere asks you to put a secret beside an Odel URL, something has gone wrong — connecting your client explains why there's nothing to paste.