Let people reach apps directly

Let people on your company network open team apps straight from your own runners, at a stable HTTPS address, with access control staying in kanman. For IT: settings, runner variables, TLS, load balancing and rollout.

Enterprise, for IT

Team apps are part of the Enterprise plan. This page is for the IT team that sets up how people reach them.

Team apps (dashboards, tools, previews) run only on the team’s own runners, inside your company network. By default, people’s browsers load them through kanman. You can instead let people on your network open apps directly from your runners, and optionally switch the path through kanman off.

Choose how people reach apps

Workspace owners and admins choose this in Workspace settings > Runs and runners > How people reach apps. Every change is recorded in the workspace audit log.

Choice What happens
Through kanman (default) Browsers load apps through kanman. Works from anywhere the person can sign in to kanman. Nothing to set up.
Direct You enter an HTTPS base address, for example https://apps.example.internal, that points at your runners or a load balancer in front of them. When you save, kanman checks the address from your browser and shows whether it works. People on the company network open apps directly; people off the network still get them through kanman.
Direct only The path through kanman is switched off: kanman refuses to pass app pages or data through for this workspace. People off the company network see a note to open the app on the company network (VPN).

Stable addresses

An app’s address never names a runner:

https://<your-host>/a/<workspace>/<team>/<app>/

Workspace, team and app are their short names, as in kanman’s own links. The address stays the same when runners are added, replaced or restarted.

Set up each runner

Set these environment variables on every runner, then restart it.

Variable What it does
KANMAN_APP_PROXY_BIND The address the runner’s app gateway listens on. Default 127.0.0.1, which only the runner itself reaches. Set 0.0.0.0 or the runner’s internal IP so your load balancer can reach it.
KANMAN_APP_PROXY_PORT The gateway’s port. Pick a fixed one, for example 8443 or 8080.
KANMAN_APP_PEERS With more than one runner: a comma-separated list of the other runners’ gateway addresses, for example http://runner-2.internal:8080,http://runner-3.internal:8080.
KANMAN_APP_BACKUP_ROOT A folder all runners can reach, such as a network share. Backups of every app’s data go there.

More than one runner

An app and its data live on one runner, its home. When a request arrives at a runner that does not hold the app, the runner forwards it to the one that does, with one hop at most. That is what KANMAN_APP_PEERS is for. Alternatively, configure your load balancer with sticky routing per path prefix /a/<workspace>/<team>/<app>/; with peers set, stickiness is not needed.

Backups and takeover

With KANMAN_APP_BACKUP_ROOT set, each app’s data is backed up hourly and before every change. When a runner is removed or stays offline, another runner takes the app over and restores its newest backup.

Without a shared folder, an app whose runner is gone waits for that runner. kanman never starts it elsewhere with different data, and the app’s owner is told.

TLS and the load balancer

  • Terminate HTTPS at your reverse proxy or load balancer, with a certificate your company’s browsers trust. Forward to the runners’ gateways over the internal network.
  • The address must be HTTPS: browsers refuse to show an http page inside kanman.
  • Health check: GET /__kanman/ping on each runner’s gateway answers 200.

Access control stays with kanman

Every app link carries a short-lived sign-in from kanman. The gateway admits only people kanman lets in, each with their own rights. Opening the address without coming from kanman shows a message to open the app from kanman.

Self-hosted edition

When kanman runs in your own network, Through kanman goes through your own kanman instance. App pages and data never leave your network.

  1. Set up DNS, a TLS certificate and the load balancer for your app address.
  2. Set the runner variables above and restart the runners.
  3. Choose Direct, enter the address and check the result kanman shows.
  4. Let people use it for a while.
  5. Switch to Direct only once everyone reaches the apps on the company network.

Related: Apps, Keep apps safe, How team apps are hosted, Live view from your runner, Hosting and data residency.

Last updated: January 1, 0001

Open kanman