Skip to content

Enterprise

Enterprise is how larger teams run VisualRunner: a custom-priced plan plus a set of hand-sold capabilities enabled per workspace. This page covers custom plans and summarises the rest; each has its own full guide:

Custom plans

If your team needs more than the standard Business tier — more active monitors, more storage, more uptime checks, or higher API/Jira/automation-rule limits — a custom plan is negotiated and priced around your actual usage rather than a fixed tier.

There's no self-serve Enterprise checkout. Every custom plan starts with a conversation and ends with a quote you review and accept.

Requesting a custom plan

  1. On the Pricing page, click Contact us in the Enterprise section (or go directly to Enterprise inquiry).
  2. Fill in your name, work email, and company — estimated scale and any extra context are optional but help us put together a more accurate quote faster.
  3. Submit. You'll see an on-page confirmation immediately; we aim to follow up within one business day.

No account is required to submit an inquiry.

Reviewing and accepting a quote

Once our team has built a quote for you, you'll receive an email with a link to a quote page showing:

  • The exact limits included (active monitors, uptime monitors, seats, storage, automated captures/month, API keys, webhooks, Jira project mappings, automation rules).
  • The total price and billing interval (monthly or annual).
  • An expiration date — quotes are time-boxed (30 days by default); an expired quote can't be accepted, so ask for a fresh one if yours lapses.

Anyone can view the quote page via its link — no sign-in required to see what's being offered. Accepting it, though, does require signing in (or creating an account first) and choosing which of your workspaces the plan should apply to. You must be that workspace's owner to accept — the same requirement as any other plan change.

  • If the target workspace has no active subscription yet, accepting redirects you to Stripe Checkout to complete payment; your Enterprise plan activates as soon as payment succeeds.
  • If the target workspace already has an active paid subscription, accepting applies the new limits immediately — no separate checkout step, matching how a self-serve plan upgrade applies immediately today.

Once accepted, your workspace's actual limits reflect exactly what was quoted — not the generic Enterprise tier — everywhere those limits are enforced (Monitors, Uptime, Scans, Collections, and so on).

Hand-sold Enterprise capabilities

Two capabilities are enabled per workspace by our team, independent of your billing plan. Ask your account contact or support@visualrunner.com to switch either on — we set an audited reason when we do.

Capability Solves
VisualRunner Enterprise extension Your IT/security team won't approve the Chrome Web Store extension
Private Runner The sites you monitor are VPN-only / internal and our servers can't reach them

VisualRunner Enterprise browser extension

A separate, privately-distributed build of the browser extension that requests no host access, no debugger, no cookies, no downloads, no tabs — the worst-case install warning is "read your browsing activity on the tab you use it on". Every screenshot is rendered on VisualRunner's infrastructure, not in the browser. It is never listed in any store: we sign and host it, your IT force-installs it by ID.

How to deploy it:

  1. We enable the Enterprise extension on your workspace (or send you a single-use register link — a workspace owner/admin opens it once to turn the feature on).
  2. Your IT force-installs it through your normal managed-extension mechanism (Google Admin console, Windows GPO, Intune, Jamf). The policy value is:
ljibdgcdnpkjlbgnkabomdngebgpamkk;https://ext.visualrunner.com/updates.xml

If your network filters extension-update hosts, allowlist https://ext.visualrunner.com.

  1. Optionally, your IT sets a managed-storage policy pinning the extension to your workspace (workspaceId), so it can't be pointed at any other tenant.
  2. Each team member opens the extension side panel and clicks Sign in (hands off to their existing visualrunner.com session — the extension carries no credentials).

Browsers auto-update it from our feed roughly every 5 hours; you can pin a version through your own policy. Full per-platform policy snippets, verification steps, and removal: VisualRunner Enterprise extension — IT deployment guide.

Private Runner (capture internal environments)

A small Docker container you run inside your own network. It pulls capture jobs from VisualRunner over an outbound-only connection and uploads screenshots back — you open no inbound port and hand us no VPN credentials. It uses the same browser engine as our own capture servers, pinned to the same version, so a runner screenshot matches one taken by us.

How to deploy it:

  1. We enable Private Runner on your workspace.
  2. In Workspace settings → Runners, click Register a runner and copy the vr_runner_… token — it's shown once (rotate to get a new one).
  3. Run the container on a host that can reach both https://visualrunner.com/api and the internal sites you want captured:

bash / zsh:

docker pull visualrunner/runner:latest
docker run -d --restart unless-stopped --name visualrunner-runner -e PLATFORM_URL=https://visualrunner.com/api -e RUNNER_TOKEN=vr_runner_xxxxxxxxxxxxxxxx visualrunner/runner:latest

PowerShell:

docker pull visualrunner/runner:latest
docker run -d --restart unless-stopped --name visualrunner-runner -e PLATFORM_URL=https://visualrunner.com/api -e RUNNER_TOKEN=vr_runner_xxxxxxxxxxxxxxxx visualrunner/runner:latest

Optional env vars: RUNNER_CONCURRENCY (1–16, default 1), RUNNER_NAV_TIMEOUT_MS (default 30000), RUNNER_HEARTBEAT_MS (default 60000). If your team can't pull from Docker Hub, ask us for an image tarball (docker load < visualrunner-runner.tar.gz).

Full multi-shell setup: Private Runner.

  1. In your project's Environments tab, set the environment's Capture delivery to your runner instead of "Platform worker". Monitors and manual captures for that environment now run on your runner.

Once the container has sent its first heartbeat, the runner shows as online in Workspace settings. Private Runner captures authenticated environments (the cookie / header / basic-auth credentials you configured are decrypted per job and sent to your runner over its outbound connection), run the full QA checks — visual comparison, text-length, accessibility, console-error, brand, and missing-translation — and count toward your plan's automated-capture allowance. Full detail, token rotation, and limitations: Private Runner.

Your infrastructure, your storage, your cost. The runner runs on hardware you provide and size — one capture at a time by default, or more if you raise RUNNER_CONCURRENCY on a bigger host (see Host requirements & concurrency). Pair it with your own workspace storage and both the capture execution and the stored screenshots stay on infrastructure you control. That compute is not part of your VisualRunner subscription — your plan price is only the custom limits in your quote, never a charge for runner capacity.

Allowlisting VisualRunner behind a WAF / firewall

If the site you're monitoring sits behind Cloudflare, AWS WAF, Akamai, or similar bot protection, that protection can block VisualRunner's checks and cause false failures. Contact us (support@visualrunner.com or your account contact) with your workspace name and the domain — we'll send you the current outbound IP to allowlist and add you to the notification list for any future change. Full guidance and a ready-to-forward email for your IT team: Allowlisting VisualRunner Traffic.

See also