They can control any of their smart devices (eg. smart bulbs) without transferring data through 3rd party servers.
Your smartphone app can talk to your smart device (eg. garage door) over the internet directly, without any API server in between.
No API server means your IoT device will always work if connected to the Internet. DDoS or any other hacker attacks on an IoT platform can disable the whole IoT network. There is no such risk in case of Husarnet.
Husarnet can connect two, ten, or thousands of devices into a single network. Scale your solutions easily as you grow.
Husarnet infrastructure is used only for establishing and maintaining the connection. As soon as a peer-to-peer connection is established, data traffic goes directly between your devices running Husarnet Client software. Husarnet servers do not take part in the communication.
To make your existing device code work over Husarnet all you need to do is start the service in the background using just a few lines of code.
From a developer point of view, Husarnet connected devices behave like they were connected to the same WiFi router. They can however be connected to different routers in different networks (in different countries) with almost no configuration.
All you need to do to make a device such as ESP32, working in LAN, work over the internet, is to add the following lines to the existing web server code.
Let's compare the amount of flash memory used for the two code snippets (for ESP32) presented in the previous image:
This means that on a simple microcontroller such as ESP32 Husarnet needs only ~450kB of additional flash in comparison to the same code working in LAN. Let's put it this way: you just installed a full VPN on your microcontroller for less than half a Mega Byte!
When it comes to RAM, Husarnet consumes only ~76kB of memory.
In typical IoT solutions RSA is used for session key exchanges and AES for data encryption.
In Husarnet we treat security much more seriously, and use X25519 (from libsodium) for key exchange, with ephemeral Curve25519 keys for perfect forward secrecy. The hash of initial public key is validated to match the IPv6 address. The packets are encrypted using libsodium ChaCha20-Poly1305 secretbox construction with a random 192-bit nonce. All to ensure high-security margins, and achieve high performance and throughput. Packets never leave your device unencrypted.
It's hard to find something more secure for IoT.
You can connect your IoT devices with computers and smartphones with no additional server in between.
In typical architectures you have:
In a solution powered by Husarnet there are only:
Because IoT server is not needed for establishing the connection
A typical IoT network operator provides a centralized service to which your devices are connected. In case such a server is down due to a hacker attack or failure, the whole IoT network is disabled.
Husarnet provides a decentralized alternative:
The pricing model is simple: a fixed monthly or annual fee with no transfer limit, starting at only 0.35 USD/dev/mo.
No hidden costs, no transfer monitoring - we can't physically do that, because of peer-to-peer data transfer. We also offer a free account up to 5 connected devices.
Husarnet Client software works standalone on: