InStep instependpoint.com Early access

Security: an agent without root, jobs only with a signature

Distributing software to every machine creates a powerful lever. InStep is built to keep that lever small: the agent has no root privileges, the device only runs verified, fixed tasks, and every remote action is visible.

How device management stays secure

  • Small privilegesThe agent runs as its own user without root. Whatever needs root is done by separate services with one fixed task each.
  • Everything verifiedJobs and updates are signed, time-limited and cannot be replayed. The device verifies before every execution.
  • Everything visibleEvery remote action reports itself on the device, and the audit log records who triggered what and when.

Your server, your devices, no cloud lock-in

The InStep server runs as a container on your own network. Devices reach out on their own – so data stays in-house and no open ports are needed on the devices.

InStep architecture On the left the administrator with the web portal in the browser, connected over HTTPS to the InStep server in the middle. The server runs on your own network as a container and contains the web portal, device API, signing service and a database with the audit log. On the right several Linux devices with the InStep agent, updater and tray icon. The devices open outbound HTTPS connections with TLS pinning to the server; over this connection they fetch signed updates and jobs. Administrator Web portal in the browser Login, live view your own network · on-premises InStep-Server Container · Podman or Compose Web portal · live updates Device API /api/v1 · JSON Signing service · ed25519 SQLite · Audit-Protokoll HTTPS Linux devices Notebooks & desktops instep-agent service, no root root services fixed tasks only instep-tray icon in the system tray no open ports outbound · HTTPS TLS-Pinning (SPKI) signed updates & jobs · ed25519
InStep architecture At the top the administrator with the web portal in the browser, connected over HTTPS to the InStep server on your own network. The server contains the web portal, device API, signing service and a database with the audit log. At the bottom the Linux devices with agent, updater and tray icon. The devices connect outbound over HTTPS with TLS pinning and fetch signed updates and jobs through it. Administrator Web portal in the browser · Login HTTPS your own network · on-premises InStep-Server Container · Podman or Compose Web portal · live updates Device API /api/v1 · JSON Signing service · ed25519 SQLite · Audit-Protokoll outbound · HTTPS TLS-Pinning (SPKI) signed updates & jobs · ed25519 Linux devices Notebooks & desktops · no open ports instep-agent no root root services fixed tasks only instep-tray system tray
Devices poll the server regularly (HTTPS polling). Updates and jobs are delivered with that request and verified on the device before they run.
  • Self-hostedOne container image with web and background service, data in a volume. Runs with Podman (rootless) or Compose.
  • Outbound connections onlyDevices work in the office, at home and over VPN, without port forwarding on the endpoint.
  • Lean agentA static Rust binary as a systemd service, with no runtime of its own.

Agent without root – root only for fixed tasks

Whatever needs root is done by separate system services with exactly one task each: applying an agent update, system updates, installing apps, reading compliance facts, setting the LAPS password, reboot, shutdown and rename, and installing missing dependencies. Each service is hardened with systemd as strictly as its task allows.

There are no free-form remote commands. Package names for self-healing and for missing dependencies never come from the server; they come from a fixed list in the agent or from the signed package.

Signed, time-limited, not replayable

Jobs and updates carry an ed25519 signature over content and checksum, an expiry date and protection against replay. The device rejects downgrades. The signing key lives only on your server.

Trust from the first contact

The TLS pin and the update key are built into your server's installer package – no “trust on first use”. Connections only go out from the device; no port is open on the device.

Remote access with guardrails

The terminal opens only with a fresh, signed grant – as the logged-in user or through a dedicated service account, never directly as root. Remote control shows only the active user's screen. It starts without a prompt, but the tray displays it for the whole session and the user can end it at any time. Clipboard, file transfer and audio are blocked, and nothing is recorded.

LAPS for Linux

The agent only sees ciphertext. The password is encrypted end-to-end, every retrieval lands in the audit log, and the password is rotated after every session.

Transparency on the device

The tray announces scheduled jobs and reports the start and result of every remote action. Local switches on the device shut down individual features. If a switch is missing, the per-feature default applies (for remote control: on). If the configuration is damaged or not owned by root, the feature stays off.

Hardened portal

Login, a strict content security policy without inline scripts, and an audit log of all administrative actions.

Honestly: where the limits are

System updates need network access and broad write permissions – that is in the nature of package managers. pacman and dnf can import keys named by your package sources; InStep never adds sources itself. There is no connection to directory services (LDAP/AD).

How we develop

Every step goes through checks for function, quality and security before it is merged. Tests run without network access and never against real hardware.

Finally manage your Linux devices with an overview

Request early access by email and join the waiting list. You will be among the first to know when InStep is available; we invite selected interested parties to test it in advance.