Skip to main content

Flux: Zero-Trust Mesh

Flux is EmberNet's zero-trust networking fabric. It connects your edge sites, devices, and cloud into one secure overlay where nothing is reachable unless it is explicitly authorized, and where you never open an inbound port or expose a device to the public internet.

Flux is what makes the rest of the platform work across sites: it's how EmberCORE in the cloud reaches a gateway on a plant floor, how a remote app's interface opens without a VPN, and how a site keeps talking to the center through firewalls and carrier-grade NAT.

Flux is the primary transport, not a fallback. Every endpoint keeps it up unconditionally, over outbound HTTPS on port 443, and it is what carries the platform's traffic. ArcNet gives each node an IP address on your organization's own private network, and its traffic rides Flux. A site reporting Flux as down is degraded.

How it works​

  • Identity, not IP. Every node, service, and user on the mesh has a cryptographic identity. Access is granted between identities, not between addresses, so there is no flat network to scan or lateral movement to exploit.
  • Outbound-only. Edge sites dial out to the mesh; nothing dials in. There are no inbound firewall rules, no port forwards, and no public IPs on your equipment.
  • Everything over HTTPS. Flux traffic looks like ordinary HTTPS, so it passes through restrictive client networks without special firewall changes.
  • Encrypted end to end. Traffic is encrypted between identities across the whole path, not just to a gateway.

What it gives you​

  • Multi-site reach: EmberCORE and central services reach every site as if it were local, with no site-to-site VPN to build or maintain.
  • App interfaces from anywhere: an app deployed at a remote site opens directly in EmberCORE, served back securely through the mesh. See the App Store.
  • Remote access: open a shell or a device console at a remote site without standing up jump hosts.
  • Resilience: sites reconnect automatically through outages and address changes; there's no static tunnel to break.

Managing the mesh: the Flux Console​

Fireball platform staff manage Flux from the Flux Console in EmberCORE, under the Zero Trust Network category. It is a live view of the whole fabric with full management of what is on it:

WhatWhat it is
IdentitiesThe cryptographic identities on the fabric: nodes, services, and users. Creating one lets that endpoint join.
ServicesThe things that can be reached over the fabric, each with its own access rules.
RoutersThe fabric's routers, which carry traffic between identities.
Access policiesWhich identities may use or host which services. Deny by default.
Device requirementsWhat an endpoint must satisfy before it is trusted.
Sign-in rulesHow identities authenticate, including third-party sign-in.

Platform staff can create, edit, and remove each of these directly from the console. The console also carries an ArcNet tab for the ArcNet network.

Tenant drill-down​

On All Clients, the console shows the whole mesh across every tenant. Select a client in the header and it drills down to just that tenant's identities, services, routers, and policies, and anything created there is tagged to that tenant automatically.

Tenant Admins and Engineers get a read-only view of their own organization's mesh: its identities, services, and edge routers.

Relationship to the App Store​

Flux is not something you deploy from the App Store. It is part of the platform itself. App Store apps ride on Flux: when you open a remote app's GUI, that session travels over the mesh.

Next steps​