Edge Agent Setup

Model a site's real interface topology — instruments, endpoints, protocols, and routing — in the dashboard, then prove the host is ready with a preflight check that records setup evidence as you progress toward validation.

What It Does

Connecting a lab to Vorian Connect is more than installing the on-premises Edge Agent. Before go-live, the site's full interface topology has to be modeled correctly. Edge Agent Setup is the dashboard surface that does that modeling, and the host preflight is the check that proves the machine running the agent is ready to listen.

The setup wizard models the real site topology:

Setup keeps a first-interface handoff visible, so an administrator can see whether the current focus has a modeled source, an enabled source channel, interface health, and ACK/routing proof before opening Validation Evidence.

Honest about scope. Agent Setup does not yet provision activation tokens or certificates, and it does not auto-discover proprietary feeds or connect instruments directly to the cloud. Setup notes and evidence are stored through the audited configuration API, never as free-form secrets in text fields.

Host Preflight

The Edge Agent ships a agent-preflight command that runs on the host machine before the agent is expected to receive traffic. It checks the conditions required for the agent to run and listen:

The check prints pass/fail results for a human operator, and can also write a machine-readable JSON report (--json) that is uploaded into the dashboard as tenant-scoped setup evidence. Each check carries a name, status, and detail, so a failing check names the condition to fix rather than a bare error.

Installer and site-specific overrides are supported through flags such as --tenant-id, --gateway-addr, --mllp-addr, --query-mllp-addr, --instrument-addr, --ntp-server, and egress proxy settings, so a single preflight run can validate a specific site's configuration before first connect.

Setup Evidence and Audit

Preflight reports and agent settings are pilot-critical onboarding data. Every settings update and setup-evidence upload writes a required audit record before changing configuration, and fails closed with no-change guidance if audit logging is unavailable. Source-linked reports treat decommissioned sources as stale, so a retired interface does not receive fresh setup evidence.

Where It Fits

Technical Details

Last updated: August 16, 2026