Skip to main content
XenonStack

Enterprise Data Management

XenonStack Insights Google Cloud IoT: IoT Core Retired, What to Use Now

and | Published | Updated

Google Cloud IoT: IoT Core Retired, What to Use Now
10:29
Google Cloud IoT after IoT Core: stack from MQTT or HTTPS endpoint through Pub/Sub and stream processing to BigQuery insight.

Key takeaway

  • Google Cloud IoT Core was retired in August 2023. See what Google documents today, how Pub/Sub, Dataflow and BigQuery fit, and how to choose.

What happened to the Google Cloud IoT platform?

Google Cloud IoT Core, the managed service that registered devices and bridged MQTT and HTTP traffic into Google Cloud, was retired. Google announced a retirement date of 16 August 2023, as reported by InfoQ. Google Cloud still offers the building blocks for an IoT platform, but you now assemble them yourself or with a partner.

This guide explains what IoT Core did, what Google Cloud documents today for IoT architecture, and how to choose a path. For the wider design view, read our guides to the IoT analytics platform and IoT edge analytics.

What did Cloud IoT Core do?

IoT Core had two main parts. The device manager registered devices, authenticated them and held a logical configuration for each one. The protocol bridge let devices connect over standard protocols such as MQTT and HTTP, so existing devices needed few firmware changes. Data then flowed to other Google Cloud services for processing and storage. Those functions still need an owner in any IoT design, which is why the replacement question matters.

What does Google Cloud document for IoT now?

Google's IoT platform architecture guide (last reviewed 9 August 2024) says IoT platform products typically provide basic MQTT and HTTPS data connectivity. It describes three parts, shown below.

Two-column diagram mapping IoT Core functions (protocol bridge, device manager, data routing, Android Things) to current parts (MQTT endpoint, device management, Pub/Sub and Dataflow, own device software).
PartWhat the guide describesWhat it means for you
IngestionAn MQTT broker or endpoint, plus an optional HTTPS endpoint, behind an external proxy Network Load BalancerYou run or buy the broker
Backend integrationApplications connect through Pub/Sub or the Dataflow MQTT connector (Apache Beam)Messages reach your processing code
Device managementCredential storage, authentication, configuration, registry and update managementYou or a partner keep the device inventory

The same page links to Intelligent Products Essentials as a related guide for building IoT applications on Google Cloud. Partner platforms are another route: ClearBlade, a Google partner, announced a migration path from IoT Core, as reported by InfoQ.

Which Google Cloud services still fit an IoT pipeline?

ServiceRole in an IoT pipelineStatus and source
Pub/SubDecouples devices or gateways from the services that process messagesCurrent; Pub/Sub overview
DataflowProcesses unbounded streams with the Apache Beam SDK, for example from Pub/SubCurrent; streaming pipelines
BigQueryServerless analysis with SQL and Python, with streaming ingestion and BigQuery MLCurrent; BigQuery introduction
Cloud Run functionsEvent-driven code without server management; Google suggests new functions are created in Cloud RunCurrent under this name; overview
Android ThingsOperating system for IoT devicesTurned down on 5 January 2022; Android Things
Cloud IoT CoreDevice registry and MQTT/HTTP bridgeRetired 16 August 2023, as reported by InfoQ

Pub/Sub, according to its documentation, is an asynchronous and scalable messaging service that decouples producers from consumers, with push delivery to webhooks. Console steps for creating an IoT Core registry no longer apply.

How should you choose a path after IoT Core?

OptionWhen it fitsTrade-off
Self-run MQTT broker in front of Pub/SubYou want control and already run containersYou own broker scaling, security and updates
Partner IoT platformYou want managed device registry and connectivityVendor dependence; check the partner's own pages for terms
Edge processing firstLatency or bandwidth limits make cloud-only designs costlyMore fleet management at the edge
Another cloud's IoT serviceYour estate already runs thereData movement and a second platform to govern

Adopt in this order: define the device identity and credential model, choose the ingestion endpoint, stream into Pub/Sub, process with Dataflow or Cloud Run functions, and land the results in BigQuery. Avoid building new designs on retired services, and avoid cloud-only designs where edge processing is needed. See our guide to edge computing and the use case on IoT for manufacturing.

What do governance, security and cost need?

Each device needs its own identity and credential, with a plan for rotating and revoking them. Decide who may act on device data, and keep an audit trail of automated actions. Costs come from message volume, stream processing and query use, so estimate them with the pricing pages of each service rather than a rule of thumb. Where AI agents act on IoT data, ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents, and NexaStack is an agentic operating platform for physical AI that runs across on-premises, cloud and hybrid environments, according to its site.

What will change in Google Cloud IoT over the next 3 to 5 years?

SignalSourceLikely effect
About 21.1 billion connected IoT devices at the end of 2025, growing 14% a yearIoT Analytics, State of IoT 2025, 28 October 2025More devices per fleet; identity and update management matter more
About 39 billion devices forecast for 2030 (13.2% compound annual growth rate for 2025 to 2030); more than 50 billion by 2035IoT Analytics, State of IoT 2025Ingestion and storage designs must scale without redesign
Google documents a build-your-own pattern (MQTT endpoint, Pub/Sub, Dataflow) in place of a single managed serviceGoogle Cloud IoT platform architecture guide, reviewed 9 August 2024Expect IoT on Google Cloud to stay a composed architecture, with partners for device management
BigQuery describes itself as AI-ready, with in-place model building using SQL or PythonBigQuery introduction, Google Cloud docsAnalytics and models are likely to sit closer to the data

This is an outlook based on the sources above, not a forecast from Google. Confirm product status on the official pages before committing.

To map one IoT decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.

Frequently asked questions

Is Google Cloud IoT Core still available?

No. Google set the retirement of IoT Core for 16 August 2023, as reported by InfoQ. Google's current IoT platform architecture guide does not mention it. Check the Google Cloud documentation for the latest status before planning any design.

What replaces Google Cloud IoT Core?

There is no single drop-in service. Google's IoT platform architecture guide describes an MQTT broker or endpoint for ingestion, Pub/Sub or the Dataflow MQTT connector for backend integration, and separate device management for credentials, registry and updates. Partner platforms such as ClearBlade also announced migration paths, as reported by InfoQ.

Can Pub/Sub receive device data on its own?

Pub/Sub is a messaging service that decouples producers from consumers and works with Dataflow, BigQuery, Cloud Storage and Cloud Run functions, according to its documentation. Google's architecture guide places an MQTT or HTTPS endpoint in front of it for device traffic.

Is Android Things still supported?

No. According to the Android Things page, the console closed to new projects on 5 January 2021 and was turned down for all projects on 5 January 2022.

How many IoT devices will there be by 2030?

IoT Analytics, in its State of IoT 2025 report published on 28 October 2025, forecasts about 39 billion connected IoT devices in 2030, up from an estimated 21.1 billion at the end of 2025.

Where should an enterprise start?

Decide the device ingestion path first (self-run or partner MQTT, then Pub/Sub), then the analytics store, then the governance around who and what may act on the data.

Ready to put AI agents to work? See an ElixirClaw demo: the agentic OS to build, orchestrate and govern AI agents across your enterprise systems.

Table of Contents

navdeep-singh-gill

Navdeep Singh Gill

Global CEO and Founder of XenonStack

LinkedIn profile

Navdeep Singh Gill is serving as Chief Executive Officer and Product Architect at XenonStack. He holds expertise in building SaaS Platform for Decentralised Big Data management and Governance, AI Marketplace for Operationalising and Scaling. His incredible experience in AI Technologies and Big Data Engineering thrills him to write about different use cases and its approach to solutions.

Get the latest articles in your inbox

Subscribe Now

Interested in solving your challenges with the XenonStack team?
Get Started

Tell us about you and your priorities so we can prepare the right conversation. It takes about 2 minutes.

Please Select your Industry
Banking
Fintech
Payment Providers
Wealth Management
Discrete Manufacturing
Semiconductor
Machinery Manufacturing / Automation
Appliances / Electrical / Electronics
Elevator Manufacturing
Defense & Space Manufacturing
Computers & Electronics / Industrial Machinery
Motor Vehicle Manufacturing
Food and Beverages
Distillery & Wines
Beverages
Shipping
Logistics
Mobility (EV / Public Transport)
Energy & Utilities
Hospitality
Digital Gaming Platforms
SportsTech with AI
Public Safety - Explosives
Public Safety - Firefighting
Public Safety - Surveillance
Public Safety - Others
Media Platforms
City Operations
Airlines & Aviation
Defense Warfare & Drones
Robotics Engineering
Drones Manufacturing
AI Labs for Colleges
AI MSP / Quantum / AGI Institutes
Retail Apparel and Fashion

Continue