#
Cloud Service

Soracom Napter

On-demand, time-limited remote access service that gives you secure, temporary connections to devices without static IPs or VPN setup.

Access any device on demand without assigning public IPs or configuring a VPN

Soracom Napter creates temporary, secure, point-to-point connections to devices—without requiring a public IP, port forwarding, or persistent tunnels. It lets you reach devices anywhere in the world for diagnostics, configuration, or management while keeping them isolated the rest of the time.

Remotely access devices only when you need to—and keep them locked down the rest of the time

Napter generates a time-limited, secure session that exposes a specific port on a device for remote access. You choose the protocol—SSH, HTTP, VNC, RDP, custom TCP—and the duration. Sessions expire automatically, eliminating the risks associated with persistent public endpoints. This provides simple, controlled access for troubleshooting, software updates, or remote support workflows.

Why use Soracom Napter for your project?

Secure connectivity icon

Controlled access

Open access only when needed, minimizing attack surface.

Authenticated Icon

Simplify troubleshooting

Reach devices for diagnosis without redesigning your network.

Branching paths

Reduce security risk

Avoid permanent public endpoints and static IP exposure.

How it works

Time-limited secure sessions

Create a remote access session that lasts only minutes or hours. Napter exposes only the requested port and closes it automatically when time runs out.

No VPN or static IPs required

Devices stay offline and unreachable until you open a session. No configuration changes or additional hardware are needed—Napter works through the Soracom platform.

Works with standard tools

Access devices using the protocols you already use: SSH for Linux devices, HTTP for configuration panels, RDP for Windows systems, or any custom TCP service.

Take a shortcut directly to technical documentation

Explore connection examples, security options, API usage, and best practices for remote device access.

Understand what this simplifies for your team

Lock Icon with Keyhole

Reduce truck rolls

Access and fix devices remotely instead of sending technicians onsite.

Soracom Event Handler icon

Increase security

Devices stay unreachable unless you explicitly open a time-limited session.

Checkmark icon

Work faster

Create a secure access session in seconds—no VPN setup required.

What you’d build without Soracom Napter

Deploy VPN clients or servers
Persistent tunnels require certificates, maintenance, IP planning, and ongoing monitoring.

Assign public IPs to devices
Exposing devices directly to the internet adds cost and creates security vulnerabilities.

Build custom remote support tools
Implementing temporary-access logic, access expiry, and authentication adds complexity and risk.

Architecture and implementation

Napter operates inside the Soracom core network, creating temporary port forwarding rules for authenticated users. When you request a session through the console or API, Napter opens a secure, time-limited connection from your device to a specific port on the target device. The device remains unreachable at all other times, preserving isolation and security.

Step 1

Enable Soracom Napter for your SIM group to allow secure temporary remote access

Open the Soracom User Console and navigate to the SIM or SIM group you want to enable for remote access.
Turn on Soracom Napter in the group settings to allow on-demand, time-limited remote access sessions without assigning public IPs to your devices.

Napter provides secure, temporary access tunnels that let you reach devices for diagnostics, updates, or support without exposing them to the Internet.
For setup details, see the Soracom Napter documentation.

Step 2

Create a temporary remote access session for the device

From the SIM details page or API, initiate a new Napter session to open a temporary port for accessing your device.
Choose the protocol you want to use—such as HTTP, HTTPS, SSH, or TCP—and specify the allowed duration of the session.

Napter generates a secure, time-bound URL or connection endpoint that you can use immediately, without configuring VPNs or firewalls.
Learn how to start sessions in the Napter session creation guide.

Step 3

Connect using the generated Napter endpoint and complete your remote task

Use the Napter-generated endpoint to access the device for diagnostics, configuration changes, software updates, or log retrieval.
The session automatically expires after the specified time, ensuring the device remains protected once remote work is complete.

No VPN setup, no NAT traversal, and no static IP assignment are required—Napter keeps connectivity both simple and secure.
For connection examples, see the Napter connection guide.

How Soracom Napter works with other Soracom services

Use Napter + Gate for deeper diagnostics
Gate gives you private network access; Napter provides time-limited remote access for maintenance or repair.

Use Napter + Inventory to troubleshoot devices
Inventory gives you device health data; Napter lets you remotely fix issues without visiting the field.

Use Napter + Harvest/Lagoon to solve problems faster
When telemetry or dashboards show issues, open a Napter session to inspect or update the device directly.

#

Get on-demand remote access with Soracom Napter

Create a free Soracom Operator ID and start opening secure, time-limited access sessions to your devices.

Sign up and start testing

Frequently Asked Questions

What is Soracom Napter?
A service that provides time-limited remote access to devices without requiring static IPs or VPN setup.
Are devices exposed to the public internet?
Devices remain fully private until a session is opened, and only the requested port is exposed.
Do I need to change device firmware?
No. Napter works at the network level and requires no device modifications.
Can multiple team members use Napter?
Yes. Permissions are managed through Soracom’s user and role system.
What protocols can I use with Napter?
Any TCP-based protocol, including SSH, HTTP, RDP, VNC, or custom services.
How long do sessions last?
You set the duration—typically minutes or hours. Sessions expire automatically.
How is access authenticated?
Sessions can require password protection or IP whitelisting, and only authorized users can initiate access.