One server. Multiple machines. No cable runs.

Name: CodeNet
Brand: Iron Glacier

CodeNet ends sneakernet in shops where pulling Ethernet to every machine was never going to happen. A small receiver plugs into each machine’s USB port and appears to the control as an ordinary flash drive that nobody ever has to carry over and plug in.

Request a Quote Compare Capabilities

What CodeNet does

CodeNet is two parts. A server sits on your shop network and holds the files. Small USB-powered receivers sit at each machine and present those files to the control.

You upload a program once, from a browser or an SFTP client, then send it to one machine or push it to all of them. The operator does not plug anything in, unplug anything, or carry anything. The file is simply on the drive when they look.

Each receiver draws its power from the machine’s own USB port, so there is no second power supply to find and no outlet to run. It pairs with the machine it is plugged into automatically.

At a glance CodeNet

Machines per server: Up to 8
Connection to machine: USB-A receiver
How the machine sees files: USB flash drive
Connection to your network: Ethernet or Wi-Fi
Receiver range: ~50 ft on a shop floor
Compliance Upgrade: Available at order or any time after

Best suited to

Smaller shops, machines that cannot share files over Ethernet, and anywhere running network cable across the floor is impractical. If you need machine data monitoring or drip feed as well, CodePod is the one to look at.

The system

Two parts, one job.

CodeNet Server

The server connects to your shop or office network by Ethernet or Wi-Fi, whichever you have where it sits, and runs a separate private wireless link to reach the receivers. That link is encrypted, and the two ends verify each other before any file moves. An external antenna gives it roughly 50 feet of reach on a working shop floor.

Upload: browser over HTTPS, or any SFTP client
Manage: central admin page for receivers, users, and file assignment
Distribute: send to one machine, a group, or every machine at once
Monitor: see which receivers are online and what they hold

CodeNet Receiver

One receiver per machine. It plugs into the control’s USB-A port, takes its power from that port, and presents itself as a standard USB flash drive. From the control’s point of view nothing unusual has happened at all.

No power supply: runs entirely off the machine’s USB port
No configuration: pairs with its machine automatically
No training: the operator browses the drive exactly as before
Paired to your machine: reads the CNC’s unique fingerprint and pairs itself to that machine
Same protection: files are encrypted at rest, like every other part of the system

Server to receiver

The right file lands on the right machine.

A program you send to machine four arrives at machine four. The server and the receiver recognize each other before anything moves, so a file cannot turn up on a control it was never meant for. That link runs on its own closed wireless network, encrypted, with no internet involved at any point.

Both ends verify each other

The server and each receiver prove who they are every time, before anything is sent. A device that is not part of your system is never offered a file.

Encrypted over the air

Every transfer is encrypted in flight, so the contents cannot be read off the air between the server and the machine.

Paired, not open

Each server is cryptographically bound to its own receivers. Another server cannot reach them, and nothing else can join the network.

Refused by default

If either side fails to verify, the transfer does not happen. The failure case is a file that did not arrive, never a file that arrived unprotected.

Pairing

Nothing to set up at the machine.

Plug a receiver into a control and it reads that machine’s own fingerprint and pairs itself to it. No password to pass along, no label to keep track of, and nothing for the operator to do. From then on, files for that machine go to that receiver, encrypted the whole way.

It comes from the machine itself

The fingerprint comes off the CNC itself, so there is no password to pass along and no label to peel off. The receiver attaches itself automatically and nobody has to set it up.

Delivered only where it belongs

A file goes to the receiver paired to your machine and to no other one. It is encrypted at rest on the way there and while it waits.

A lost receiver isn’t a lost program

Files on a receiver are encrypted at rest, and every program stays on the server regardless. What left the building is a piece of hardware to replace.

In practice

Set up once, then forget it.

Configuration happens before the server ships, once we have the decisions only you can make: who needs an account, and how the server should sit on your network. Receivers are the easy part, since each one pairs itself the first time it is plugged in.

Place the server

Put it somewhere central with power, connect it to your network by Ethernet or Wi-Fi, and enter your network details once through the browser admin page.
Plug a receiver into each machine

Into the control’s USB port. It powers up from the machine and pairs itself. There is nothing to configure at the machine and nothing for the operator to do.
Upload once, send anywhere

Drop the program onto the server from your desk, then assign it to the machine that needs it, or push it to all of them. It is on the drive before the operator reaches the control.

Optional

Working toward CMMC? There is an upgrade for that.

A Compliance Upgrade adds audit logging, certificates issued to your users, and enforced password rotation. It is available on both products as a signed software update, so you can order it with your unit or unlock it later without sending anything back. What the upgrade adds →

Compare

CodeNet and CodePod side by side

The difference is how they reach the machine and how many machines one unit covers. Everything else, protection included, works the same way on both.

Capability comparison of CodePod, CodeNet Server and CodeNet Receiver
Capability	CodePod	CodeNet Server	CodeNet Receiver
Machines covered	1	Up to 8, via receivers	1
Connection to machine	Ethernet	Via receivers	USB-A
Connection to your network	Ethernet or Wi-Fi	Ethernet or Wi-Fi, plus an encrypted private link to receivers	Encrypted private link to server
How you upload	SFTP or HTTPS browser	SFTP or HTTPS browser	Via the server
How the machine sees files	Network file share	—	USB flash drive
Data protection	Encrypted at rest, full disk	Encrypted in transit and in use; nothing readable at rest	Encrypted in transit and in use; nothing readable at rest
Access protection	User login and password	User login and password	User login, plus the CNC’s own fingerprint
Server-to-receiver link	—	Encrypted, both ends verified	Encrypted, both ends verified
User accounts	Multiple, isolated	Multiple, isolated	Managed by the server
Admin interface	Browser-based	Browser-based, central	Managed by the server
MTConnect / OPC‑UA forwarding	Yes	No	No
Ethernet-type DNC drip feed	Yes	No	No
Needs its own power	Yes	Yes	No, powered by the machine

Questions

Common questions

Does the machine need to support anything special?

Only a USB-A port that it can already read files from. If an operator can put a flash drive in it today, a receiver will work in it.

How far will the receivers reach?

Roughly 50 feet in a real factory environment, using the server’s external antenna. Shop floors are hard on wireless signals, so that figure comes from a floor with machines and racking between the two ends, not from an empty room. For larger floors, tell us the layout and we will work out what you need.

Is the link between the server and the receivers secure?

Yes. Every transfer over that link is encrypted, and the server and the receiver verify each other before a file moves. The two are cryptographically paired, so a server talks only to its own receivers and a receiver trusts only its own server. If either side does not check out, nothing is sent.

Can I send a program to just one machine?

Yes. Files are assigned per machine from the server’s admin page. You can also push the same file to a group or to every machine at once when a revision affects all of them.

Does it need an internet connection?

No. Like CodePod, CodeNet runs entirely on your own network and makes no outbound connections.

What if someone unplugs a receiver?

Files on a receiver are encrypted at rest, and the server keeps every program regardless, so a missing receiver is hardware to replace and not work to redo. Files are delivered only to the receiver paired to your machine, so a receiver taken somewhere else stops being sent anything. Plug it back into its own machine and it carries on as normal.

Can I mix CodeNet and CodePod in the same shop?

Yes, and plenty of shops should. A common pattern is CodePod on the machines that can share files over Ethernet and are worth monitoring, and CodeNet covering the rest at a lower cost per machine.

Do I need the Compliance Upgrade?

Only if you handle Controlled Unclassified Information and have to evidence it. The upgrade adds audit logging, certificates issued to your users, and enforced password rotation, and it brings real administration with it. If nobody is assessing you, buy the device without it.

Nothing about the device changes if you skip it. The machine still never touches your network, files are still encrypted at rest, every user still signs in over SFTP or HTTPS, and the firewall still denies by default.

It is a signed software update, so adding it later takes no hardware and no return. What the upgrade adds →

Does the unit get security updates?

Yes. Units under support receive security updates as issues come to light, on no fixed schedule and independent of the release calendar. How long a unit stays under support is set in your agreement, so the term is known before you order.

What happens in two years?

A new release lands in September of every even year, so you can budget against them. At the end of a unit’s support term you can exchange it at a reduced price against the unit you send back, buy current hardware outright, or arrange extended support and keep running what you have. Your users, settings, and logs move across either way. Security updates are separate and land on the unit you already have. Exchange terms go in your agreement.

Who builds it

Iron Glacier is an American company, deliberately small and working on one problem. Design, testing, and support are not separate departments here, so a question about your unit goes straight to the bench it was built on. More about how we work →

How many machines are we covering?

Send us your machine list and a rough idea of the floor layout, and we’ll work out how many receivers you need and what it costs.

sales@ironglaciertech.com (385) 288-0738