Servers are billed by the second in USDG, and the unused balance comes back when you stop. Open the app

One-click apps

Pick an app, pay for the minutes you want, and it boots ready to use on its own HTTPS address, locked with a login that only your wallet can read. No setup page, no account to create.

AppForSmallest sizeLogin
VS Code
vscode
Write and run code from any browser, or hand an agent's workspace to a human.small (2 GB, 0.04 USDG/h)Password, shown to the owner on the server page.
JupyterLab
jupyter
Notebooks for data work, quick experiments and model evals.micro (1 GB, 0.02 USDG/h)Token, shown to the owner. Their link logs in directly.
Headless Chrome
chrome
Let an agent browse, scrape, fill forms and take screenshots from its own browser.small (2 GB, 0.04 USDG/h)Token, shown to the owner, passed as ?token= in the URL.

From the app

  1. Open New server. The apps are the first group: VS Code, JupyterLab, Headless Chrome.
  2. Pick a size (the smaller ones are greyed out), a region and how long to prepay, then confirm the approve and open().
  3. The server page opens with a Login card: the address, the password or token (hidden until you press Show), a copy button and an Open button. The Logs panel shows the boot and prints [nora] the app answers on port …, behind its login when it is ready.
  4. Close and refund when you are done. The server and everything on it are deleted, and the unused USDG comes back.

How an app is locked

  • Each lease gets its own login: an HMAC of a server secret and the lease id, 32 hex characters. Nora computes it when the server boots and again when the owner asks for it. It is never written to a database.
  • It reaches the server as an environment variable at boot. A fixed start script hands it to the app, and refuses to start the app without it. The app only listens on its port once it is configured with the login, so its HTTPS address never serves an open app, not even for a second.
  • Only the wallet that owns the lease can read the login: on the server page after one signature, or through GET /api/v1/leases/{id}/app with the owner's token.
  • Before the app starts, outbound port 25 is closed (IPv4 and IPv6), as on every template. If the rule cannot be set, the app is not started.
  • The login stops working when the server is deleted. A new lease gets a new one.

VS Code

code-server 4.146, the open-source VS Code that runs in the browser. Open the address, enter the password, and you get the editor, its terminal, git, and extensions from Open VSX. The workspace is /root/workspace. Small and up: the editor, its extension host and a language server need the 2 GB.

JupyterLab

JupyterLab 4.6 with Python 3.13 from the official Jupyter image. The Open button carries the token in the link, so it logs you in directly; otherwise paste the token on the login page. Notebooks live in /root/work. Install packages from a cell with %pip install pandas. Micro and up.

Headless Chrome

Chromium from Debian, started headless on the server, with a small gate in front of its DevTools endpoint. Chromium itself only listens on the server's loopback; the gate is the only thing on the public port, and it answers 401 to any request without the token. It installs at boot, so it is ready in about a minute and a half. Small and up: a browser needs the memory.

Connect Puppeteer or Playwright over WebSocket:

javascript
import puppeteer from "puppeteer-core";
const browser = await puppeteer.connect({ browserWSEndpoint: "wss://<address>/?token=<token>" });
const page = await browser.newPage();
await page.goto("https://en.wikipedia.org/wiki/Headless_browser");
console.log(await page.title());
await browser.disconnect();

// Playwright
import { chromium } from "playwright-core";
const b = await chromium.connectOverCDP("wss://<address>/?token=<token>");

Or fetch a rendered page with plain HTTP, no library:

shell
curl "https://<address>/content?url=https://example.com&token=<token>"        # the HTML after scripts ran
curl -o page.png "https://<address>/screenshot?url=https://example.com&token=<token>"   # 1280 x 800 PNG
curl "https://<address>/json/version?token=<token>"                              # browser version and WebSocket URL

The token also works as Authorization: Bearer <token>. Every connection shares the same browser; open a new page or context per task.

From an agent

The apps are templates like the others: vscode, jupyter and chrome. Details in Agents API, SDK and MCP.

javascript
import { Nora } from "./nora.mjs";

const nora = new Nora({ privateKey: process.env.NORA_KEY });
const box = await nora.rent({ template: "chrome", size: "small", minutes: 30 });
await box.waitReady();                 // follows the boot until the app answers
const { websocket, secret } = await box.app();
// ... drive the browser ...
await box.stop();                      // close(), server deleted, unused USDG refunded
shell
NORA_KEY=0x... node nora.mjs rent --template jupyter --size micro --minutes 30   # waits, then prints the login
NORA_KEY=0x... node nora.mjs app <lease>

curl -s -X POST https://www.noracloud.xyz/api/v1/leases/42/boot -H "authorization: Bearer $TOKEN" \
  -H 'content-type: application/json' -d '{"template":"vscode","region":"iad"}'
curl -s https://www.noracloud.xyz/api/v1/leases/42/app -H "authorization: Bearer $TOKEN"

In an MCP client, rent_server with template: "chrome" waits until the browser is ready and returns the WebSocket URL; app_login reads it again later.

Good to know

  • An app costs what its size costs, by the second. There is no extra fee for the app.
  • Apps run as root on your own server. The Nora terminal and the exec API work on them as on any template.
  • If an app stops (a crash, or it runs out of memory), it starts again within seconds and the Logs panel says so. Pick a bigger size if it keeps happening.
  • Env vars you add at boot reach the app. The start command is fixed; for your own setup, use Agent box or Any public image.
  • Each app opens its own address; it is not linked from anywhere, and it answers nothing useful without the login.