Installing Norsk Studio

Norsk Studio is installed and run by Norsk CTL — the control plane that manages every Norsk product on a machine. CTL installs Studio, runs its containers, and takes care of TLS, sign-in and the reverse proxy for you. There is nothing to assemble by hand and no compose files to write.

The standalone Norsk Studio installer (norsk.video/studio/install) and the up.sh / down.sh scripts that came with it are retired. If you are following an older guide or blog post, use the instructions on this page instead.

Before you start

You need:

  • A Norsk licence. Licences are issued by our team, sized for what you are building — get in touch and we will sort one out.

  • A machine to run on. A Linux server (Ubuntu 22.04 / 24.04 / 26.04 LTS, Debian 12, or Oracle Linux 9), or a Mac or dev box with Docker Desktop or OrbStack running.

Install

One command installs Norsk CTL and registers Norsk Studio. Run it with nothing after it and it asks for what it needs — this machine or a server, your licence file, an admin password, and the address clients will use — then shows you the plan and waits for a yes:

curl -fsSL https://norsk.video/install/studio | bash

There is no sudo on that line. Choose server and it asks for your password when it reaches the steps that need root; choose local and it never needs one.

When it finishes, sign in at https://<your-host> as admin and launch a Studio instance from the dashboard.

If you already know the answers

Every question is also a flag, and a run that names them asks nothing. This is the form for a cloud box, a rebuild you have done before, and anything scripted — cloud-init, CI, Ansible — where there is nobody to answer prompts:

curl -fsSL https://norsk.video/install/studio \
  | sudo bash -s -- --license /path/to/license.json --admin-password '<8+ chars, 1 digit>'

Add --local (and drop the sudo) to install on a Mac or a dev laptop instead of a server. --help lists every flag and works in the piped form above.

The questions only ever appear for a bare run with a terminal attached. Under cloud-init, CI, or anywhere else with nobody to answer, the install skips them and stops immediately naming the flag it is missing, rather than waiting on input that cannot arrive.

Going further

Norsk CTL owns the install journey, and its documentation covers the parts that vary by environment — laptop installs, cloud hosts, real TLS certificates, moving off ports 443 and 80, running behind another reverse proxy, and upgrades.

Once Studio is running, carry on with your first workflows.