Point your trackers to cloudGPS addresses: 11 ingestion protocols, history, reports, API and White Label already run on a three-server cluster in Germany. Your time goes to clients and installations.
Set the address and port of the tracker's protocol. If the protocol is unknown, connect the tracker to the auto-detection port and the platform will tell you what device it is.
| Protocol | Server | Port |
|---|---|---|
| Globus | gl.cloudgps.online | 3200 |
| Teltonika (Codec 8, 8E) | tl.cloudgps.online | 3201 |
| Bitrek | bt.cloudgps.online | 3202 |
| Wialon IPS | ips.cloudgps.online | 3203 |
| GT06 (Concox) | gt.cloudgps.online | 3204 |
| Ruptela | rt.cloudgps.online | 3205 |
| Sinotrack (H02) | h2.cloudgps.online | 3206 |
| Coban TK103 (GPS103) | tk.cloudgps.online | 3207 |
| Kids' GPS watches | sw.cloudgps.online | 3208 |
| BCE / Xirgo (FMS500) | bc.cloudgps.online | 3211 |
| JT/T 808 + JT/T 1078 (MDVR) | jt.cloudgps.online | 3212 |
| Protocol auto-detection | id.cloudgps.online | 3210 |
Clients keep working as usual while you move the trackers.
We set up the account and White Label: your domain, logo and colors. The first devices can be added the same day.
The address and port are changed by SMS command or the manufacturer's configurator; trackers can be moved in batches.
While clients get used to it, Wialon forwards data to cloudGPS with its standard retranslation, and you move trackers gradually.
Reports, fuel, geofences, alerts, mobile access and API already work, and clients sign in at your address.
What the integrator takes on in each option.
| Own server | cloudGPS | |
|---|---|---|
| Launch | rent a server, install software, set up protocols and backups | partner account and White Label in one day |
| Protocols | every new protocol has to be bought or written | 11 protocols already accepted, new ones added within weeks |
| Fault tolerance | one server means a single point of failure | 3 nodes, database replication with automatic failover, two load balancers in different locations |
| Backups | set up and tested by you | nightly to separate storage, checked weekly |
| Updates and security | your administrator | platform updates and edge protection on our side |
| Features | reports, fuel, API and branding as separate modules or development | included in the rate |
| Billing | server and licences every month regardless of device count | per active device, switched-off devices are free |
Where the data lives and for how long.
Hetzner servers in Germany, ISO 27001 certified data centres. A privacy policy and a data processing agreement (DPA) are ready for your clients.
Recent data on fast disks, older data in the archive. The full history is kept while the contract runs.
Every night a physical database copy taken from a replica goes to separate storage, and once a week the copy is verified.
Forwarding to Wialon IPS, Wialon Retranslator and Teltonika, reporting to PUESC SENT-GEO and e-TOLL. REST API v1 with tokens and access scopes, Swagger documentation and event webhooks.
Sensor preset catalog, calibration tables, device commands sent manually or automatically on geofence entry and exit, CAN data. Sensors are configured on the server, and the tracker keeps its stock firmware.
Changing the server address and port in the tracker settings is enough. Trackers keep their stock firmware and their own protocol.
Yes. Wialon's standard retranslation is set up to the cloudGPS server, clients compare the data, and you move trackers gradually.
Send us the protocol specification or the tracker model. New protocols are added within weeks.
For the whole contract. After it ends, the data is deleted within 90 days.
In Hetzner data centres in Germany. All infrastructure holding client data is in the EU.
REST API v1 with tokens and access scopes, Swagger documentation and event webhooks: geofences, alarms, device online and offline.
Tell us how many devices you have and which platform they run on now, and we will suggest a migration plan.