Sandbox & Staging Orgs
Every Hubble account starts in Sandbox — an always-free, closed environment for bringing your hardware onto the network. Once you upgrade to the Live Network, you can also create a standalone Staging Org for siloed device testing with the same network access as production.
Build in Sandbox
When you first sign up, you start in Sandbox: a closed environment for zero-to-one device activation. Start with a free account (Sign Up if you don't have one), then use Dash Quick Start to get your first device on the network.
Log in to the Hubble Connect mobile app to turn your phone into a scanning gateway on the Terrestrial Network. While your organization is limited to Sandbox, you'll only receive packets captured locally through Hubble Connect.
Unlock Live Network Access
To unlock global coverage, upgrade your account to the Live Network, multiplying your scanning gateways from one (your mobile device) to over 100 million. Every device in your organization becomes discoverable on the full network, and you'll receive packet data for all detections.
Staging Orgs
Use a Staging Org to test devices in an environment that's fully siloed from your production org — separate org ID, separate user access, separate API credentials — while still getting the same Live Network access as production.
Note: Staging Orgs replace the old tag-based Sandbox environment that used to live inside your production org. Staging is now a genuinely separate organization: your own space to test new devices, hardware revisions, or integrations without touching production data.
Create a Staging Org
You can create a Staging Org on demand from your production account. Because it's a separate org, packet data doesn't flow through your production API or webhook — you'll need to configure access separately.
- From Dash, select the org dropdown and click "Create a Staging organization".
- Add existing users automatically, or manually add later.
- Move devices into the staging org, or register new devices.
- Generate a new API token and/or configure a webhook scoped to the staging org for backend integration (production credentials do not carry over because staging is a separate organization).
Moving Devices Between Orgs
You may move devices you own between orgs at any time. Reassign devices from Production to Staging, or Staging to Production, using the Dashboard flow or the Update Device API with set_destination_org_id.
User Access
User permissions are set independently per org. As with production, Admins can make changes to the organization and devices, while Members have view-only access. Learn more in the Users & Roles guide.
Because staging is a separate org, granting a new user access to your production org does not automatically grant access to your staging org, and vice versa.
Org Type Summary
| Sandbox | Production Org | Staging Org | |
|---|---|---|---|
| Purpose | Getting started and technical validation | Your live, in-production device deployment | Devices you've set aside for testing |
| Live Network access | None — limited to self-provided packets via the Hubble Connect app install (phone as gateway) | Full access (100M+ scanning gateways) | Same access as production |
| Org ID | Your account's default org, before you upgrade | Your existing org ID | A new, independent org ID, for a separate org from production |
| User access | Managed within your account | Managed within your account | Managed independently |
| API token / webhook | Available, but only returns self-provided packet data (i.e. Hubble Connect) | Your existing credentials | Requires its own API access setup |
| Registered device limit | 100 devices | Determined by your plan | 100 devices |
| Billing | Not billable | Billed per your plan | Not billable |
| Packet history retention | Same as production | Standard platform retention | Same as production |
| API rate limits | Same as production | Standard platform limits | Same as production |