Connect device fleets to infrastructure that is already close to them.
Managed MQTT brokers, private APNs for cellular fleets and telemetry ingestion at the Joy edge — static addressing, DDoS-protected endpoints and single-digit-millisecond paths to devices across India, on one operational layer with your servers and storage.
Device fleets fail in ways web applications do not: a broker endpoint changes IP and ten thousand meters stop reporting; an amplification attack fills the uplink and the control channel dies with it. Joy IoT is built around those failure modes. Broker endpoints are static IPv4 addresses on AS152565 that survive every upgrade, they sit behind the same always-on scrubbing as every Joy server, and the edge that terminates device connections is in Noida, Mumbai and Chennai — the same metros your devices are in.
The product joins three pieces into one operational layer. Managed MQTT brokers with TLS, per-device credentials and topic ACLs. Private APNs so cellular devices reach your infrastructure over a private path rather than the public internet. And telemetry ingestion that buffers, validates and forwards device data into Joy Storage, a managed database or your own servers over the private backbone, with dashboards for connection counts, message rates and last-seen per device.
IoT is in build; fleets are onboarded through early access. If you already run a broker on a Joy VPS, the network features — static IPs, DDoS filtering, private VLANs — are available today.
I1 · I2 · I3
The three things this product line is built around — the same three boxes you see on the tile.
One operational layer for hardware, sensors and gateways
Brokers, private APNs, ingestion and the servers that consume the data are provisioned from one console and one API, with real-time visibility of connections, message rates and device state.
Connected hardware for real-world operations
Static, DDoS-protected endpoints in Indian metros keep meters, gateways, kiosks and vehicles reporting through attacks and upgrades; per-device credentials and topic ACLs keep fleets isolated from each other.
Device-to-platform connectivity for distributed operations
Private APNs bring cellular fleets onto a private path; the backbone carries telemetry to storage and databases in the same region without crossing the public internet.
Specification
| Brokers | Managed MQTT 3.1.1 and 5 over TLS; per-device credentials; topic ACLs; retained messages and shared subscriptions |
|---|---|
| Endpoints | Static IPv4 and hostname per broker on AS152565; always-on DDoS scrubbing; regional anycast on the roadmap |
| Private APNs | Cellular fleets terminate on a private network into Joy; static private addressing per SIM; no public exposure of devices |
| Ingestion | HTTPS and MQTT ingestion with buffering and schema validation; forwarding to Joy Storage buckets, managed databases or your servers over the private backbone |
| Visibility | Connection counts, message rates, last-seen and error rates per device and per fleet in the console; alerts by email and ticket |
| Compute | Rules and processing on hourly-billed NVMe VPS in the same region; private VLANs between brokers and your servers |
| Security | TLS everywhere, credential rotation, audit of staff access; data handled as described in the Privacy policy |
Three steps
Create a broker or APN
Choose the region and protocol; the static endpoint, CA and first device credentials are issued in the console.
Enrol devices
Provision per-device credentials and topic ACLs from the console or API — in bulk from a CSV or from your own provisioning system.
Route the data
Forward topics to Joy Storage, a managed database or your servers over the private backbone; watch fleet health on the dashboard.
Where IoT fits.
Questions about IoT.
Can I run my own broker instead?
Which regions will open first?
How are private APNs delivered?
Is device data stored by Joy?
More answers in the full FAQ — billing, network, DDoS, backups, support and legal.
Per broker and per device, published at launch
Early-access fleets are quoted by ticket. Run your own broker on an NVMe VPS today from $2.99 per month with static IPv4 and DDoS filtering included.
NVMe VPS in every region with static IPv4 and DDoS filtering — the compute this product line runs next to.
Works with
Build IoT into your stack.
Create an account and deploy in under ninety seconds, or talk to sales about a design for your workload — regions, sizes, timelines and a quote within one business day.