Skip to main content
Bifrost Edge is built for fleet-wide deployment. Rather than asking users to download and configure anything, you push Edge to every machine through your existing device management platform with a managed configuration that points it at your organization’s Bifrost. The first time it runs, a user signs in once, and from then on it is invisible.

​
Works with your MDM

Edge deploys through the device management platforms you already use, on macOS, Windows, and Linux.

Jamf

Deploy Edge to your Mac fleet with a configuration profile and managed settings.

Microsoft Intune

Push Edge to Windows, macOS, and Linux devices alongside your existing Intune policies.

Kandji

Distribute Edge across managed Apple devices with zero-touch provisioning.

Omnissa Workspace ONE

Roll Edge out to Windows, macOS, and Linux endpoints from your Workspace ONE UEM console.

JumpCloud

Deploy Edge to macOS, Windows, and Linux devices through JumpCloud commands and software management.

​
Managed configuration

Your MDM delivers a small managed configuration that tells Edge which Bifrost to connect to. Because this is delivered centrally, machines arrive pre-pointed at your organization and users never have to enter a server address or paste a key.

Pre-pointed at your Bifrost

The managed configuration sets your gateway and management endpoints, so every machine connects to the right place from the start.

No secrets on the device

The configuration carries only non-sensitive connection settings. Identity and keys come from the user’s sign-in.

​
What happens on first launch

1

Edge installs silently

Your MDM pushes Edge to the machine as part of its normal device setup. There is nothing for the user to download.
2

One setup approval

On first run, Edge asks for a single approval to set itself up so it can route AI traffic on the device. This happens once.
3

User signs in

The user signs in through the browser with your organization’s single sign-on, linking the machine to their identity and keys.
4

Governance turns on

From that point on, all supported AI traffic on the machine is routed through Bifrost, with policies kept in sync automatically.
After setup, Edge keeps its policies and configuration in sync with Bifrost on its own. Changes you make centrally - app policy, MCP allow and deny lists, routing - reach the fleet without revisiting individual machines.

​
Next steps