overnight.technology

Getting started · live products

Docs

Docs homeTunnelsBio linksFile shareNetwork tools

How to start with the products that are live today: authenticated tunnels, bio link pages, file share, and free network tools. The complete tunnel reference stays on the app docs. Nothing here adds a feature, price or uptime promise that is not already on the live site.

TunnelsBio linksFile shareNetwork tools

Tunnels

CLI, troubleshooting and FAQ

Quickstart

Needs Linux or macOS (x86_64 or arm64), bash, curl and python3. The installer puts frpc (the open-source frp client, v0.61.1) and the ot script into ~/.local/bin. Request access first; the API token is shown on the dashboard after we set up your account. Online payment is not open yet.

curl -fsSL https://app.overnight.technology/install.sh | bash
export PATH="$PATH:$HOME/.local/bin"
ot login --token YOUR_API_TOKEN
ot http 3000 --slug demo

You get https://demo.overnight.technology. The token and settings are kept in ~/.config/ot-tunnels/. Stop the tunnel with Ctrl+C.

Locking a link

Every tunnel requires auth. Requests that fail it get a 401 and never reach your machine. The same options are in the dashboard under Create tunnel.

  • token (default) ot http 3000 --slug demo
    Header X-OT-Tunnel, or ?ot= on the URL.
  • basic ot http 3000 --slug demo --basic user:pass
    The browser asks for a username and password.
  • own secret ot http 3000 --slug demo --secret …
    Token mode with a secret you choose.
  • IP allowlist ot http 3000 --slug demo --allow 203.0.113.7,10.0.0.0/8
    Only those IPs or CIDRs, and they still need the token or password.

Webhooks and stable URLs

Webhook senders cannot type a password, so use token mode and put the secret in the URL you register, for example on hooks.overnight.technology with ?ot= in the query string. The query string reaches your app unchanged; ignore the ot parameter there. A slug belongs to the account that created it. Running ot http again with the same slug keeps the URL. If you pass no --secret, the existing secret stays. Running without --allow clears the allowlist.

Request log, limits and errors

The dashboard lists the latest 200 requests per tunnel (time, method, path, status, IP, browser, bytes), including 401s. Bodies are not stored. The API is GET https://app.overnight.technology/api/tunnels/<slug>/logs with a bearer API token. Plans and daily caps are on the pricing page (Starter from €9 / month).

Common responses: 401 if auth fails; 404 unknown tunnel; 409 slug taken; 429 after the daily cap until midnight UTC; 502 or a 404 from frp if auth passed but ot http is not running. Clients installed before 7 November 2026 may need the install command again (“client too old”).

How it works

frpc on your machine keeps an outbound connection to ctrl.overnight.technology:7000, so no inbound ports or router changes are needed. Public HTTPS uses Let's Encrypt certificates on our own server in the EU, passes the auth gateway there, and only then goes through frps to your machine. Service checks run every 60 seconds on the status page. We do not publish an uptime guarantee. Tunnels carry HTTP(S) only.

Request access Full tunnel docs Tunnels overview

Image and file share

File share getting started

Open share.overnight.technology, upload a file (max 25 MB) and get a private share URL plus a private delete link. No account. Optional password. Default expiry is 7 days (you can set the number of days). Limit of 10 uploads per hour per network. Executables are blocked.

Share a file

Network tools

Network tools getting started

Open the tools page and run a DNS lookup, follow an HTTP redirect chain, check a TLS certificate, or see your public IP. No sign-up and no query logging.

Open tools

Questions

Email hello@overnight.technology. Service checks are on the status page. overnight.technology is part of the NOCTIS group; see noctis.industries and overnight.holdings.