Infrastructure
This English version is provided for convenience. The Dutch version is the binding one.
Trainiq's infrastructure consists of web servers, application servers, database systems and network components, among other things. These are set up redundantly with load balancing and automatic failover, so a fault in one component is picked up by another automatically. As a rule our customers notice nothing.
1. Structure
The infrastructure is built in layers:
- Hosting layer: physical servers in a German data centre with ISO 27001, ISO 9001 and SOC 1/2 Type II certification
- Network layer: traffic is spread over several application servers by a load balancer
- Application layer: several parallel application servers handle incoming requests
- Database layer: separate database systems with encrypted storage
- Backup layer: daily encrypted snapshots, stored on a separate host outside the production environment
The list of third parties we use (including location, certifications and data categories) is at trainiq.nl/en/subverwerkers.
2. A separate environment per training provider
Every training provider gets its own isolated environment at Trainiq, with its own database. No shared data storage with other training providers, no shared user list between customers. Optionally a training provider can run its environment on its own domain.
For you that means:
- Other customers don't affect your performance. A peak at another training provider has no effect on your environment.
- No risk of mixed-up data. A faulty query at another training provider can never expose your data, because yours physically sits in a different database.
- Simple to leave. If you stop using Trainiq, you receive an export of your own environment, without the hassle of untangling data shared with other customers.
- Suited to stricter compliance demands. For customers with tougher requirements (healthcare, government) this isolation shortens the audit path.
3. Availability and recovery
Redundant setup with load balancing and automatic failover limits the impact of a single component failing. For failures that still lead to an outage, our recovery objectives are:
- RTO (recovery time objective): under 2 hours for an infrastructure outage
- RPO (recovery point objective): under 24 hours of data loss in the worst case (daily backup cycle)
- Restore test: every quarter we perform a real restore of a random snapshot to verify that our backups are usable
Updates are rolled out in versioned steps and can be rolled back to the previous version in a single action. See also our uptime objective and maintenance window at trainiq.nl/en/beschikbaarheid.
4. Backups
- Daily automatic snapshots of all production databases
- 30-day retention, stored encrypted on a separate host
- Private files (for example signatures, signed contracts) are part of the same daily snapshot
- Configuration and environment variables are exported at every significant change
- Legally required retention (such as the 7-year period for invoices under art. 52 AWR, Dutch tax law) is managed separately
Need a specific backup of your own environment? You can request one through info@trainiq.nl. When the Agreement ends you receive an export as standard, as described in article 31 of the terms and conditions.
5. Administration and access
Production servers are not directly reachable from the public internet. Administrative access runs only over secured routes with mandatory public-key authentication and two-factor verification. No password authentication, no shared admin accounts.
All significant administrative actions are logged in an audit trail with actor, timestamp and context. Customers can consult that audit log themselves in the admin portal. Further details about our security measures are at trainiq.nl/en/beveiliging.
Questions?
Working on an audit, supplier assessment or compliance questionnaire and need more detail about a specific layer? E-mail info@trainiq.nl or call +31 85 071 1114. For enterprise customers we can share additional technical documentation under NDA.