if (your_platform && raw_gps_data)HaaSif (our_platform && integrate_or_automate)API

Hardware is Hard.
We Solved It.

Want GPS devices sending real-time data into your platform? We deliver everything you need in one clean JSON stream: load balancing, firmware and chip differences, inventory, supply chain, and cellular connectivity. All handled. All included.

Think of it as AWS for GPS hardware.

stream.jsonHardware as a Service
{
timestamp : "2026-04-27T14:32:07Z"
device.id : 5963284
position.latitude : 39.89667
position.longitude : -86.26265
position.altitude : 248
position.speed : 62
position.direction : 274
position.hdop : 0.8
movement.status : true
battery.level : 91
battery.voltage : 4.07
gsm.signal.level : 78
gsm.signal.dbm : -67
wifi.mac.address : "A4:C3:F0:85:7C:B2"
wifi.signal.strength : -72
position.satellites : 11
gnss.jamming.status : false
vehicle.mileage : 48293
harsh.braking.event : false
harsh.acceleration.event : false
geofence.status : true
can.engine.rpm : 1840
can.fuel.level : 73
// 1,800+ fields available — request full schema
}
12+device types·
1JSON schema·
0firmware issues·
0inventory
21yrs
Hardware Expertise
600K+
Devices Deployed
$2M+
US Warehouse Inventory
3+
Major Carriers Covered
2-Day
Shipping from Indiana
Time to Live

From Discovery Call to Live Data: Weeks, Not Months.

The typical path from first conversation to devices streaming data into your platform is 2 to 4 weeks. Compare that to the DIY alternative.

Building It Yourself
Weeks 1-4
Evaluate and select hardware vendors
Weeks 4-8
Negotiate MOQs and place first order
Weeks 8-20
Wait for overseas production and shipping
Weeks 20-24
Configure firmware and test devices
Weeks 24-28
Source and activate SIMs, negotiate carrier contracts
Weeks 28-32
Build protocol parsers for each device type
Week 32+
First device live in your platform
Total: 7 to 9 months before you ship a single device
With BrickHouse GPS
Day 1
Discovery call with a solutions engineer
Days 2-5
Hardware recommendation and configuration spec
Days 5-10
Devices configured, activated, and shipped from Indiana
Days 10-14
You build your webhook listener
Week 2-3
Integration tested and validated
Week 3-4
First device live in your platform
Total: 2 to 4 weeks. Same result. No hardware team required.
The Real Problem

We Handle the Hard Part.

Hardware. Cellular. Firmware. One JSON stream. Everything else is our problem.

What BrickHouse GPS delivers
Hardware, shipped to your customers
12+ device types across four families. Stocked in our US warehouse, shipped white-label under your brand.
Cellular connectivity, already activated
Every device ships with an active SIM. Our SIMs carry contracted coverage across all major and regional US carriers. No carrier contracts for you to sign.
Firmware configured to your specs
Reporting intervals, power profiles, geofence parameters. All set before the device ships. OTA updates managed by our team.
One clean JSON stream
Every device, every hardware family, same schema. Build your integration once. It works for everything.
What you never have to deal with
Factory relationships and MOQs
Overseas manufacturers require minimum order quantities, NDA negotiations, and months of qualification. We have 21 years of those relationships already in place.
Chip configuration and firmware builds
Every chipset family has its own toolchain, reporting intervals, and protocol quirks. We configure all of it before the device ships. You never touch a firmware build.
Protocol fragmentation across device types
OBD-II, hardwire, battery, solar. Each hardware family uses different native formats. We normalize everything into one schema. Your parser never breaks.
Carrier contracts and SIM management
Our SIMs carry contracted coverage across all major and regional US carriers. Connectivity is built in. You never sign a carrier agreement or manage a SIM pool.
Supply chain risk and lead times
Overseas production means 4-month lead times on a good day. We warehouse in the US and ship within days. Supply chain risk stays on our side of the table.
Ongoing OTA updates and device health
Firmware bugs don't stop after launch. We manage OTA updates, device health monitoring, and hardware support for your entire deployed fleet.

BrickHouse GPS has spent 21 years building the infrastructure, relationships, and expertise to handle every layer of this stack. You skip straight to the JSON.

The Comparison

The Real Cost of Going It Alone.

Every workstream you own. Every risk you carry. Until now.

Factory and manufacturer relationships
DIY
You build them from scratch
BrickHouse
21 years of relationships, already in place
Minimum order quantities
DIY
Tied to factory MOQs
BrickHouse
Order exactly what you need
Lead time from order to deployment
DIY
4+ months overseas
BrickHouse
Ships from US warehouse in days
Chip configuration and firmware
DIY
Requires a firmware engineer
BrickHouse
Configured and managed by us
OTA firmware updates
DIY
You build the update system
BrickHouse
Automated by our team
Protocol parsing per device type
DIY
Custom parser per hardware family
BrickHouse
One JSON schema, all devices
SIM provisioning and management
DIY
Source SIMs, activate, manage pool
BrickHouse
Active SIMs included with every device
Cellular coverage and roaming
DIY
Negotiate carrier contracts yourself
BrickHouse
Contracted coverage on all major and regional carriers
Inventory and warehousing
DIY
Capital tied up in stock
BrickHouse
We warehouse, monthly per device
White-label fulfillment to end users
DIY
You build a fulfillment operation
BrickHouse
Blind shipped under your brand
Device support and troubleshooting
DIY
Your support team handles it
BrickHouse
Our hardware team handles it
Supply chain risk
DIY
Fully on you
BrickHouse
Fully on us
Who Is This For?

Which One Are You?

Add GPS hardware to your platform without hiring a hardware team.

You're a developer at a software company that needs location or asset tracking functionality. You know exactly what data you need. You just don't want to spend 18 months sourcing hardware, negotiating with carriers, and debugging firmware before you can write a single line of application code. BrickHouse GPS gives you a clean JSON stream from day one. Your integration is one webhook. Everything else is our problem.

What This Means for You
  • Ship your hardware feature in weeks, not quarters
  • One API schema regardless of which device your customers use
  • No firmware engineers, no carrier contracts, no warehouse ops
  • Scale device volume without changing your integration
Get Your Data Stream →
The Hardware

12+ Devices. One Schema.

Every device in our lineup, regardless of connection type or chipset, delivers the same JSON schema to your webhook. Build your integration once. It works for all of them.

Vehicle Trackers
LiveWire Volt
LiveWire Volt
Bluetooth
2-Wire Install
The simplest hardwired install — two wires to any live voltage source (battery, fuse box, or accessory wire). Always-on tracking with no ignition dependency.
LiveWire Dash
LiveWire Dash
3+ Wire Install
Adds ignition sensing so you know exactly when a vehicle starts and stops. Supports external sensors and remote engine shutoff. More wires, more control.
LiveWire Pro
LiveWire Pro
3+ Wire + CAN Bus
Everything the Dash does, plus direct CAN bus integration for deep vehicle diagnostics — fuel level, engine hours, fault codes, and more. Supports the widest range of external sensors.
TrackPort
TrackPort
OBD-II Plug-In

Plugs directly into the OBD-II or J1939 port. No installation required. Three models:

TrackPort 4 — standard GPS tracking
TrackPort Pro — engine diagnostics + fuel data
TrackPort Pro MAX — ELD compliance + Bluetooth
Asset Trackers
EON Odyssey
EON Odyssey
Long-Life Battery
Monitor assets left in the field for years. Rugged, weatherproof, and built for generators, trailers, and heavy equipment that don't connect to vehicle power.
EON TailLight Tracker
EON TailLight Tracker
Self-Charging Trailer
Covert trailer tracking that charges itself from the trailer's taillight connection. No battery management. No recharge schedules.
Spark Nano
Spark Nano
Battery / Covert
Compact, magnetic-mount battery tracker. Ideal for covert tracking and portable asset monitoring where a hardwired install isn't possible.
MotoTrack
MotoTrack
Bluetooth
Wired + Backup Battery
Wires into vehicle or asset power but includes a long-lasting internal backup battery that keeps tracking for several months if external power is cut or the asset sits idle.
Dash Cameras — VizTrack
VizTrack Road-View
VizTrack Road-View
Forward-Facing HD
Captures the road ahead in HD. Footage syncs with GPS data for instant incident context and driver exoneration.
VizTrack Dual-View
VizTrack Dual-View
AI Dual-Facing
Road-facing and driver-facing cameras in one unit. AI detects distraction and fatigue in real time and alerts before incidents happen.
if (your_platform && raw_gps_data)HaaSif (our_platform && integrate_or_automate)API
Two Ways to Work With Us

Two Ways In. One Hardware Layer.

Not a remote-control API. Two distinct options. Run both at once if you want.

Option A: Hardware as a Service

Your platform. Our hardware layer.

Your end users interact exclusively with your software. BrickHouse GPS is completely invisible. We ship the hardware, manage cellular, configure firmware, and stream clean JSON to your webhook. You build the product. We handle everything underneath it.

  • Your brand, your UI, your product
  • BrickHouse GPS is invisible to your customers
  • You handle your own customer support
  • One webhook. One schema. All devices.
Option B: Platform API Integration

Your software + our telematics platform.

Your end users get a login to the BrickHouse GPS telematics platform, which can be white-labeled under your brand. Our API passes data between your software and our platform so both stay in sync. Your customers get our full feature set (maps, alerts, reports, history) while your software handles the rest of their workflow.

  • White-label available under your brand
  • We handle tech support if branded BrickHouse GPS
  • You handle tech support if white-labeled
  • Your customers access our full feature set
You can use both simultaneously, or migrate between them over time.

Once devices are deployed in the field, the same data stream can be forked to send data to two places at once: our platform and your platform simultaneously. This means you can go live immediately using our platform's full feature set while you build your own product in parallel. As you add functionality to your platform, your customers migrate over on their own timeline. The same devices, the same data stream, zero hardware changes required.

How It Works

Three Steps to Live Data

01
Tell us what you need
Share your use case, device preferences, reporting frequency, and volume. We'll recommend the right hardware and configure it to your specs before it ships.
02
We ship. You receive.
Configured, activated devices ship from our Indiana warehouse, white-labeled under your brand if needed. No factory negotiations. No overseas lead times. No SIM activation.
03
Point us at your webhook
Give us your listener URL. We configure the data stream to POST to your endpoint. You return a 200. Clean JSON starts flowing. Your integration is live.
Integration

One Webhook. That's It.

Integrating with BrickHouse GPS HaaS is intentionally simple. You build a single HTTP listener. We point the data at it. You never touch another piece of the stack.

HTTP POST to your listener
Give us your endpoint URL. We configure the data stream to POST JSON to your handler. Each request contains one or more device messages in the body. You parse, store, and respond with 200. That's the entire integration.
We handle load balancing
You don't need to worry about 10,000 devices hammering your listener simultaneously. We manage load balancing on our side and deliver a clean, metered stream to your endpoint. Your infrastructure stays predictable.
No data loss if you go offline
If your listener goes offline, we buffer the data on our end. When your server comes back online, we resume delivery from where we left off. No gaps, no lost events, no manual recovery required.
Your integration: the complete picture
BrickHouse GPS HaaS
12+ device types
All major carriers
Load balanced
Buffered delivery
POST
JSON body
Your Platform
POST /handler
// parse body
// store to DB
return 200
Your Data. Full Stop.

We move your data. We don't keep it.

Every data packet from your devices passes through our servers on its way to yours. We cache it only long enough to confirm you received it, then we delete it. We don't store your data, share it, sell it, or use it for any other purpose. It's your data and it goes where you tell it to go.

We don't store it
Deleted on confirmed delivery
We don't share it
No third-party access, ever
We don't sell it
Your data has no value to us beyond getting it to you
See how it works in the FAQ below
What Builders Say

Built by Developers. Trusted by Platforms.

Software teams use BrickHouse GPS to power their location-aware products without building a hardware team.

★★★★★

"Coming soon. We are collecting quotes from our current HaaS customers."

Customer Name
Title, Company
★★★★★

"Coming soon. We are collecting quotes from our current HaaS customers."

Customer Name
Title, Company
★★★★★

"Coming soon. We are collecting quotes from our current HaaS customers."

Customer Name
Title, Company
Pricing

Less Than Building It Yourself. Faster Than Anything Else.

The question is not what we cost. It's what it costs to do this without us. A hardware engineer, firmware developer, carrier account manager, and warehouse operation are fixed costs you carry forever. Our per-device monthly model means you only pay for what you deploy, at our scale.

Always cheaper than building in-house
A hardware engineer, firmware developer, carrier account manager, and warehouse operation are fixed costs you carry forever. Our per-device monthly model means you only pay for what you deploy, at our scale.
Always faster. to market and to your customers
Overseas hardware takes 4+ months from order to deployment. Our Indiana warehouse ships configured, activated devices within days. Your customers get hardware faster. Your revenue starts sooner.

Tell us about your deployment and we'll build your exact quote on the discovery call.

1. Device Type
Need diagnostic data? CAN bus / OBD fault codes
2. Reporting Frequency
3. Device Volume
4. Fulfillment

Make your selections above to unlock your quote.

Common Questions

Device protocols, HaaS, and the Locate GPS API. What's the difference?

What is a device protocol, and do I need to know it?+

Every GPS device has its own firmware-level language for sending data to a server and receiving commands. The format is unique to each device and each firmware version. If you integrate directly with a device, you have to parse its specific data format, learn its command set, and maintain that integration as firmware changes. This is the hard path. When you use BrickHouse GPS HaaS, you never touch a device protocol. We handle all of that on our end and send you one clean, normalized JSON stream regardless of which device is in the field.

What exactly is Hardware as a Service (HaaS)?+

HaaS is the simplest integration path. You create a webhook listener on your platform — a URL that accepts an HTTP POST. We push a unified JSON payload to that endpoint every time a device reports. The data schema is identical regardless of which device type is in the field. You don't need to know anything about GPS hardware, cellular carriers, firmware versions, or device protocols. Optionally, you can send commands back through our system to change device behavior, but that is not required to get started.

What is the Locate GPS API, and is it the same as HaaS?+

No — they are separate offerings. The Locate GPS API is for companies that are using or reselling our Locate GPS platform. It lets you connect an ERP or other software to Locate, automate actions inside the platform such as creating geofences and alerts, and manage devices at scale without logging in manually. For example, you could provision hundreds of devices, update alert thresholds, or export trip history — all via API calls. HaaS, by contrast, is for companies building their own platform who want the raw GPS data pushed directly to them. Most customers use one or the other, not both.

When would someone use both HaaS and the Locate GPS API at the same time?+

This is uncommon, but it happens during platform migrations. If you are currently reselling Locate GPS to your customers and you are building your own in-house platform to eventually replace it, you might run both in parallel during the transition. Your customers continue using Locate GPS while your new platform receives the same raw data via HaaS. Once your platform is ready, you migrate customers over and wind down the Locate GPS side. Same devices, same data stream — no hardware changes required.

What happens to my data? Does BrickHouse GPS store it?+

No. With HaaS, your data passes through our servers in transit to yours. We cache each packet only long enough to confirm your endpoint received it, then we delete it. We do not store your data, share it with third parties, sell it, or use it for any purpose other than delivering it to you. This is different from our Locate GPS platform, which does store data on your behalf so you can run reports and view history. With HaaS, the data is yours and it goes where you tell it to go. We are just the pipe.

Skip the Hardware Problem.
Ship Your Product.

Fill out the form and one of our integration experts will reach out within one business day. Tell us what you're building and we'll tell you exactly how we can support it.

You've seen the problem. You've seen what we deliver. The next step is a single conversation with one of our solutions engineers, someone who has done this integration dozens of times and can tell you in 30 minutes exactly what your deployment looks like, what it costs, and how fast you can be live.

No pitch. No deck. Just a technical conversation about your platform and a detailed quote.

Talk Tech to Tech

Tell us what you're building. We'll connect you with one of our solutions engineers for a discovery call. No sales pitch. Just a technical conversation about fit and a detailed quote.

Select all that apply.
Data stream to my own platform only
We build everything. Your customers never see BrickHouse GPS
BrickHouse GPS platform for my customers
Your customers log into our platform (can be white-labeled)
Both simultaneously
Fork the stream. Run both options at the same time or migrate over time
What happens next
We review your submission and schedule a discovery call with one of our solutions engineers, typically within one business day. The call is technical: bring your questions about the data schema, webhook setup, device specs, and pricing. We will give you straight answers and a detailed quote.