How to Choose an NB-IoT Module: Quectel vs u-blox vs Nordic

Why Choosing the Right NB-IoT Module is Important?

A team scopes a water meter product around a Quectel BC66 because a reference design online used it. Three months in, they realize the module has no application processor - every line of business logic needs a separate host MCU, doubling the BOM and the firmware complexity they'd budgeted for. A Nordic nRF9151 would have run the whole application on the module itself.

This is the decision that matters most in NB-IoT module selection, and it's not brand preference. It's whether you want a standalone cellular modem paired with your own MCU, or an integrated System-in-Package that runs your application directly. Get this wrong and you're either paying for integration you didn't need or missing the processor you actually required.

By the end of this NB-IoT module comparison, you'll know which module family fits your architecture - standalone or integrated and how Quectel, u-blox, and Nordic differ within each category.

The Real Split: Standalone Modem vs. Integrated SiP

Before comparing brands, the architecture decision comes first. NB-IoT modules fall into two categories that solve different problems.

Standalone modems - Quectel's BC66/BC65/BC95 family and u-blox's SARA-N series:

• Pure cellular modems that handle the radio connection only

• Require a separate microcontroller running the application logic

• Communicate with the host MCU over AT commands or a serial interface

Integrated SiPs - Nordic's nRF91 series (nRF9160, nRF9161, nRF9151):

• Bundle a full application processor into the same package as the modem

• The nRF9151 includes a 64MHz Arm Cortex-M33 with 1MB flash and 256KB RAM, alongside the LTE-M/NB-IoT modem, GNSS, and RF front-end

• Your application runs directly on the module — no separate host MCU required

Neither approach is universally better:

• A standalone modem is cheaper per unit and lets you pick exactly the MCU your application needs

• An integrated SiP cuts BOM count and simplifies the board, but the MCU that comes with it is what you get, whether or not it matches your compute requirements

Quectel:

Quectel's BC66, BC65, and BC95 modules are pure NB-IoT modems built for cost and power efficiency, not application processing.

• Compact, purpose-built package - the BC65 ships in a 17.7mm x 15.8mm LCC package designed specifically for space-constrained, high-volume products like metering and asset tags.

• PSM_EINT wake feature - lets an external interrupt wake the module from Power Saving Mode without the host MCU having to poll it constantly.

• Footprint compatibility across the family - BC65, BC66, and BC68 share a compatible footprint, so migrating between them as a design evolves doesn't force a full board respin.

• Best fit - application logic simple enough for a small external MCU, and per-unit cost matters more than integration simplicity. The classic case is smart metering, where millions of units need to ship as cheaply as possible.

u-blox:

u-blox's SARA-N series occupies the same standalone-modem category as Quectel, with a similar division of labor.

• Same architecture as Quectel - the module handles the cellular connection, an external MCU handles everything else.

• Mature, well-documented - both Quectel and u-blox are widely-deployed NB-IoT module families with solid AT command documentation.

• Where the real difference lies - carrier certification coverage in your target markets, existing supplier relationships, and which documentation style your firmware team already knows.

• Regional consideration - for products targeting European carrier networks specifically, u-blox's regional certification history is worth checking against your exact deployment countries before committing.

Nordic:

Nordic's nRF9151 takes a fundamentally different approach - a complete System-in-Package rather than a bare modem.

• What's inside - application processor, LTE-M/NB-IoT modem, GNSS, power management, and RF front-end, all in one pre-certified module.

• Power flexibility - supports both Power Class 3 (23dBm) and the newer Power Class 5 (20dBm), cutting peak power consumption by roughly 45% for battery-powered products.

• No separate host MCU - the application runs on the module itself via Nordic's nRF Connect SDK, collapsing two supply chain relationships into one and removing an entire class of modem-to-host integration bugs.

• The trade-off - you're committed to the Cortex-M33's compute capability and Nordic's software ecosystem. Fine for most sensor and metering applications; less ideal if your team has deep firmware expertise in a different MCU architecture.

NB-IoT Module Comparison: Quectel vs u-blox vs Nordic Side by Side

Which Should You Choose?

• Does your application need meaningful onboard processing — sensor fusion, local decision logic, data buffering beyond simple pass-through? If yes, an integrated SiP like the nRF9151 removes a whole processor selection and integration step.

• Is per-unit cost the dominant constraint at high volume, with genuinely simple application logic? A standalone Quectel or u-blox modem paired with a low-cost MCU usually wins here.

• Does your team already have deep firmware expertise in a specific MCU architecture that isn't Arm Cortex-M33? A standalone modem lets you keep that MCU rather than adopting whatever ships inside an integrated SiP.

• What are your target deployment countries? Carrier certification and regional support differ enough between Quectel, u-blox, and Nordic that this should be checked against your actual markets before finalizing a choice, not assumed to be identical across vendors

FAQ on NB-IoT chip Selection

What's the difference between an NB-IoT modem and an NB-IoT SiP?

A standalone modem, like Quectel's BC66 or u-blox's SARA-N, handles only the cellular connection and requires a separate microcontroller for application logic. A System-in-Package, like Nordic's nRF9151, integrates an application processor alongside the modem in one module, so no external MCU is needed.

Is Nordic's nRF9151 more expensive than a Quectel or u-blox module?

Per-module cost is typically higher for an integrated SiP than a bare modem. But the real comparison isn't module-to-module — it's total system cost:

• External MCU cost and sourcing (standalone route only)

• Firmware development for a separate host processor (standalone route only)

• Board space for two chips vs. one

The total BOM and engineering cost can favor either approach depending on application complexity

Can I switch from a Quectel module to a Nordic SiP later in development?

Not without significant rework — these aren't drop-in replacements. A standalone-modem design assumes a separate host MCU handling application logic; an integrated SiP design assumes that logic runs on the module itself. Switching between them means re-architecting the firmware split, not just swapping a part number.

Does NB-IoT module choice affect battery life?

Yes, meaningfully. Power Saving Mode and eDRX support differ in implementation detail across vendors, and Nordic's Power Class 5 option specifically targets reduced peak power consumption for battery-constrained designs. This is worth evaluating against your specific duty cycle and battery budget rather than assumed to be equivalent across all three vendors.

Should a first-time NB-IoT product default to an integrated SiP to simplify development?

For a team without existing standalone-modem and MCU integration experience, an integrated SiP like the nRF9151 generally reduces development risk by removing the modem-to-host integration layer entirely. Teams with established MCU firmware expertise and cost-sensitive, high-volume products often still prefer the standalone-modem route despite the added integration work.

Conclusion

NB-IoT module selection starts with architecture, not brand: standalone modem plus your own MCU, or an integrated SiP running your application on the module itself. Quectel and u-blox both serve the standalone category well, differentiated mainly by regional certification and documentation familiarity. Nordic's nRF9151 is the strongest integrated option when onboard processing and BOM simplicity matter more than picking your own MCU.

If you're scoping an NB-IoT product and aren't sure whether your application needs a standalone modem or an integrated SiP, CoreFragment's team can review your compute and power requirements before you commit to a module family.