Editions · Enterprise
A deployment built around your requirements
When security, compliance and the contract set the terms, we design the deployment to meet them: an isolated, hardened environment that we manage for you, or inside your own cloud if you prefer.
Who it is for
When the requirements come first
For projects decided in the security review, the compliance checklist and the contract.
01 · Security
A security office to convince
Go-live waits on a review of the architecture, the access model and the vendor. We bring the diagrams and answer the questions.
- Architecture review
- Vendor assessment
02 · Compliance
Compliance that names the terms
Rules that say where data lives, who can reach it and how GDPR applies. The environment is designed to meet them from the first day.
- Data residency
- GDPR
03 · Contract
Service levels in the contract
Availability and response times agreed and written into the contract, not left to the best effort of a public plan.
- Contractual SLA
- Dedicated project team
Where it runs
Isolated by default, in your cloud if you ask
Always its own environment, managed by the team that builds the platform. Only the account that holds it changes.
Exists only for your project, down to the network and the billing boundary.
Deployed and managed by us, next to the rest of your infrastructure.
Hardened environment
Every setting turned to strict
On top of the platform's own security, every door it does not need is closed.
Application and database run in private subnets. Traffic enters through the front door or not at all.
- Application
- Private subnet · no public IP
- Database
- Private subnet · no public IP
- Ingress
- Front door only
A managed web application firewall filters requests before they reach the application. Every transport uses TLS.
- WAF
- Managed rules · on
- Console and API
- HTTPS only
- Device traffic
- TLS
Your people sign in with the corporate account they already have, with multi-factor authentication.
- Sign-in
- SSO · OpenID Connect
- Provider
- Your corporate IdP
- MFA
- On
Devices can authenticate with mutual TLS and their own X.509 certificate before they send a byte.
- Transport
- Mutual TLS
- Identity
- X.509 · one per device
- Unknown certificate
- Rejected
No SSH and no open administration ports. Our engineers use managed sessions with temporary credentials.
- SSH
- Disabled
- Admin ports
- Closed
- Engineers
- Managed session · temporary credentials · MFA
Backups run as a managed service. Compute, storage and backups stay in the region you require.
- Backups
- Managed service
- Region
- The one you require
- Compute and storage
- Same region as backups
ACCESS ON YOUR TERMS
Shared responsibility
Who does what, agreed before go-live
The split your security review will ask about, settled before the first device connects.
| Task | Thinger.io | Your team |
|---|---|---|
| Requirements and service levels | Takes part: Designs the environment to meet them | Leads: Security, compliance, region and SLA |
| Environment design and deployment | Leads: Designed, built and deployed by the project team | Takes part: Reviews and approves |
| Sign-in and user access | Takes part: Connects your identity provider | Leads: Your IdP decides who gets in |
| Platform and environment updates | Leads: Applied and verified by us | Not involved |
| Monitoring, backups and incidents | Leads: Within the agreed service levels | Not involved |
| Devices, dashboards and applications | Takes part: Project team support | Leads: Your product, built by your team or with ours |
Compliance and contract
Answers your security team can sign
Bring your security questionnaire. We answer it control by control, and the service levels go into the contract.
- ISO 27001
- GDPR
- Contractual SLA
- Security questionnaire
Deployment modes
One platform, four ways to run it
Many projects start on a Private Cloud plan and move here when the contract asks for more. Nothing is rebuilt.
| Cloud | Private Cloud | On-Premise | EnterpriseThis page | |
|---|---|---|---|---|
| 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.
Pricing
Scoped with you, sized per project
No price list. A project team works with yours from the first call to operation.
Requirements call
Security, compliance, data region, identity provider and service levels.
Environment design and SLA
A concrete proposal: the architecture, how it is operated and the agreed service levels.
The same team operates it
The project team that designed the environment keeps it running once it is live.
Next step
Tell us what your project has to meet
Security requirements, data region, identity provider, service levels. Send us the list, or the questionnaire, and we will design the deployment around it.