The architecture behind Keystone and Redoubt
Every ZET controller runs the same core design: two isolated processing domains, one dedicated to deterministic motion, the other to everything networked. That split is what lets a single platform scale from a hobbyist bench to a government floor without redesigning the brain.
Two cores, one job each
Real-time motion core
Handles g-code interpretation and deterministic step/servo command timing on a dedicated real-time processor. It is never blocked by network activity, UI rendering, or a display reconnecting — the motion loop keeps running regardless of what the supervisory core is doing.
Networked supervisory core
Runs connectivity, the local display UI (when one is attached), CAM tool integrations, and the security stack. It talks to the motion core over an internal control link — disconnecting it, rebooting it, or swapping the display module attached to it never interrupts a running job.
Modularity, not a marketing line
Because job state and configuration live on the motion core, the same unit can run as a pure external network controller with no display at all, or with a local display docked for on-machine control — and you can change your mind later without losing any configuration.
Fast on the wire, secure over the air
2.5 Gigabit Ethernet, standard
Every ZET controller — Keystone and Redoubt alike — ships with 2.5GbE as the primary control-plane connection: enough headroom for high-resolution toolpaths, live status streaming, and remote diagnostics without contention.
Optional Wi‑Fi 6E module
For installs where running conduit isn’t practical, an optional Wi‑Fi 6E module supports WPA3-Enterprise authentication on a network segment kept isolated from the real-time control plane — wireless convenience without putting the motion core on the same trust boundary as the rest of the shop network.
Built to fit your existing workflow
Native support and post-processor plugins are being developed for the CAM tools already running on most shop floors, so switching controllers doesn’t mean relearning your toolpath software.
Vectric Aspire
Native post-processor and direct job-send support for Aspire, covering the workflow most hobbyist and prosumer router/laser shops already use.
Autodesk Fusion 360
Post-processor and cloud-to-controller job hand-off for shops running Fusion 360’s CAM workspace across mixed hobbyist and production equipment.
Mastercam
Post-processor support targeting the production and industrial machining workflows Mastercam is built for — the same tier ZET Redoubt is designed to serve.
Designed for environments that can’t tolerate a black box
Isolated control plane
Wireless and network management traffic are kept off the same trust boundary as real-time motion commands, whether you’re connected over 2.5GbE or the optional Wi‑Fi 6E module.
Signed firmware
Firmware updates for both cores are designed to be cryptographically signed and verified before install, so what’s running on the floor is always what shipped.
FIPS 140‑3 roadmap
The ZET Redoubt Gov configuration is engineered toward FIPS 140‑3 Level 2 cryptographic module validation for federal and defense procurement. Validation is a roadmap milestone, not a current certification — we’ll update this page the moment that changes.
WPA3-Enterprise
The optional Wi‑Fi 6E module authenticates via WPA3-Enterprise rather than a shared pre-shared key, so wireless access can be tied to individual credentials and revoked per-user.