Deployment
A compliance system that holds personal data should sit where you trust it.
Some organisations will not put a register of their personal data on someone else's servers. Others want nothing to do with running software. TrustOS supports both, with the same product either way.

In short
Where does TrustOS run?
In one of two ways, with the same product. It can run inside infrastructure you control, where the agreed scope can include handing over the source code, or Code Colonies can host it for you with data kept on servers in India.
Side by side
Your infrastructure or ours
| In your infrastructure | Hosted by us in India | |
|---|---|---|
| Where it runs | Your cloud account or data centre | Our hosting, on servers in India |
| Who operates it | Your team, with our support during handover | Our team |
| Source code | Can be handed over in the agreed scope | Not needed |
| Identity and single sign on | Your identity provider | Configured with you |
| Upgrades | Planned with your change process | Rolled out by us, announced in advance |
| Best for | Banks, insurers, hospitals and others with strict data residency or vendor rules | Teams that want to start quickly without new infrastructure |
In your infrastructure
What a self hosted deployment includes
The exact scope is agreed before work starts. These are the pieces we usually cover.
Environment setup
Cloud or data centre environments, network rules, databases and storage, with development, test and production kept separate.
Security configuration
Encryption, access control, logging, backups and monitoring, set to your policies and reviewed with your security team.
Identity integration
Sign in through your identity provider, with roles mapped to the teams that do the work.
Source code handover
Where agreed, the source code, build steps and technical documentation, so your team can run and change it.
Integration support
Connectors to the systems that hold personal data, built and tested with your technology team.
Knowledge transfer
Hands on sessions for the people who will operate TrustOS, with runbooks for common tasks.
Questions
About deployment
Can we move from hosted to self hosted later?
Yes. Records export in standard formats, and we plan the move with you so requests in progress are not lost.
Which clouds do you support?
TrustOS runs on mainstream cloud platforms and on servers in your own data centre. We confirm the specifics during scoping, against your policies.
Who builds the connectors to our systems?
Usually our team with yours. Integration and custom work can be delivered on 2good.dev terms, where you pay after you accept the work.
Does self hosting change what the product can do?
No. The modules are the same. What changes is who operates the environment and how upgrades are scheduled.
See it with your data
Show us where your personal data lives. We will show you TrustOS running on it.
A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.
Or get a rollout proposal in two minutes- Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
- Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
- Step 3A first phase you can planModules, owners and effort, written down for you to keep.