Google Cloud IoT is a set of managed services (Pub/Sub, Dataflow, BigQuery, Cloud Run and Vertex AI) that ingest, process and analyze device data. Since Google retired IoT Core, teams assemble these services into a device, gateway and cloud architecture.
Key takeaways
- Definition: Google Cloud IoT is a modular stack of managed services for ingesting, processing and analyzing device data.
- IoT Core: Google retired IoT Core, so devices connect through an MQTT broker that forwards data to Pub/Sub.
- 5 steps: Design, connect, ingest, process and apply ML: 5 steps carry data from device to insight.
- Cost: Pub/Sub, Dataflow, BigQuery and Cloud Run charge for consumption, with no idle infrastructure.
- Dev Station: Dev Station builds IoT backends on GCP for US and UK clients.
What is Google Cloud IoT after the retirement of IoT Core?
Google Cloud IoT is now a set of standalone managed services (Pub/Sub, Dataflow, BigQuery, Cloud Run, and Vertex AI) that together ingest, process, and analyze device data. Google retired the integrated Cloud IoT Core service, so the current approach assembles these services into a layered device, gateway, and cloud architecture. Modularity means each component scales and is priced independently.
Managed, serverless foundation
Core ingestion, processing, and analytics services are fully managed, so you never provision or patch the underlying infrastructure.
Modular best-of-breed stack
Mix Pub/Sub, Dataflow, BigQuery, Cloud Run, and Vertex AI. Each component scales and is priced independently.
Built for data-driven IoT
The data analytics and AI heritage of GCP suits turning high-volume device telemetry into action.
How do you build an IoT solution on Google Cloud in five steps?
Define the architecture, connect devices, ingest data with Pub/Sub, process it with Dataflow into BigQuery, and derive insight with Vertex AI. The steps bring an IoT project to life on GCP, on top of a sound IoT architecture.
- Design the IoT architecture. Follow a layered model: the device layer for data collection, the gateway layer for secure connectivity, and the cloud layer for data processing and analysis. For instance, a smart agriculture solution might use soil sensors (device layer) connecting via a LoRaWAN gateway (gateway layer) to GCP services (cloud layer). Each part can then be optimized independently.
- Securely connect and manage devices. Devices connect over MQTT, a lightweight messaging standard suited to IoT. Because Google Cloud IoT Core has been retired, run an MQTT broker (self-managed or from a partner) that forwards messages to Cloud Pub/Sub, and replicate device authentication with JSON Web Tokens and device registries in a custom or partner solution.
- Ingest streaming data. Cloud Pub/Sub is a fully managed, real-time messaging service for data ingestion. It decouples data producers (your devices) from data consumers (your processing applications), which creates a scalable and resilient pipeline that keeps messages even when downstream systems are briefly unavailable.
- Process and analyze IoT data in real time. Cloud Dataflow is a unified stream and batch processing service. Pipelines read from Pub/Sub, transform the data, and write it to a destination, and BigQuery, the serverless data warehouse of Google, holds the data for long-term analytics. A common job calculates 5-minute average temperature readings from a sensor stream and flags anomalies before storing the aggregates.
- Apply AI and machine learning. With data in BigQuery, Vertex AI, the unified machine learning platform of Google, trains models with AutoML or custom TensorFlow code. A typical application is predictive maintenance, where a model trained on historical sensor data learns the signatures that precede a failure, such as a vibration pattern combined with a temperature rise.
Which Google Cloud services make up the IoT stack?
Five core services make up the stack: Pub/Sub, Dataflow, BigQuery, Cloud Run, and Vertex AI. All three major clouds offer solid IoT capabilities with different strengths: Google Cloud is strongest in data analytics, machine learning integration, and serverless compute, AWS offers a mature and broad feature set, and Azure provides strong enterprise integration.
| Service | Role in the IoT solution | Key benefit |
|---|---|---|
| Cloud Pub/Sub | Global, real-time data ingestion | Scalability and reliability |
| Cloud Dataflow | Stream and batch data processing | Serverless and automated scaling |
| BigQuery | Data warehousing and analytics | Fast SQL queries on large datasets |
| Cloud Run | Running containerized applications | Pay-per-use serverless compute |
| Vertex AI | Machine learning model development | Unified platform for building and deploying models |
| Feature | Google Cloud (GCP) | Amazon Web Services (AWS) | Microsoft Azure |
|---|---|---|---|
| Core IoT service | Pub/Sub (ingestion) | AWS IoT Core | Azure IoT Hub |
| Data analytics | BigQuery and Dataflow | Kinesis and Redshift | Stream Analytics and Synapse |
| Machine learning | Vertex AI | SageMaker | Azure Machine Learning |
| Strengths | Data, AI, and serverless compute | Mature, broad service catalog | Strong enterprise integration |
How do you migrate an IoT solution to Google Cloud?
Migrate in four phases, assess, plan, execute, and validate, and run the new GCP system in parallel with the old one until the cutover. The approach applies to a move from an on-premise gateway, another cloud provider, or a re-architecture after the IoT Core retirement.
- Assess. Document the existing architecture, including device protocols, data formats, processing logic, and application integrations. Identify all dependencies.
- Plan. Design the target architecture on GCP and a data migration plan that covers historical data and the redirection of real-time streams.
- Execute. Set up the GCP infrastructure, then migrate a small, non-critical subset of devices first. Redirect data streams and migrate historical data.
- Validate. Test the new system and compare performance, data accuracy, and functionality against the old one. Decommission the legacy infrastructure once validated.
Predictive maintenance
Train models on historical sensor data to predict machinery failures, for example a vibration pattern plus a temperature rise that forecasts a bearing failure.
Fleet tracking
Large fleets sending frequent location updates produce a high message rate, which Pub/Sub ingests while Dataflow and BigQuery handle processing and analysis.
Smart agriculture
Soil sensors connect via a LoRaWAN gateway to GCP, where Dataflow computes average readings and flags anomalies before warehousing in BigQuery.
How is IoT security handled on Google Cloud?
Security on GCP is layered across device identity, encryption in transit, key management, and access control, because each device is a potential attack surface. Google Cloud holds certifications relevant to IoT workloads, including ISO/IEC 27001, SOC 2, SOC 3, HIPAA, and PCI DSS.
| Security layer | Mechanism | What it protects |
|---|---|---|
| Device authentication | JWTs, per-device keys, mutual TLS | Ensures only registered, verified devices publish data |
| Network security | VPC Service Controls, private Google access | Keeps telemetry traffic off the public internet where possible |
| Key management | Cloud KMS (HSM-backed keys) | Centralized encryption key lifecycle and rotation |
| Access control | Cloud IAM with least-privilege roles | Restricts who and what can read, write, or process data |
| Secrets and tokens | Secret Manager | Secure storage for API keys, service-account credentials, and device tokens |
After the IoT Core retirement, device registry and certificate-rotation functions must be replicated with custom solutions on GCP or partner-managed MQTT brokers. Automated rotation and revocation are essential for a secure fleet at scale.
How much does Google Cloud IoT cost?
Cost follows consumption, because Pub/Sub, Dataflow, BigQuery, and Cloud Run charge only for what you use, with no idle infrastructure cost. The table lists the pricing model and the typical IoT cost driver for each service.
| Service | Pricing model | Typical IoT cost driver |
|---|---|---|
| Cloud Pub/Sub | Per GB of data ingested | Telemetry volume from connected devices |
| Cloud Dataflow | Per vCPU-hour, memory, and shuffle | Streaming pipeline uptime and throughput |
| BigQuery | Storage per GB per month plus analysis per TB scanned | Telemetry retention and query frequency |
| Cloud Run | Per vCPU-second and memory-second | Container invocations triggered by device events |
| Vertex AI | Per training-hour and per prediction | Model training frequency and inference volume |
To control BigQuery costs, use partitioned tables and cluster on device IDs, schedule long-running analytics during off-peak hours, and cap query bytes billed. For Dataflow streaming, right-size worker counts and use autoscaling to match ingestion volume.
Frequently asked questions
Five questions come up most often when teams plan IoT on Google Cloud.
Is Google Cloud IoT Core still available?
No. Google retired IoT Core, so devices now connect through a self-managed or partner MQTT broker that forwards data to Cloud Pub/Sub.
Which service ingests IoT data on GCP?
Cloud Pub/Sub, a fully managed real-time messaging service that decouples device producers from processing consumers.
Where is IoT data stored for analytics on GCP?
In BigQuery, the serverless data warehouse of Google, after Dataflow pipelines transform it.
How do you add machine learning to IoT data on GCP?
Use Vertex AI with AutoML or custom TensorFlow models trained on historical data in BigQuery, for example for predictive maintenance.
How should an IoT migration to GCP be sequenced?
Assess, plan, execute with a small non-critical subset of devices, then validate against the old system before decommissioning it.
Choosing the platform is the easy half, and the build around it is where most projects stall. Dev Station Technology builds IoT backends on GCP for clients in the United States and the United Kingdom. Visit dev-station.tech or email sale@dev-station.tech for a consultation. Device and telemetry data brings GDPR and ISO 27001 into scope for UK and EU deployments, and SOC 2 where a US client needs it, so region and retention are decided at architecture time. Our engineers work from Vietnam with overlap into US Eastern, US Pacific and UK GMT hours, and we invoice in USD or GBP.
Want an AI assistant to summarize or cite this guide?
Click any link below to open the AI with a pre-filled prompt referencing this article:
Talk To Us
Tell us what you are building and what it has to connect to. An engineer answers, and you get a straight view of what the work would take.
Get In Touch →