---
title: "Build on Hubble Network"
description: "Get started integrating with Hubble Network — connect your first device, explore the Device SDK, and access the Cloud API."
source_url: "https://hubble.com/docs/"
---

# Introduction

Use this site to integrate and scale with [**Hubble Network**](https://hubble.com/).

---

## Chip Compatibility
Hubble's Terrestrial Network works with any Bluetooth Low Energy (BLE) capable [**system on a chip (SoC) or microcontroller unit (MCU)**](/docs/compatibility#terrestrial-network-any-bluetooth-device), whatever firmware environment it runs. The Device SDK is portable C with no operating system dependency of its own:
- **Zephyr RTOS** (real-time operating system) and **FreeRTOS**: ready-made SDK ports make integration a simple change to your application firmware. Espressif chips are also supported through **ESP-IDF** (Espressif IoT Development Framework).
- **Bare metal or any other RTOS**: integrate the SDK directly by following the [**Porting Guide**](https://hubblenetwork.github.io/hubble-device-sdk/main/quickstart/bare-metal/index.html), or start from one of our [**reference applications**](/docs/compatibility#find-your-chip).

Satellite Network requires one of our [**supported SoCs**](/docs/compatibility#satellite-network-supported-socs).

## Connect Your First Device
Sign up for a Hubble account and provision a supported developer kit in minutes using **Dash Quick Start**.

**Going further?** Where you go next depends on what you're building:
- **Piloting Hubble for your organization?** Run through the [**Pilot Framework**](/docs/guides/implementation/rollout) — a four-phase process for validating coverage, device connectivity, real-world network performance, and backend integration before ramping up in production.
- **Building custom hardware or firmware?** Browse [**Reference Applications**](/docs/compatibility) as a starting point for your own application, and connect your proprietary hardware to Hubble Network.

---

## Device SDK
Connect any device that uses a commercial off-the-shelf BLE chip to Terrestrial Network with a simple change to your application firmware.
- [**Access the Device SDK on Github**](https://github.com/HubbleNetwork/hubble-device-sdk).
- Browse [**Reference Applications**](/docs/compatibility) as a starting point for building your own custom application.
- Read the [**SDK Reference**](/device-sdk/downloads) to understand the Device SDK structure.

## Cloud API
Register your devices on Hubble Network and access packet data transmitted by the network via webhook or API request.
- Review the [**Cloud API Reference**](/docs/api-specification/hubble-platform-api) for the full scope of platform features.
- Import the raw [**OpenAPI spec (YAML)**](pathname:///docs/openapi.yaml) directly into your developer environment, API client, or AI coding tool.
- Learn how to [**onboard your devices**](/docs/guides/cloud-integration/register-devices) and [**get packet data**](/docs/guides/cloud-integration/get-data).

## Explore the Rest of the Site
- [**Network:**](/docs/network/terrestrial/transmission-guidance) Learn about the Terrestrial and Satellite Networks and review transmission guidance.
- [**Security:**](/docs/security/network) Understand how end-to-end data security works, from device to network to cloud.
- [**Build:**](/docs/guides/cloud-integration/register-devices) Everything for building on Hubble — devices, packets, gateways, the dashboard, and developer tooling like Hubble Connect, the Pluto SDR test flow, and the CLI.
- [**Manufacturers:**](/docs/guides/implementation/rollout) Best practices for scaling secure device onboarding, provisioning, and backend ingestion — including working with an ODM.
- [**Use Case:**](/docs/guides/use-case/asset-tracking) Get into the specifics of building with Hubble in the context of business use cases.

---

## About This Site
- **Active Documentation:** we actively maintain and update our guides for both the latest release and any supported previous versions.
- **Ongoing Updates:** we regularly review our documentation to ensure it meets your evolving needs.
- **Deprecation Policy:** when changes introduce breaking modifications, we provide advance notice and clear migration guidance. Deprecated features remain documented for at least one major release cycle.