Editions · On-Premise
The full platform on your own servers
Run Thinger.io inside your own data center: your racks, your disks, your network, your rules. Devices report to servers you control, and operational telemetry never has to leave the perimeter.
Who it is for
When the platform must live with you
When data cannot leave, or the contract is only won with the software inside your walls.
01 · Tenders
Public tenders
Procurement that requires the platform delivered and operated inside the organization. A per host license and a standard install answer that clause directly.
- Public sector
- On-site delivery clauses
02 · Policy
Critical infrastructure policies
Utilities and industrial operators whose operational telemetry must stay inside their own perimeter. Devices report to servers on your network.
- Water and energy
- Industrial plants
03 · Your iron
Teams that run their own iron
IT departments with their own data center, virtualization and backup discipline. The platform is one more Docker host they already know how to run.
- Own data center
- Existing backup routine
How it installs
Software you install, not a service you depend on
A standard Docker Compose deployment: three steps, and the whole platform runs on your host.
A Linux host with Docker
A fresh server, VM or cloud host with Docker Engine and Docker Compose.
Fetch your compose file
Your license token, issued per host, retrieves the deployment configuration.
$ curl -o docker-compose.yml \ "https://subscriptions.thinger.io/v1/docker-compose.yml?token={LICENSE}"Bring the stack up
One command pulls the images and starts every service.
$ docker compose up -d
INSTALLED WHERE YOUR DATA LIVES
After the install
Day one, and every day after
What your team does once the stack is up: first login, devices, updates and backups.
First login
Create the admin account
Open the host in a browser and sign up with the admin email of your license. No other address can register.
https://192.168.1.100Devices
Point your devices at it
One line in the firmware sends each device to your server instead of the public cloud.
#define THINGER_SERVER "192.168.1.100"Updates
New releases arrive on their own
A watcher in the stack pulls new server images and restarts the container. Nobody logs in to upgrade.
ouroboros · monitor thingerBackups
Back up one folder
All state lives under /data on the host, so your existing backup routine covers the whole platform.
/data/thinger /data/mongodb
Security
Certified processes, per device credentials
A compromised sensor does not expose the fleet, and none of it leaves your perimeter.
- Operated by an ISO 27001 certified company
- Per device credentials over TLS
- Everything inside your own network
Deployment modes
One platform, four ways to run it
Prototype on the free Cloud, prove it on a Private Cloud, land on-premise at contract stage.
| Cloud | Private Cloud | On-PremiseThis page | Enterprise | |
|---|---|---|---|---|
| Best for | Learning, first prototypes and makers | Products and fleets in production | Policies that keep data inside your own perimeter | Strict security, compliance and contractual requirements |
| Infrastructure | Shared community cloud | A dedicated instance per customer | Your own servers and network | Isolated infrastructure designed for the project, ours or in your cloud |
| Operations | Managed by Thinger.io | Managed by Thinger.io | Operated by your IT team, with our support | Managed by Thinger.io to your requirements |
| Pricing | Free | Public plans from 49 EUR per month | Sized per project | Sized per project, custom SLA |
The platform is the same in every mode, so the choice is about who runs it, where it lives and what the contract has to guarantee.
Beyond a standard install, Enterprise covers custom deployments.
Next step
Bring the platform inside
Scoped per project, with a per instance license sized to your fleet and storage. Tell us about your infrastructure and the rules it must satisfy.