Skip to main content

EmberNet Endpoint

EmberNet Endpoint is the software that joins a machine to the EmberNet platform as a first-class endpoint. Install it on a host, whether a Windows workstation, a Linux facility gateway, an edge compute node, or a Raspberry Pi, and that machine becomes securely addressable from anywhere on the EmberNet fabric, without your operations team having to publish a route.

It runs on Windows and Linux, built from the same design and the same auth model on each platform.

What it does​

EmberNet Endpoint connects the host to the EmberNet fabric with these components:

ComponentRole
FluxThe primary transport. The always-available zero-trust fabric. It reaches out over outbound HTTPS on port 443, so it works on restrictive networks that allow only HTTPS. It is never torn down.
ArcNetThe host's encrypted network interface. It gives the host an address on your organization's private network, and its traffic rides Flux.
A parallel tunnelAn optional extra tunnel for legacy point-to-point deployments, switched on per endpoint from EmberCORE.

Flux is the one that carries traffic. It is always up, and EmberCORE is told within seconds if it stops connecting. An endpoint reporting Flux as down is degraded, and that is the state worth investigating first.

The parallel tunnel sits outside that. It is switched on per endpoint from EmberCORE, and it deliberately never affects the status the endpoint reports for Flux.

Once connected, workloads running on the host can reach EmberNet-hosted services directly, and the host itself is reachable from the rest of your fabric, all under the zero-trust model enforced by the platform.

Where it sits in the stack​

The endpoint joins the fabric and makes its host reachable. On facility gateways it also carries fabric traffic for other devices rather than only riding it.

Choose your platform​

  • Windows: a single signed installer, a tray app, and a local web UI. For engineer laptops, control-room HMIs, and factory-floor kiosks.
  • Linux: a headless daemon with an operator CLI and a local web UI. For facility gateways, edge nodes, and any Linux host that needs to be on the fabric.

Key characteristics​

  • Zero-touch after enrollment. Enroll once with your identity provider account via the device-code flow; the endpoint configures its tunnels and keeps them healthy on its own.
  • Split-tunnel by default. The endpoint claims routes only for EmberNet-assigned subnets. Your normal network keeps working exactly as before.
  • Local-only control surface. The management screen is available on the host itself only, never exposed to the network.
  • Nothing inbound. Flux connects out over HTTPS on port 443, so the host needs no inbound port opened, and its status is reported to EmberCORE.
  • Managed from EmberCORE. Enrolled endpoints appear in EmberCORE, where you can see their status and manage them at fleet scale.

Next steps​