inline

Fleet

Run one command on a Linux, Mac or Windows machine and approve the code it shows. It reports each service by how far it really reaches, and for each risk a firewall can fix, inline drafts a plan that changes nothing until a person approves it.

1:30 · narrated, with captions · Security and the platformRead about Fleet

Chapters

What it covers

  • Linux, macOS and Windows
  • Joins when a person approves
  • Real reach
  • Plans that roll back

inline Fleet: one command joins a Linux, Mac or Windows machine, reports how far each service reaches, and drafts firewall plans that roll back.

Read about Fleet

Transcript

The narration as spoken, by chapter. Select a time to play the film from there.

Intro

inline Fleet. What is really reachable on every machine you run, and a reviewed firewall plan for each risk.

Join a machine

Run one command on any Linux, Mac or Windows machine. It checks what is really reachable, then shows a code to approve.

Approve the code

Type that code into inline. You see what the machine reported, and its key fingerprint, before you approve it.

The first report

It joins with its own key, and reports each service by how far it really reaches, not just which ports are open.

Every machine

The fleet page shows every machine, worst first, and updates as they report.

One machine

inline can explain any machine in plain words, but fixed rules decide every finding and plan.

The firewall plan

For each risk a firewall can fix, inline drafts a plan: who keeps access, the exact script it will run, and how it rolls back.

Safeguards

Nothing changes until a person approves. Sending from the dashboard takes two keys: the workspace setting and a flag on the machine. Those plans never touch SSH, RDP or WinRM, and every change rolls back unless it is confirmed. Fleet is on every inline plan: three machines on Free, fifty on Pro, unlimited on Enterprise.

Put it on one repository

Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.