Installing Orakul

Installing Orakul takes no special skills. You don't need to configure nginx, certificates or a database — the installer does all of that. Your part is to rent a server, paste one command into the console, accept the agreements and answer three questions in the browser. If something goes wrong, write to us using the form at the bottom of this page. We answer and, if needed, finish the install ourselves: it's part of the deployment and costs nothing extra.

What to have ready

• A server running Ubuntu: 2 cores, 4 GB of memory, 40 GB of disk. That's enough for a team of agents.
• A domain for the panel, with an A record already pointing at the server's IP — the HTTPS certificate is issued for it.
• Your Orakul license key, which we issue at purchase.
• Three access keys: a Telegram bot token, a Google Gemini key and your Telegram ID. Any of them can be left empty and filled in from the panel later — the install won't stop because of it.

Step 1. The server

Any provider with Ubuntu will do. The screenshot shows Hetzner: a CX23 plan (2 vCPU, 4 GB, 40 GB SSD), an Ubuntu image, IPv4 and IPv6. That's about €6 a month.

Add your SSH key when creating the server — then you get into the console without a password. No key? The provider's web console works too.

The minimum configuration: 2 cores, 4 GB of memory, 40 GB of disk

Step 2. Download the installer

Connect to the server over SSH as root and download the script:

wget -O install.sh https://orakul.digital/install.sh

A small file — it downloads instantly

Step 3. Run it with your license key

Run the script and pass it your key:

sudo bash install.sh ORK-XX-000000-XXXXXXXX-XXXXX

The script checks the key, downloads the distribution and prints a link — everything after that happens in the browser. The link is single-use and valid for this install only, so open it on your own computer.

The key and the one-time link are different for every install

Step 4. Accept the agreements

The wizard has six screens, and the first three are documents: the license (EULA), the data processing agreement (DPA) and the standard contractual clauses (SCC). The full text of each is right there in the window, next to the licence key it is accepted for, and the "Next" button stays shut until the checkbox is ticked.

Every acceptance is recorded: the date and time (UTC), your IP address, the key and the version of the text. The same documents are always on the site — the links above and in the footer — so you can read them beforehand instead of mid-install.

The DPA applies where we process personal data on your behalf: support, diagnostics, deployment. The SCC apply only where such data is transferred out of the EEA, the UK or Switzerland — accepting them now means the terms are in place if that ever happens.

Step 1 of 6 — the license (EULA)

Step 2 of 6 — data processing (DPA)

Step 3 of 6 — international data transfers (SCC)

Step 5. Panel language and time zone

The fourth wizard screen. The language you pick is the language of the panel and of reports; you can switch it later. The time zone matters more than it looks: schedules run by it, so "every Monday at 9:00" means nine in the morning where you are.

Step 4 of 6

Step 6. The panel domain

Enter the domain the panel will open at and an email for Let's Encrypt — certificate expiry notices go there. The domain's A record must point at the server's IP before this step: the certificate is issued during the install, and without the record it can't be.

Step 5 of 6

Step 7. Access keys

Three fields, each with a link to where the value comes from:

• Telegram bot token. Send /newbot to @BotFather — it replies with the token.
• Google Gemini key. Created in Google AI Studio; the agents run on it.
• Your Telegram ID. Send any message to @userinfobot — it replies with a number. It's what lets the bot answer you and gives you panel access.

Any field can stay empty: the install goes through and you add the key from the panel later.

Step 6 of 6 — the install itself starts after this

Step 8. Wait 10–20 minutes

The installer sets up packages, browsers and the database, showing the log as it goes. You can minimise the window — the process runs on the server and won't be interrupted.

But do not close the browser window. The admin password is shown at the end on this very page and nowhere else: close the tab and the password is gone. Minimise it, switch to other tabs, go do something else — just don't close it.

The log is visible right on the page; keep the tab open until the install finishes

Done

At the end the wizard shows the panel address, the login admin and a password. Save the password right away — the page closes 10 minutes after the install finishes. It also reminds you to delete the answers file, which still holds your keys:

rm /opt/orakul-dist/deploy/install.env

The Telegram bot replies as soon as you send it your first message.

The password is generated during the install — this one is long dead

First run: finding your way around

Open the panel at the address from the final screen — the login is admin and the password is there too. You won't have to figure it out alone: on the first login the panel shows which agents already come installed.

• Orakul Help (@help) — help with the panel itself: setup, keys, building agents, errors.
• Assistant (@assistant) — general questions and anything no other agent fits.
• Prompt Builder (@prompt_builder) — writes the system prompt for a new role: asks clarifying questions and hands back ready text.

Shown once per browser; the button opens a chat with the help agent straight away

The "Ask Orakul Help" button opens the chat with the question "What can you do?" already asked — and the agent answers with a map of the system: where to get keys and where to paste them, how to create an agent through "Subagents → Hire a specialist", how to give your staff access, and how to put a task on a schedule. It's faster than hunting through the interface: the agent knows this panel and answers about it, not in generalities.

The help agent answers for your own installation, naming the actual panel sections

A sensible first hour: ask @help what it can do; fill in any missing keys under "API Keys"; build your first agent for a real task with Prompt Builder; give it that task in the chat and look at the result. By then the shape of the system is clear, and the rest of the setup follows your own processes.

If the installation failed

It happens: a provider serves a broken package, the domain hasn't propagated through DNS yet, the disk runs out. In that case the wizard shows a screen with the log and the buttons "Copy log" and "Download full log".

There's no need to reinstall anything. Most steps have usually completed already, so the install can be resumed where it stopped rather than started over. Copy the log and send it to us with the form below — we'll work out what happened and tell you what to do next.

"Copy log" puts the whole log on the clipboard