Docs

From zero to connected

Infser separates account access, workspace authorization and device execution so every step has a clear trust boundary.

Quick start

Four steps to a governed connection.

01 · Create your account

02 · Pair a device

Generate a pairing request from Infser and confirm it from your workspace.

03 · Review capabilities

The device reports the capabilities it actually supports. Infser does not assume access that was not reported.

04 · Use AI safely

Read-only actions can flow directly; higher-risk operations can require explicit approval before execution.

Agent install

Native on Linux, macOS and Windows

Install the native Infser agent only on systems you control. The signed release manifest selects the correct artifact; pairing still determines which workspace can use the machine.

Linuxshell

curl -fsSL https://infser.com/install-agent.sh | sudo sh -s -- --pair <TOKEN>

macOSshell

curl -fsSL https://infser.com/install-agent-macos.sh | sudo sh -s -- --pair <TOKEN>

WindowsPowerShell

irm https://infser.com/install-agent.ps1 -OutFile install-agent.ps1; .\install-agent.ps1 -Pair <TOKEN>

The optional @infser/cli adds commands such as npx --yes https://infser.com/downloads/cli/0.3.0/infser-cli-0.3.0.tgz doctor, but Node.js is not required by the native agent.

Trust model

Access is never just “connected”

User identity, active workspace membership, device lifecycle, fresh capability support and policy are evaluated before sensitive runtime operations are admitted. Operating-system metadata never grants a capability by itself.

Ready

Create an account, then pair only the machines you want AI to reach.

Start free Security model