On-Prem & Self-Hosted Deployment

Overview

ToRun can run on your own infrastructure. A one-command Docker installer builds the backend, database migrator, and web app from source and brings the platform up behind a single reverse proxy — the host machine needs only Docker. This is for teams that need data residency, air-gapped operation, or their own local models.

What the installer does

The on-prem installer:

• Builds the Host API, the database migrator, and the SPA frontend from source inside Docker.
• Configures a single edge reverse proxy in front of everything.
• Auto-generates the secrets, certificate, and environment configuration needed to run.
• Seeds an initial admin account from configuration (admin email and password are config-driven).

Because everything is built from source in the container, the host machine doesn't need a .NET or Node toolchain — just Docker.

Using your own local models

On-prem deployments can point at your own local LLMs instead of (or alongside) hosted providers. Combined with the BYOK vault, this means inference can stay entirely within your environment.

Licensing options

On-prem is offered with several commercial options:

• Per-seat license — priced per seat per year, with a $0 setup headline; professional services are available hourly when you want hands-on help.
• Source license — a one-time fee for the source plus an annual updates fee, for organizations that need the code itself.
• Source escrow — available so the source is protected and accessible under agreed conditions even in worst-case scenarios.

(Exact figures are set in the current pricing agreement; your sales/quote reflects the live numbers.)

Operations posture

The on-prem design targets zero-headcount operations — automated install, automated updates, and a self-service support path — so a small team (or a solo operator) can run it without a dedicated ops staff.

Updates

Deployments can self-update so you stay current without a manual rebuild cycle.

Tips

• Set the admin email/password via configuration before first boot so the seeded admin is yours from the start.
• If data must never leave your network, run local models via BYOK and avoid configuring hosted-provider keys.
• Keep auto-update enabled unless you have a change-control reason to pin a version.