Run Odoo on your own servers, without giving up a control plane
A practical model for operating Odoo on Linux infrastructure you control while keeping deployment, environments, and routine operations consistent.
Technical notes for teams that run Odoo on infrastructure they own. Written from the operating model behind Tnion.SH.
A practical model for operating Odoo on Linux infrastructure you control while keeping deployment, environments, and routine operations consistent.
What Tnion.SH checks over SSH, what stays on your host, and how to prepare a Linux server before the first provision.
Connect selected repositories at workspace level, map branches to environments, and deploy modules without distributing personal access tokens.
Run Odoo on your terms.
Your repository, your Linux host, one explicit operating path between them.
Source
GitHub modules
Coordinate
Tnion.SH
Run
Odoo + PostgreSQL
Your Linux server
Specific guidance, without invented benchmarks or customer claims.
A practical model for operating Odoo on Linux infrastructure you control while keeping deployment, environments, and routine operations consistent.
What Tnion.SH checks over SSH, what stays on your host, and how to prepare a Linux server before the first provision.
Connect selected repositories at workspace level, map branches to environments, and deploy modules without distributing personal access tokens.
Separate Production, Staging, and Development by purpose, then use explicit branch mapping and controlled data movement between them.
Why useful Odoo backups include the database and filestore, how Tnion.SH records artifacts, and why restores begin with a safety backup.
How workspace authorization, encrypted server credentials, host verification, scoped repository access, and audit events fit together.