01
Workspace
The boundary for people, servers, projects, Git access, and activity. Invite your agency or product team without sharing SSH credentials.
Product
Your Odoo infrastructure. One control plane.
Tnion.SH is a BYOS control plane: bring your own servers, keep ownership of the hosts, and run Development → Staging → Production like a platform — without surrendering the metal to a hosted SaaS.
Architecture
Layers that match how agencies actually ship
The product model is intentional: isolate clients and teams at the workspace, keep hosts under your account, and promote releases through real environments.
02
Servers you own
Register Linux hosts over SSH. Tnion.SH never takes ownership of the machine — you keep the VPS, the keys, and the bill with your provider.
03
Projects & instances
Each Odoo project maps to instances across Development, Staging, and Production so clients and releases stay isolated.
04
Deploy & operate
Git-backed deploys, backups before risky moves, instance hostnames, and fleet signals — from one console instead of ad-hoc scripts.
Workflow
From empty account to first deploy
- 01
Create a workspace
Name it, pick a slug, become owner. Members and invites live here.
- 02
Connect a Linux server
SSH username, password, and port. Test connection, verify host key, then provision.
- 03
Define the project
Choose Odoo version and edition, create the project, attach environments.
- 04
Ship with Git
Link the repository, deploy modules to the right stage, restore from backup when you need a clean rollback path.
Prefer a guided path? Follow the quickstart in docs.
BYOS
Bring your own servers — keep the ownership boundary clear
You own
- VPS or bare-metal Linux hosts
- SSH credentials and host keys
- Customer data on your disks
- Choice of provider and region
Tnion.SH operates
- Control plane and console UX
- Provisioning and deploy orchestration
- Workspace membership and access
- Backup workflows and instance routing
Ready to run Odoo like a platform?
Create a workspace, connect a non-production server first, and ship your first environment with Git and backups in the loop.