Product

Roadmap

What is shipped, what we are building, and what we won't build.

Priorities come from what operators ask us for. Dates are left out on purpose: we'd rather ship than promise. Want something moved up? Tell us why.

Now

  • Hardening. Fixes from an independent security review of the newest features.

Next

  • Sign in with Google Workspace or Microsoft 365, and an option to require it for your domain.
  • Locked mode. Devices that only obey your team's keys, with end-to-end encrypted sessions, so a compromise of our servers can't reach them. See the security model.
  • Session recording. Replay what was done in a shell, for compliance and for "what did the technician change on our kiosk?". Output only by default, retention you choose, every playback in the audit log, exportable as an open asciicast file.
  • Single sign-on with SAML (Okta, Entra ID, OneLogin).

Need one of these? Write to support@fieldhand.dev: what customers ask for gets built first.

Later

  • Separate invoices per customer for integrators who resell Fieldhand.

Not planned

  • Full-OS image updates (A/B partitions) and container deployment. Fieldhand runs on the OS you already have. If you need to ship firmware images, Mender or balena do it well, and Fieldhand runs next to them.
  • Windows and macOS agents.

Shipped

Everything in the changelog: fleet commands, alerts to chat and PagerDuty, service health and logs, an API with tokens, a viewer role, audit export, device web pages, files, the browser terminal with drop-proof shells, health and connection history, alerts, tags, teams, signed auto-updates and per-device billing.

Something wrong or missing on this page? Tell us.