Wormhole

What is this?

Wormhole creates a persistent outbound tunnel from a Linux device to a web service running locally on that device. Each device gets a unique HTTPS URL (such as https://<yourdevice>.dataplicity.io/) that routes to the service.

Why does it matter after devices ship?

Many IoT devices host a web-based control panel, REST API, or configuration interface. These work fine on the local network but are unreachable from outside. Wormhole exposes them over HTTPS without port forwarding or managing certificates on each device.

How does it work in Dataplicity?

1. A web service runs on the device (for example on port 80 or 8080)
2. Wormhole is enabled for that device in the dashboard
3. Dataplicity routes HTTPS traffic from the Wormhole URL to the local service
4. The connection is encrypted between Dataplicity and the agent

Wormhole does not replace application-level security. Secure your web service with authentication and follow basic hardening practices.

When should I use it?

• The device hosts a web control panel or API
• You need a bookmarkable URL to reach a device service
• You want to access a device's web interface from anywhere without VPN
• You are running automated scripts against device-hosted REST APIs

Example workflow

An industrial controller runs a web dashboard on port 8080. The vendor enables Wormhole, bookmarks the URL, and gives support teams access to the dashboard for any field-deployed unit without configuring customer firewalls.

Related

• Wormhole guides
• Wormhole security
• Remote access