Technology Never Stands Still, and Neither Do We
Validated Mini-ITX platforms engineered for reliable deployment in industrial, edge, and embedded system environments.
Custom Mini-ITX Engineering
Custom Mini-ITX Board Design & ODM
Modify an existing Mini-ITX platform or develop a new motherboard around the I/O, power, mechanical, thermal, software, and lifecycle constraints of your system. We help engineering teams determine what can be changed, what the processor platform can actually support, and when a requirement needs a new PCB rather than another adapter.
Standard Board Almost Fits?
When a Custom Mini-ITX Board Becomes the Better Engineering Choice
A custom motherboard is justified when the constraint sits on the board itself. The processor may be suitable while the production system still fails because the required interfaces are missing, connectors are in the wrong locations, expansion consumes too much space, or the available power architecture does not match the equipment.
Mini-ITX fixes the board outline at 170 × 170 mm. Inside that envelope, processor resources, PCB area, connector keep-outs, power stages, routing channels, and cooling zones all compete for space. A requirement that looks simple at the system level can therefore require a board-level redesign.
The Required I/O Combination Does Not Exist
The system needs a specific mix of Ethernet, COM, CAN, GPIO, USB, displays, storage, or expansion that cannot be implemented cleanly with a catalog motherboard.
The Existing Board Does Not Fit the Product
Rear I/O, internal headers, cable exits, heatsink zones, or component height conflict with the enclosure even though the compute platform is suitable.
The Electrical Requirements Have Changed
Input voltage, protection, peripheral power, environmental limits, or lifecycle requirements exceed what the original motherboard was designed to support.
Board-Level Customization
What We Can Change on a Mini-ITX Motherboard
- Ethernet
- Controller count, 1GbE/2.5GbE/10GbE architecture, copper or SFP-family interfaces, management ports, and connector position.
- COM, CAN & GPIO
- RS-232/422/485 channels, CAN interfaces, digital I/O, transceivers, isolation requirements, headers, and application-specific pinout.
- USB & Display
- USB allocation, external or internal connectors, HDMI, DisplayPort, LVDS, eDP, touch interfaces, and display topology.
- Storage & Expansion
- M.2 sockets, SATA ports, NVMe, PCIe slot width, wireless modules, storage topology, and expansion-card interfaces.
- DC Power
- Input range, protection, sequencing, peripheral rails, standby behavior, connector current, and startup requirements.
- Board Mechanics
- Rear-I/O layout, internal connector position, orientation, component height, keep-outs, mounting interfaces, and cooling zones.
Multiple Serial Ports → Multiple Power Inputs → Multiple 10G Ethernet Ports →
Platform Architecture
Requested Connectors Must Map to Real CPU and SoC Resources
We resolve the data path before committing to the connector count. PCIe 3.0, 4.0, and 5.0 operate at 8, 16, and 32 GT/s per lane respectively. USB 3.2 defines 5, 10, and 20 Gbps transfer-rate tiers, while SATA 6Gb/s defines a 6 Gb/s link rate. These signaling rates are not application-throughput guarantees; they define the interfaces that the architecture must allocate correctly.
| Requested Function | What Must Be Mapped | Typical Constraint |
|---|---|---|
| PCIe / M.2 | Endpoint width, generation, lane source, bifurcation, and simultaneous operation. | Available processor lanes, switch uplinks, shared resources, and controller topology. |
| USB | Native host ports, hub topology, controller generation, connector type, and attached devices. | A hub increases port count but does not increase the bandwidth of its upstream host connection. |
| Ethernet | MAC/PHY or discrete controller architecture and each controller’s connection to the host. | PCIe resources, controller bandwidth, power, driver support, and available rear-I/O area. |
| NVMe / SATA | Storage interface, M.2 keying, lane assignment, boot requirements, and concurrent devices. | M.2 and SATA resources may be shared or mutually exclusive on a particular processor or chipset. |
Engineering Intake
What We Need Before Starting a Custom Board Feasibility Review
A useful design brief describes the equipment around the motherboard, not only the motherboard itself. Missing enclosure, power, peripheral, or software information can invalidate an otherwise workable port map.
| Engineering Input | What to Provide | What It Determines |
|---|---|---|
| Compute & Software | Workload, processor preference, OS, memory, accelerator, boot method, and required drivers. | Processor platform, software baseline, memory architecture, and available platform resources. |
| I/O & Peripherals | Port count, protocol, speed, attached device, electrical mode, isolation, pinout, and concurrent-use requirements. | Controllers, transceivers, resource allocation, and connector architecture. |
| Power | Input-voltage range, source characteristics, startup behavior, peripheral load, and protection requirements. | Power-tree architecture, conversion stages, connector rating, and protection strategy. |
| Mechanical | Enclosure drawing, rear openings, height limits, heatsink interface, keep-outs, and cable zones. | Connector placement, critical component location, and mechanical feasibility. |
| Product Program | Prototype quantity, estimated annual demand, expected product life, and revision-control requirements. | Component strategy, design-reuse decisions, and lifecycle planning. |
Design Strategy
Modify a Proven Platform or Create a New Mini-ITX PCB?
The lowest-risk solution is the smallest engineering change that closes the product requirement. We separate configuration, PCB redesign, and new architecture before committing the project to a full motherboard design.
| Engineering Path | Best Fit | Result |
|---|---|---|
| Controlled Configuration | The reference motherboard already satisfies electrical, mechanical, and I/O requirements. | A controlled SKU using defined BOM options, connector population, and configuration settings. |
| Platform-Based PCB Redesign | The processor architecture fits, but I/O, power, connector placement, or mechanics do not. | A new PCB that retains as much of the proven platform architecture as practical. |
| New Board Architecture | No existing platform can satisfy the combined compute, I/O, expansion, power, and mechanical requirements. | A new resource map, schematic architecture, PCB implementation, and board revision. |
Engineering Review
Have a Port List, Block Diagram, or Enclosure Drawing?
Send the hard constraints: workload or processor preference, required interfaces, exact power input, enclosure geometry, operating environment, OS, quantity, and expected product life. We will first determine whether the requirement needs a new PCB.
After Architecture Freeze
From Approved Resource Map to Schematic and PCB Layout
PCB engineering begins after the major interface paths and controller architecture are agreed. At this stage the job is to preserve that architecture electrically, mechanically, and in manufacturable PCB data.
- Schematic Definition Capture processor support circuits, memory, controllers, clocks, resets, boot devices, power rails, protection, debug access, and external interfaces.
- Stackup & Constraint Definition Establish the fabrication stackup with the PCB supplier, then define controlled-impedance structures, reference planes, differential-pair rules, via strategy, and power-current requirements.
- Critical Placement Place processor, memory, clocks, power stages, high-speed controllers, M.2 devices, network magnetics, and connectors around electrical, thermal, and enclosure constraints.
- PCB Routing Route high-speed and power networks against the approved constraints while preserving return paths, spacing, length requirements, breakout feasibility, and test access.
- Design & DFM Review Check schematic-to-layout consistency, footprints, clearances, fabrication rules, assembly access, test points, drawings, BOM identity, and revision-controlled output files.
PCB Impedance Calculator → PCB Trace Width Calculator → PCB Via Current Calculator →
Engineering Reference Basis
PCB Quality Requirements Need a Defined Standard and Revision
Quality requirements should be written into the project specification, fabrication data, and acceptance criteria. An IPC reference is useful only when the applicable document, revision, product requirement, and any customer-specific exceptions are defined.
- IPC-2221C
- Generic printed-board design standard used as a basis for PCB design requirements alongside the applicable sectional standard.
- IPC-6012F
- Qualification and performance specification for rigid printed boards, including multilayer and plated-through-hole constructions.
- IPC-A-600M
- 2025 revision of the acceptability standard used for evaluating observable conditions on fabricated printed boards.
- IPC-A-610J
- 2024 acceptability standard for completed electronic assemblies after the PCB enters assembly.
- J-STD-001J
- 2024 requirements covering materials, methods, process control, and verification for soldered electronic assemblies.
- Project-Specific Requirements
- Material system, copper construction, inspection criteria, special tests, documentation, and acceptance requirements are defined for the actual product.
Controlled Design Release
What Leaves the Custom Board Design Stage
A design is ready to leave engineering when the released revision can be identified unambiguously and the prototype team knows both what has been defined in CAD and what still requires physical verification.
Architecture Record
Approved block diagram, platform selection, I/O resource map, storage and expansion topology, power architecture, mechanical constraints, and unresolved prototype risks.
Manufacturing Data
Released schematic, PCB layout, fabrication outputs, assembly data, BOM revision, placement data, drawings, stackup requirements, and board revision identity.
Prototype Check List
Board-level items requiring hardware evidence, such as rail behavior, boot, memory, interfaces, high-speed links, thermal behavior, mechanical fit, and connected peripherals.
The release package becomes the engineering baseline for prototype fabrication, assembly, bring-up, and subsequent validation. Those stages create their own test evidence rather than changing the design record informally.
FAQ
Custom Mini-ITX ODM Engineering Questions
Does Mini-ITX define the processor, memory, or electrical architecture?
No. The Mini-ITX form factor defines the physical board framework, including the 170 × 170 mm size and mechanical compatibility. Processor family, memory architecture, I/O controllers, power design, and most system features remain board-design decisions.
Can an existing operating-system image be retained after a PCB redesign?
Sometimes. Retaining the same processor platform and major controllers can reduce software changes, but a PCB redesign may still alter Ethernet, storage, USB, GPIO, serial controllers, ACPI behavior, device enumeration, or firmware configuration. Driver and OS compatibility must therefore be checked against the final hardware revision.
Can component substitutions be made after the motherboard design is released?
They should be controlled through an engineering-change process. A substitute that appears electrically similar can still change firmware, timing, thermal behavior, signal integrity, qualification status, lifecycle risk, or manufacturing parameters.
Should the enclosure be finalized before PCB layout starts?
The enclosure does not need to be production-released, but the critical mechanical envelope should be stable before placement is frozen. Rear openings, connector locations, mounting points, heatsink interfaces, cable zones, and height limits directly affect PCB placement.
Does a successful schematic review mean the board is ready for production?
No. Schematic review closes logical and electrical design issues at that stage. PCB implementation, fabrication data, prototype bring-up, hardware testing, and applicable system validation still have to demonstrate that the released design works as intended.