Choose Your Right Plan

Yes. We do have a generous free trial plan that comes with access to all our features, including premium features. No credit card is required. Free trial plan is valid for 30 days. Upgrade to a paid plan is required after this trial period. If you are a business user and want to extend your 30-day free trial period for further testing, please write to us: support@socketxp.com. Free trial plan usage is subject to our fair-use policy.

SocketXP HTTP Web Service Remote Access Solution is available in Eco, Pro, Standard or Premium Plans. Please subscribe to our Eco, Pro, Standard or Premium Plan.

Yes. We can get you a customized price plan if your usecase is special and doesn't fit any of the existing price plans above. Please write to us at: support@socketxp.com.

Yes. SocketXP offers a self-hosted Enterprise version of its IoT Gateway that you can run on-premise or in a cloud vendor of your choice. A 30-day free trial license for the Enterprise version, which includes all enterprise features, can be downloaded from SocketXP. Refer to our self-hosting guide to get started: https://docs.socketxp.com/platform/self-hosting-server/. To purchase a license after the trial, please write to us: support@socketxp.com

Yes. SocketXP offers a free Community version of its IoT Gateway server for self-hosting. It comes with limited features and supports managing up to 100 devices. If you need all the enterprise features or want to manage more than 100 devices, try the self-hosted Enterprise version with a 30-day free trial license. Refer to our self-hosting guide to get started: https://docs.socketxp.com/platform/self-hosting-server/

SocketXP uses SSL/TLS X.509 certificates and keys for encrypting data transmitted over the public internet from all endpoints to our cloud gateway. It is the same technology used by the banks and governments for exchanging confidential data over the internet.

SocketXP does NOT expose your IoT device ports (TCP ports) directly to the internet through our cloud gateway, unlike other IoT remote access solutions in the market. Basically, SocketXP solution does NOT perform 'port-forwarding', like other vendors do. We enforce Zero Trust Security on all our access endpoints.

SocketXP offers advanced security features such as short-lived authtokens that expire after a certain time period. These authtokens can be used only for a specific purpose such as device registration, device access, REST API access etc.

SocketXP Cloud Gateway is a massively scalable platform (supports managing more than 100,000 devices) that dynamically scales based on demand. Each user account (with a paid subscription plan) comes with its own maximum device limit based on the number of device licenses purchased under the subscription plan.

SocketXP Cloud Gateway runs in the US-Central (Iowa) Region and Europe (Frankfurt, Germany) Region. Depending on where you are located in the globe, your access speed may vary. European customers are recommended to use the Europe gateway.

Yes. We can create a new instance of SocketXP Cloud Gateway in your geographic location for high-volume users. We can also install, support and manage dedicated on-prem or private cloud version of SocketXP IoT Cloud Gateway for your exclusive private use. Please write to us: support@socketxp.com

If you are unable to connect to your device from the SocketXP web portal, it is either your device is powered down or it doesn't have a stable internet connection or a firewall setting is blocking SocketXP agent from connecting to our cloud gateway. Please check our troubleshooting guide for more tips on what you could next: https://docs.socketxp.com/guide/troubleshooting-guide.

The error message "Invalid device key" could mean two things:

1) You recently deleted the device from the web portal but the "device.key" file in the device at "/var/lib/socketxp" belongs to the previous registration. In that case, delete the stale "device.key" file and re-execute the SocketXP login command.

2) You are a customer in the EU region but trying to connect your device with the SocketXP cloud gateway in the US region using the "device.key" obtained from the SocketXP cloud gateway in the EU region. Use "--region=eu" in ALL the commands to resolve this issue.

Most likely, the problem is, you have created more than one tunnel or service for the same endpoint: SSH port 22, in this case.

Visit the SocketXP web portal, go to the devices section, click the Device ID to show the device details, scroll down to the bottom of the page to view the "services" or "tunnels" listed for this device. If you see more than one entries for port 22 (say for example: tcp://localhost:22, tcp://127.0.0.1:22, tcp://192.168.10.1:22), delete them just keep one entry. You should have only one service listed for each port.

Also, check if the SocketXP agent is running on the device and the SSH server daemon status is active, up and running (Use the "sudo systemctl status sshd" linux command to check SSHd status).

Yes. Our troubleshooting guide is located at: https://docs.socketxp.com/guide/troubleshooting-guide