Wiliot vs Hubble: Why Gateway Infrastructure Decides Your Asset Tracking Architecture

Every vendor comparison you’ve read about asset tracking focuses on the wrong layer. Tag cost per unit, cloud dashboard features, energy harvesting specs: these get the attention. But there’s a question nobody’s spreadsheet answers early enough: what does it cost to build and maintain the invisible layer between your tags and your data?

That layer, the gateway infrastructure, is where deployments succeed or quietly bleed money for years. A $0.10 tag is meaningless if it requires a $2,000 gateway every 30 meters to read it. And a brilliant cloud platform doesn’t help when your assets leave the building and vanish from visibility.

If you’re comparing Wiliot vs Hubble for supply chain asset tracking, the tag specs are a sideshow. The real fork in the road is architectural: do you build a gateway mesh everywhere you want visibility, or do you subscribe to a network that already covers the planet?

This piece breaks down both architectures on their actual cost and coverage merits, with numbers.

Wiliot’s Ambient IoT Innovation, and the Bridge It Depends On

Credit where it’s due: Wiliot built something genuinely novel. Their IoT Pixel is a passive BLE tag, no battery, thin as a postage stamp, powered by harvesting ambient RF energy. At scale, tag costs push toward commodity pricing. For high-volume use cases like pallet-level tracking or item-level retail inventory, the tag economics are compelling.

But the tag is only half the system. Wiliot’s architecture requires a proprietary gateway called the Wiliot Bridge. These bridges listen for BLE signals from nearby tags, decode them, and backhaul the data to Wiliot’s cloud platform. Each bridge needs power (AC outlet or PoE), network connectivity (Ethernet or Wi-Fi), and physical mounting at the right density to ensure consistent tag reads.

That density requirement is where the math changes. BLE read range for passive tags is limited, typically 3 to 10 meters depending on environmental conditions. In a warehouse environment with metal shelving, concrete walls, and RF interference, you may need a bridge every 5 to 8 meters for reliable coverage. A 10,000-square-meter warehouse could require dozens of bridges, each one requiring power, networking, and commissioning.

None of this invalidates the tag innovation. But it means the tag is only as useful as the gateway mesh supporting it. Every square meter of visibility demands infrastructure investment. And that investment follows you, or rather, doesn’t follow you, to every new site, every outdoor yard, and every mile of transit in between.

This is not unique to Wiliot. Any BLE-based asset tracking system, whether built on Kontakt.io beacons, Aruba gateways, or Cisco Spaces, inherits the same fundamental constraint. The gateway dependency is architectural, not vendor-specific. Wiliot simply brings it into sharper focus because their tag is so inexpensive that the gateway cost ratio becomes especially stark.

How Hubble Eliminates the Middle Layer Entirely

Hubble Network takes a structurally different approach. Instead of relying on local gateway infrastructure to relay tag signals, Hubble’s tags and sensors communicate directly to satellite and terrestrial networks. There are no bridges, no gateways, no local hardware to install, power, or maintain.

The core technical achievement: Hubble has enabled standard Bluetooth signals to reach low-earth-orbit satellites. This means a BLE-class device, small, low-power, low-cost, can report its location and sensor data from essentially anywhere on Earth without intermediary hardware on the ground.

The coverage profile this unlocks is fundamentally different. Indoor warehouses, outdoor staging yards, trucks in transit, ocean containers, remote distribution points, third-party facilities where you have no installation rights: all covered by the same network. You don’t build the infrastructure. You subscribe to it.

Hubble’s connectivity model is pay-per-usage: you pay for the messages and assets you actually track. No upfront infrastructure capital. No networking. No maintenance contracts. The network is the infrastructure, and it’s already deployed.

The Gateway Tax: TCO Across Five Dimensions

This is where the comparison stops being theoretical and starts being financial. Here’s total cost of ownership across the five categories that matter most.

Upfront infrastructure is the most visible cost, but also the most underestimated. A single Wiliot Bridge is a modest expense. But a deployment-ready installation includes the bridge hardware, mounting, electrical work (or PoE switch upgrades), network provisioning, and commissioning labor. Multiply that by 40–80 bridges per large facility, and you’re looking at a substantial capital outlay before a single asset is tracked.

Ongoing maintenance is where gateway costs compound rather than simply add up. More gateways mean more firmware to manage, more hardware that can fail, more network connections to monitor, and more IT tickets when something goes down. A 50-bridge pilot is manageable. A 5,000-bridge global rollout across 60 sites is a different operational reality, one that requires dedicated headcount.

Scaling to new sites exposes the linear trap. Every new warehouse, distribution center, or regional hub requires the full infrastructure buildout repeated from scratch. There’s no carryover from your previous deployment; each site starts at the same cost floor. With Hubble, adding a new site means onboarding new tags. The network is already there.

In-transit and outdoor coverage is arguably the most consequential gap. Assets on trucks, ships, or rail cars have no gateway infrastructure. Outdoor yards and staging areas require weatherproof installations with independent power and connectivity, both expensive and fragile. With a gateway-dependent architecture, you’re tracking assets inside your four walls but flying blind everywhere else. Hubble’s satellite coverage makes transit visibility a default feature, not a special project.

IT and operations overhead accumulates quietly. Gateway networks need monitoring dashboards, security patching, access controls, and integration with your existing IT stack. Each bridge is a network endpoint, and your security team will want it treated like one. Hubble’s cloud-native model shifts this burden entirely to the network provider.

Here’s the cost trajectory over time:

  Cost ($)
    |
    |         Wiliot (gateway-dependent)
    |        /
    |       /  <-- Each new site adds infrastructure cost
    |      /
    |     / _ _ _ _ _ _ _ _ _ _ _
    |    / /
    |   / /   Hubble (gatewayless)
    |  / /     <-- Cost scales only with assets tracked
    | / /
    |/_/__________________________ Time / Scale
    Year 1    Year 2    Year 3    Year 5

The gap widens every year. What looked like comparable costs in a single-site pilot becomes a dramatic divergence at multi-site scale.

Where Gateways Hit Their Coverage Ceiling

Gateway dependency isn’t just a cost problem. It’s a coverage strategy problem. There are entire categories of high-value tracking scenarios that gateway-dependent systems structurally cannot address:

In-transit visibility. Your pallet is tracked perfectly inside your DC. It loads onto a truck and disappears for 48 hours. It reappears at the destination, if that facility also has gateway infrastructure. The gap in between is where theft, spoilage, and delays happen undetected.

Third-party facilities. You can’t install gateways in a partner’s warehouse, a co-packer’s facility, or a 3PL’s cross-dock. You either negotiate infrastructure rights (slow, expensive, politically fraught) or accept a coverage gap.

Outdoor and yard operations. Container yards, staging areas, construction laydown yards: these are large, open, weather-exposed environments where gateway deployment is expensive and maintenance-intensive. Many organizations simply skip outdoor coverage and accept the blind spot.

Temporary or remote operations. Pop-up distribution during peak season, disaster response staging, field operations in areas without fixed infrastructure: these scenarios don’t have gateway answers at any cost.

Hubble’s satellite and terrestrial network covers all of these natively. The coverage boundary isn’t your facility wall. It’s the planet.

Choosing the Right Architecture for Your Operation

The honest framework:

GATEWAY-DEPENDENT (Wiliot) MAKES SENSE IF:
  → Single, controlled indoor facility
  → Existing BLE gateway infrastructure already deployed
  → Assets never leave your four walls
  → Small-scale pilot with no multi-site scaling plans

GATEWAYLESS (Hubble) MAKES SENSE IF:
  → Multi-site or global operations
  → Assets move between facilities and in transit
  → You lack or don't want on-premise IT infrastructure
  → 3-to-5-year TCO matters more than pilot-phase cost
  → You need visibility in locations you don't own or control

For a single-facility, indoor-only use case with existing network infrastructure, Wiliot’s tag economics can work in your favor. That’s a real scenario, and it’s fair to acknowledge it.

But if you’re a VP of Supply Chain managing assets across multiple DCs, third-party logistics partners, in-transit legs, and global distribution, the calculus is unambiguous. Building and maintaining gateway infrastructure at every point of visibility is an ongoing drag on budget, IT resources, and deployment speed.

Making the Infrastructure Decision That Scales With You

The gateway question isn’t a footnote in your vendor evaluation. It’s the architectural decision that sets your cost trajectory, defines your coverage ceiling, and determines how fast you can expand visibility to new sites and scenarios.

Wiliot built a genuinely innovative tag. But pairing a low-cost tag with high-cost infrastructure creates a mismatch that grows more pronounced as you scale. Hubble’s approach flips the model: subscribe to the network, deploy the tags, get visibility everywhere your assets go.

If you’re building a business case for enterprise asset tracking, model both architectures honestly. Account for infrastructure at every site. Account for transit gaps. Account for the IT team’s time. Then compare the five-year numbers.

If you want help building that model for your specific operation, request an architecture assessment from Hubble. Bring your site count, your asset volumes, and your coverage requirements, and see what the gatewayless path actually looks like.

Hubble Network connects your assets to satellite from a single Bluetooth tag—no gateways, no infrastructure buildout. See how it works →