When an embedded product moves beyond proof of concept, the hardware question usually becomes more specific: should the team design a custom carrier board around an existing compute module, or build a fully custom single board computer?
Both approaches can work. Both can reduce the limitations of off-the-shelf development boards. But they are not the same engineering path, and choosing the wrong one can add cost, schedule risk, or long-term maintenance problems.
This article compares the two options from a product engineering point of view.
What is a custom carrier board?
A custom carrier board is a PCB designed to host an existing compute module, system-on-module, or core board. The compute module usually contains the processor, memory, storage, PMIC, and sometimes wireless or high-speed interfaces. The carrier board exposes the interfaces needed by the final product.
A carrier board may include:
- Power input and protection
- Ethernet, USB, UART, RS485, CAN, GPIO, I2C, SPI, or audio interfaces
- Display and touch connectors
- Camera or sensor connectors
- Wireless module sockets
- Buttons, LEDs, relays, or expansion headers
- Mechanical mounting features
- Connectors positioned for the enclosure
This approach keeps the high-complexity compute section on a proven module while allowing the product team to customize the external interfaces and mechanical layout.
What is a fully custom SBC?
A fully custom SBC integrates the processor, memory, storage, power management, I/O, connectors, and product-specific circuits on one board.
Instead of using a separate compute module, the full board is designed around the selected SoC and the final product requirements.
A fully custom SBC may be better when the product needs:
- A specific board shape or size
- Lower bill of materials at scale
- Direct control over component selection
- Fewer board-to-board connectors
- Optimized thermal design
- Long-term production control
- Custom display, wireless, storage, or industrial interfaces
- Better fit for a fixed enclosure
- A more integrated manufacturing process
This path gives the engineering team more control, but it also increases design responsibility.
The main trade-off
The carrier board approach reduces risk by relying on a ready compute module. The fully custom SBC approach increases control by integrating everything into one board.
In simple terms:
- A carrier board is usually faster and lower risk.
- A fully custom SBC is usually more optimized and more scalable.
- A carrier board keeps the compute design outsourced to the module supplier.
- A fully custom SBC requires deeper hardware and BSP ownership.
- A carrier board may cost more per unit.
- A fully custom SBC may cost more upfront.
The right choice depends on schedule, volume, interface complexity, mechanical constraints, software support, and lifecycle expectations.
When a custom carrier board makes sense
A custom carrier board is often the better first step when the product team wants to move quickly from prototype to pilot production.
It can make sense when:
- The target volume is low or medium.
- Time to market is more important than unit cost.
- The selected compute module already has stable Android or Linux support.
- The product mainly needs custom connectors and I/O.
- The enclosure can support a module-plus-carrier structure.
- The team wants to reduce high-speed design risk.
- The project is still validating product-market fit.
- The compute platform may change in the future.
For example, an IoT gateway may use a proven Linux compute module and a custom carrier board with Ethernet, RS485, CAN, USB, LTE, and power input circuits. This can be practical if the product needs industrial interfaces but does not require a highly optimized board cost.
A display product may also use a compute module with Android support, while the carrier board handles display, touch, speakers, buttons, and enclosure-specific connectors.
Advantages of the carrier board path
The biggest advantage is reduced development risk.
A compute module supplier usually handles many difficult parts of the design, including DDR layout, power sequencing, boot configuration, and basic BSP support. These are areas where mistakes can be expensive.
A carrier board can also simplify certification and debugging because the compute section is already validated. The engineering team can focus on product-specific I/O, power input, mechanical fit, and application integration.
Another advantage is flexibility. If the product may later move to a different processor, the carrier board concept can sometimes be adapted to another module family.
Limitations of the carrier board path
The carrier board approach is not always the best long-term solution.
Possible limitations include:
- Higher unit cost
- Larger total board area
- Board-to-board connector reliability concerns
- Less control over module component choices
- Dependency on module supplier lifecycle
- Limited access to some internal signals
- Mechanical constraints from module placement
- Less opportunity for deep cost optimization
For low-volume or fast-moving projects, these trade-offs may be acceptable. For high-volume products, they may become expensive.
When a fully custom SBC makes sense
A fully custom SBC is often the better path when the product requirements are clear and the expected volume justifies deeper engineering investment.
It can make sense when:
- The product has a fixed mechanical design.
- The board must fit a specific enclosure.
- The product needs cost optimization at scale.
- The interface layout is highly specific.
- The team needs control over component selection.
- Long-term supply planning is important.
- The product will be manufactured repeatedly.
- The module-plus-carrier structure is too large or expensive.
- The project needs a cleaner integrated design.
For example, a wall-mounted control panel may require a specific PCB outline, display connector location, touch panel interface, speaker position, power input, and mounting holes. A fully custom SBC can be designed around the enclosure instead of forcing the enclosure to adapt to a module.
An industrial controller may also benefit from a fully custom SBC if it needs a specific mix of Ethernet, RS485, CAN, GPIO, relays, isolated inputs, power protection, and testing points.
Advantages of a fully custom SBC
The main advantage is product-level optimization.
A fully custom board can remove unused circuits, place connectors exactly where they are needed, reduce assembly complexity, and align the PCB with the enclosure. It can also improve unit cost when volume is high enough.
A fully integrated design can also simplify production. There is one main board instead of a module-plus-carrier assembly. Functional testing can be designed around the final board, and firmware flashing can be integrated into the production process.
For companies building long-life products, a fully custom SBC can also provide better control over component sourcing and lifecycle planning.
Challenges of a fully custom SBC
The main challenge is engineering responsibility.
A fully custom SBC requires careful design around the processor, memory, power, storage, high-speed signals, boot configuration, thermal behavior, and manufacturing test points. BSP work may also be deeper because the board differs more from standard reference designs.
Common project tasks include:
- Schematic design
- PCB layout
- DDR and high-speed routing review
- Power sequencing validation
- Bootloader and kernel adaptation
- Device tree configuration
- Display and touch bring-up
- Wireless module integration
- Functional test development
- Manufacturing validation
This path requires an experienced hardware and software team. If the team does not have that experience internally, working with an embedded board design partner becomes important.
Software and BSP considerations
The hardware path also affects software work.
With a carrier board, the compute module may already provide a usable Android or Linux BSP. The main work may involve enabling peripherals on the carrier board and testing product-specific interfaces.
With a fully custom SBC, BSP work can be broader. The project may require bootloader changes, kernel configuration, device tree updates, driver integration, display tuning, touch setup, wireless module support, and production image preparation.
For both paths, BSP support should be evaluated early. A good hardware design can still fail as a product if the software platform is unstable.
Manufacturing and testing
Manufacturing should be considered before the design is frozen.
For a carrier board, testing may need to verify both the compute module connection and the carrier board interfaces. The factory process may include module installation, board-to-board connector inspection, firmware flashing, and final functional testing.
For a fully custom SBC, the test process can be more integrated. The board can include test points, programming interfaces, and fixture support designed for production.
In both cases, testing should cover the interfaces that matter to the product, not just basic power-on behavior.
Practical decision checklist
A carrier board may be the better choice if:
- You need a faster prototype-to-pilot path.
- Your volume is not high enough to justify a full custom SBC.
- You want to reduce processor and memory design risk.
- A ready compute module already meets performance needs.
- Your main customization is connector and interface layout.
A fully custom SBC may be the better choice if:
- Your product has strict mechanical constraints.
- You need lower unit cost at scale.
- You want full control over component selection.
- You need a cleaner integrated design.
- The product will be manufactured over a long lifecycle.
Final thoughts
There is no universal answer. A custom carrier board and a fully custom SBC solve different problems.
A carrier board is useful when speed, risk reduction, and platform reuse are important. A fully custom SBC is useful when integration, cost optimization, mechanical fit, and lifecycle control become more important.
For teams building industrial devices, smart terminals, IoT gateways, HMI panels, or connected equipment, the best path depends on the maturity of the product requirements and the expected production plan.
Companies such as Avontek support embedded hardware projects from standard SBC evaluation to Custom SBC development, including Android and Linux BSP support, display and touch integration, I/O customization, manufacturing, and functional testing.
Top comments (0)