What is Verizon ThingSpace?
ThingSpace is Verizon's IoT platform for managing cellular connectivity and devices at scale — the place enterprises provision SIMs, control connectivity, and monitor and manage their fleets on Verizon's network.
IoT DEVICE MANAGEMENT
The device-management portal behind Verizon ThingSpace, at estate scale.
Verizon’s ThingSpace is an IoT platform that sells cellular connectivity to enterprises, and those enterprises need to manage their own fleets on it — activating SIMs, changing rate plans, watching usage, chasing a device that has gone silent. That management surface is ThingSpace Manage, and a portal like it is where the platform is judged: the network can be flawless and the product still feels broken if an operator cannot find a device or run a change across ten thousand of them without fear.
CONTEXT
Where this started.
The problem is scale and state. The fleet is measured in millions, not thousands, so every list, search and bulk action is a scale problem; and the data behind each device — connectivity status, session usage, diagnostics — arrives asynchronously and is only ever eventually consistent. A portal that assumes instant, complete state looks right in a demo and misleads in production.
Faststream’s work was to build a management portal that stays fast and truthful at estate scale: a coherent view assembled from lagging data, bulk operations that never leave the fleet in an unknown state, and multi-tenant access so each enterprise sees and touches only its own devices.
CHALLENGES
4 problems, named.
Stated before they had answers.
01
Estate scale, not store scale
The fleet is in the millions. List views, search, bulk actions and usage queries that are instant at a few thousand devices become slow or inconsistent, so the architecture had to be designed for the estate from the start.
02
Device state is live and lagging
Connectivity, usage and diagnostic data arrive asynchronously and eventually consistent. The portal had to present a coherent, clearly-timestamped picture rather than pretend the state was instantaneous.
03
Bulk operations with consequences
Activations, suspensions and rate-plan changes run across thousands of devices at once, each with a billing effect. A partial failure could not be allowed to leave the fleet in an unknown state.
04
Many tenants on one platform
Every enterprise manages only its own devices within the shared platform, so tenant isolation and role-based access had to be correct before anything else was trustworthy.
ARCHITECTURE
How the system was built.
A web portal over a carrier's connectivity-management platform: fleet views, search and bulk operations at the front; device-inventory, connectivity-lifecycle, usage/diagnostics and a tracked bulk-operation engine in the application tier; and integration to the carrier platform's APIs and eventually-consistent event and usage streams beneath. The design point throughout is estate scale and honest, timestamped state.
CONTRIBUTION
What Faststream did.
The specific scope, rather than a capability list.
- Portal architecture — the end-to-end design of a device- and connectivity-management portal built for a fleet in the millions.
- Front-end application — fleet inventory, search, filtering, device detail and dashboard views that stay responsive at estate scale.
- Connectivity lifecycle — activation, suspension, rate-plan and policy changes surfaced as safe, auditable operations.
- Bulk-operation engine — tracked jobs across large device batches with per-device status and partial-failure handling.
- Usage & diagnostics — metering, session-state and diagnostic views reconciled from asynchronous platform streams.
- Multi-tenant access — tenant isolation and role-based access control across enterprise operators.
- Platform integration — integration with the carrier's connectivity-management APIs, event streams and billing/policy data.
WHAT WAS HARD
The parts that consumed the schedule.
Written out because a reader facing the same programme gets more from this than from a summary of what went well.
01
Search and lists at millions of rows
Making inventory search and fleet views feel instant at estate scale drove the data model and indexing, not the UI.
02
Reconciling eventually-consistent state
The portal had to be honest about lag — assembling connectivity, usage and diagnostics into a coherent, timestamped view instead of a falsely live one.
03
Bulk actions that fail cleanly
A rate-plan change across thousands of SIMs must never half-apply; the bulk engine tracks every device and reports partial failure rather than hiding it.
04
Getting multi-tenant RBAC right first
Isolation between enterprises and roles is the thing that has to be correct before any feature on top of it can be trusted.
OUTCOME
What resulted.
A portal that holds up at estate scale
Fleet management — inventory, search, lifecycle and bulk operations — that stays responsive across a device population measured in millions.
Honest, timestamped device state
A coherent view reconciled from asynchronous, eventually-consistent platform data, rather than a falsely instantaneous one.
Safe bulk operations
Large lifecycle changes executed as tracked jobs with partial-failure handling, so the fleet is never left in an unknown state.
Multi-tenant by construction
Tenant isolation and role-based access so each enterprise manages only its own devices.
Disclosed with permission
This programme is described with the customer’s agreement: Verizon and the ThingSpace platform are named here by permission. Internal architecture, data models, interfaces and confidential deliverables remain undisclosed, and figures that would expose them are omitted rather than approximated. Further detail is available under a non-disclosure agreement.
CAPABILITY USED
What this was built from.
Every item links to its own page.
SERVICE
Cloud, OTA & Device Management
Ingest, fleet control, updates, analytics.
PRODUCTSoftware & Frameworks
Device platform, simulator, OTA, analytics.
PLATFORMConnected Edge
Sensors, gateways, links and device cloud.
SOLUTIONConnected Products
Devices that ship, connect and stay managed.
PRODUCTDevice management & OTA
Fleet control and update delivery.
SERVICEEmbedded Software
The device side of the same fleet.
WHERE THIS APPLIES
Industries this serves.
COMMON QUESTIONS
Questions this programme gets asked.
What is ThingSpace Manage?
The device- and connectivity-management application within ThingSpace: the portal used to activate and suspend SIMs, change rate plans, watch usage and connectivity state, run diagnostics and perform bulk operations across an IoT fleet.
What is a connectivity-management portal?
A web application that lets an enterprise manage a fleet of cellular IoT devices on a carrier's network — activating and suspending SIMs, changing rate plans, watching usage and connectivity state, running diagnostics and performing bulk operations, all from one place.
What does IoT device lifecycle management involve?
The full arc of a connected device: provisioning and activation, rate-plan and policy changes, suspension and reactivation, usage and billing visibility, diagnostics when a device goes quiet, and clean deactivation — each step with a billing and connectivity consequence.
Why is estate scale different from store scale?
A portal that works for a few thousand devices can fail quietly at a few million: list views, search, bulk actions and usage queries that were instant become slow or inconsistent. The architecture has to be designed for the estate, not scaled up to it afterwards.
How do you present device state that is always slightly stale?
Connectivity, usage and diagnostic data arrive asynchronously and are eventually consistent. The portal reconciles these streams into a coherent, clearly-timestamped view rather than pretending the state is instantaneous.
How are bulk operations handled safely?
Operations across thousands of devices are executed as tracked jobs with partial-failure handling and per-device status, so an activation or plan change across a large batch never leaves the fleet in an unknown state.
How is multi-tenant access controlled?
Enterprises manage only their own devices within the shared platform, enforced by tenant isolation and role-based access control so an operator sees and acts on exactly what their role permits.
KEEP READING
Related work.
BUILD WITH FASTSTREAM
Bring us the difficult part.
Tell us the platform, the fleet size and the operations that have to stay safe at scale. Device- and connectivity-management portals that hold up at estate scale are core Faststream work.