Documentation

Appearance

Firewall operations #

Customer networks are the norm for commercial IoT deployments. Devices sit behind NAT, corporate firewalls, and ISP routers you do not control.

Why traditional access fails #

Port forwarding requires:

  • Administrative access to the customer's router
  • A static local IP for each device
  • Inbound firewall exceptions
  • Coordination with customer IT for every deployment

VPN access requires:

  • VPN server setup and maintenance
  • Customer IT to allow VPN traffic
  • Per-user VPN accounts and credential management

How Dataplicity works in customer networks #

The agent makes outbound HTTPS connections to documented Dataplicity destinations. The Dataplicity access path does not require a per-device inbound rule.

In unrestricted networks, the outbound route may work without an additional network change. In filtered networks, confirm DNS, accurate device time, network-owner approval, and the required destination allowlist.

Restricted networks #

Some customer networks filter outbound HTTPS. In that case, use the current host and port list in Firewall requirements. It includes the core service destinations:

  • api.dataplicity.com
  • m2m.dataplicity.com

Provide the complete current requirements to customer IT during deployment planning.

When to use this #

  • Devices deployed to customer-owned facilities
  • Retail, industrial, agricultural, or municipal sites
  • Any environment where you cannot configure the local router