One command to install, one to start, and a browser tab. This level gets Odara running on your machine and walks through the two screens you only ever see once.
Goal
Odara running locally, open in your browser at http://localhost:3002, signed in with an
admin account you created.
You'll need
- Linux (x86-64) or Windows 10/11, with a terminal you can type into.
- A browser.
- About 10 minutes, most of it the download.
No exercise files for this one.
Steps
1. Install
Linux — in a terminal:
curl -fsSL https://odara.rs/install.sh | sh
Windows — in PowerShell (not the old Command Prompt):
irm https://odara.rs/install.ps1 | iex
Both installers work in your user account — no sudo, no administrator prompt. They put
Odara under ~/.local/share/odara on Linux and %LOCALAPPDATA%\Programs\Odara on Windows,
and add the odara command to your PATH.
When they finish, they print the version they installed and the address to open.
2. Start it
Open a new terminal — the old one doesn't know about the PATH change yet — and run:
odara
Leave that terminal open: it's the Odara server, and closing it stops Odara. Then open http://localhost:3002 in your browser.
3. Accept the license
The first screen is the License Agreement for Odara Community Edition. The I Accept button only becomes active once you've scrolled to the end of the text.

4. Create the admin account
Next is Setup Admin Account. This only appears while the installation has no users at all — the account you create here is the administrator.
Fill in your name, email and a password of at least 8 characters, then Create Admin Account.

Read the yellow box before you click. There is no "forgot password" email for this account: if you lose the password, the only way back is from a terminal on the machine running Odara:
# Linux
~/.local/share/odara/bin/odarax-api --reset-admin-password [email protected]
# Windows
& "$env:LOCALAPPDATA\Programs\Odara\Odara.exe" --reset-admin-password [email protected]
That prints a new random password and exits. Put the real one in your password manager now and you'll never need it.
5. Meet the workspace
You land in the editor with a Welcome to Odara tour. Take it — it's ten short steps and it names every area of the screen. The next level covers the same ground in more depth, so skipping is fine too; you can replay it any time from your profile.

Expected result
http://localhost:3002shows the Odara editor.- The top bar shows the current project on the left and your name on the right.
- MY PIPELINES in the left panel says No saved pipelines.
Common pitfalls
odara: command not found right after installing.
The terminal you installed from started before the PATH changed. Open a new one. On Linux
the installer also prints a source … line that fixes the current terminal.
The browser says the connection was refused.
Odara isn't running — the terminal with odara in it was closed, or it exited with an error.
Start it again and read what it prints.
Port 3002 is already in use.
Something else is listening there — often a previous Odara you forgot about. Stop it. On
Linux you can also start Odara on another port with PORT=3010 odara and open that port
instead.
You see a sign-in form instead of Setup Admin Account. This installation already has users — someone set it up before you. Ask them for an account, or reset a password as shown in step 4.
What you built
Nothing yet — but everything from here happens in this browser tab, and every file path you type from now on is read by that terminal you left open.
Check yourself
One question, drawn from a larger bank. Get it right to pass.
Which terminal must stay open while you use Odara?