Device compatibility

This page exists to answer one question honestly: "Will it work with my machine?"

The list below is not a support list. Every row has a maturity level, and the levels mean very different things. Read the levels first.

What the levels mean

Level	What it means for a print shop
Pilot	The code is ready and is being tried on real machines in the controlled pilot. There is no guarantee it works on your device first time; we try it together and record the outcome, whether it works or not.
Lab (simulated)	The path exists in the product but has only been exercised in a test environment. We have no evidence of a job reaching a real device. Do not assume it works today.
Roadmap	We plan to build it. It does not exist today. These rows are not a support promise.

We do not call any row "certified". Using that word requires collected field evidence from a set number of print shops running real jobs; until that evidence is complete, our language does not change.

Pilot scope

These are the paths being tried in the controlled pilot today:

Path	What it does	What the pilot is proving
Hotfolder	A PDF dropped into a folder you choose is picked up, checked, and placed in the folder your print server watches	Folder permissions, correctly waiting for the file copy to finish, the sidecar file, the server actually picking the job up
EFI Fiery	Submitting a job to Fiery and reading its status	Job submission, status polling and job listing evidence on a real Fiery site
Generic SNMP	Reading printer status (online, paper/toner state, errors)	Discovery and status-read evidence from a real printer

These three are the pilot's first target. If you run a print server other than Fiery, the hotfolder path usually still does the job: we check the file and place it in the folder your server watches.

Paths that are still lab-only

These exist in the product but have no real-device evidence — do not assume they work today:

• IPP and raw printing — direct submission to a printer on the network. No real delivery evidence has been collected yet.
• Generic JMF — the general path for servers that speak JDF/JMF. Not proven against a live endpoint.

Roadmap

The print servers below are not supported today. Their names are listed here not as "coming soon", but so that you do not have to ask:

Canon PRISMAsync · HP SmartStream / PrintOS · Ricoh TotalFlow · SCREEN Trueflow · SCREEN EQUIOS · Konica Minolta AccurioPro · Xerox FreeFlow · Heidelberg Prinect

If you run one of these, the practical answer today is the hotfolder path. We set the order by what pilot print shops actually need — telling us which server you run affects that order.

About device discovery

Edge Hub can look for printers on the local network (mDNS, SNMP, IPP, the Windows printer list) and also lets you enter an IP address by hand.

One important distinction: a device appearing in the list does not mean a job can be sent to it. Discovery means getting an answer over the network; delivery is separate evidence. If you can see your device on screen but cannot send a job, that is not a contradiction — they are two different steps.

What we record during the pilot

When we try a connection on your machine, we note:

• device make and model,
• print server and version,
• the path used (hotfolder, Fiery, SNMP, IPP),
• the network route and any firewall restriction,
• the test job identifier and its result,
• the error record if it failed.

That record is worth something to you too: you do not get stuck at the same point twice. It is kept without your name or your customer details.

Next

• If you have just installed: Your first 15 minutes.
• If a device is not showing up or will not connect: troubleshooting.