Published: September 13, 2026 | Category: Buying Guide | QSCompute
Europe's packaging regulation (PPWR, Regulation (EU) 2025/40) became broadly applicable on 12 August 2026, recyclability assessments turn mandatory in 2028, and the first recycled-content mandates — 30% for contact-sensitive plastic packaging — land on 1 January 2030 against more than 80 million tonnes of EU packaging waste a year. At the same time the labour model underneath a materials recovery facility (MRF) keeps failing: manual sorting lines carry roughly 40% annual turnover and a fraction of the throughput a machine sustains. Legal pressure plus a labour model that does not hold is why waste sorting quietly turned into a machine-vision and edge-compute market — and why the hardware you specify at the belt now decides your purity numbers.
The market has moved from optional automation to baseline infrastructure. Robotic waste sorting was worth about $3.36 billion in 2026 and is forecast at $7.78 billion by 2031 (18.3% CAGR), with municipal MRFs the single largest end-use segment at roughly 38% share. The fastest-growing slice is specifically AI sorting: the AI-powered segment is expanding at about 15.8% CAGR versus 10.4% for conventional automated sorters, and its payback is shorter — commonly 2.5–4 years versus 3.5–5 years for mechanical-only sorting.
The throughput numbers explain why: TOMRA's deep-learning recognition add-on identifies overlapping objects at up to 2,000 ejections per minute and 98%+ purity on aluminium can-to-can sorting, while its high-speed variant runs conveyor belts up to 6 m/s. AMP's pick-robot line runs 80–120 picks per minute at up to 99% accuracy. Two things follow from those numbers. First, the classification decision is a real-time vision problem, not a reporting problem. Second, the inference has to live at the belt: a round trip to a cloud region is several camera frames of latency at 6 m/s, which is several items already past the ejector.
Almost every recycling deployment that goes wrong is over-specified at the wrong layer. A MRF does not need a data centre; it needs a small number of hardened nodes positioned where the cameras are, plus one place to aggregate.
| Tier | Workload | Typical platform | Why |
|---|---|---|---|
| Belt-side / sorter node | NIR + RGB material classification, bale composition monitoring, contamination and jam alerts | ARM DIN-rail box (RK3588) or Jetson Orin Nano Super | One node per belt or per optical sorter; 5–25 W fanless, DIN-rail or PoE, single camera group |
| Pick-robot cell | Object detection, grasp targeting, motion sequencing, multi-camera fusion | Jetson Orin NX 16 GB up to AGX Orin 64 GB | 30–120 picks/min needs deterministic low-latency inference plus native robot I/O |
| Line / facility headend | Data aggregation, dashboards, model retraining, recyclability and DPP reporting | x86 server + L40S or RTX 6000 Ada | Historian, retraining, compliance reporting and multi-line rollup |
The belt-side tier is the one that scales with count: an optical sorter and its NIR bank already exist, and the AI node is an addition, not a replacement. That is why ARM edge hardware fits this layer so well — low power, no fan, and a form factor that survives a cabinet next to a conveyor.
The honest answer to "which one" is both, in different places. This is the decision table we use with integrators:
| Factor | ARM edge (RK3588 / Jetson Orin) | x86 + discrete GPU |
|---|---|---|
| Power envelope | 5–60 W, fanless capable | 150–350 W+, active cooling and airflow required |
| Vision throughput | 6–275 TOPS INT8; 2–6 camera streams per node | 100–1,000+ TOPS; 8–30 streams per box |
| Enclosure / siting | Sealed IP-rated fanless enclosure, DIN-rail, small cabinet | Larger filtered cabinet, larger PSU, more heat to remove |
| Software stack | TensorRT, RKNN, ONNX Runtime — INT8-first | Full CUDA ecosystem incl. FP16/FP8 and training |
| Robot I/O | Native CAN, GPIO, multi-Ethernet, some TSN | EtherCAT master cards, PCIe fieldbus cards |
| Fleet retraining / analytics | No — ship cropped frames and metrics to the headend | Yes — can host retraining and the historian |
| Best fit | Per-belt nodes, compact pick cells, retrofit | Multi-line headend, heavy multi-camera lines |
Rule of thumb: inference at the belt belongs on ARM; aggregation, retraining and compliance reporting belong on x86 + GPU. If you are choosing between a single large GPU box at the facility and eight ARM nodes at eight belts, take the ARM nodes — the failure domain is smaller and one box going down costs you one belt, not the plant.
A MRF is one of the more hostile places you can put electronics: paper fibre and glass fines in the air, constant vibration from screens and balers, occasional washdown, wide temperature swings near the tipping hall, and mains transients from large motors starting. The minimum specification we would accept on a belt-side node:
Retrofit first. The cheapest win in a recycling facility is a vision node bolted onto an existing manual QC station: one ARM box plus one camera gives you composition data and contamination alerts before you commit capital to a robot cell. If you are buying a pick robot, buy the Jetson Orin NX or AGX Orin with it — retrofitting compute into a robot cell later is materially harder than specifying it up front. Multi-site operators should stand up the headend GPU server from day one, because that is where model retraining and the PPWR recyclability reporting pipeline will live, and both get harder to bolt on later. Compliance-driven buyers should note the timeline: PPWR recyclability assessment becomes mandatory in 2028, which is short enough that facilities able to output per-bale composition data today will be the ones that adapt without a project.
Adding AI vision or pick-robot compute to a sorting line? We supply the hardened hardware.
QSCompute provides ARM edge boxes (RK3588, Jetson Orin Nano/NX/AGX), fanless industrial PCs and GPU headend servers with wide-temperature, IP-rated and power-loss-protected options. Send us your belt count, camera count and throughput in tonnes per hour and we will spec the nodes and the headend.
Contact: +86 137-1464-6179 | info@qscompute.com