Key Concepts
Understand the building blocks of hav.sh.
Before diving in, it helps to understand how hav.sh is organized. Here are the key concepts you'll encounter.
#Teams
A Team is your workspace in hav.sh. Everything — servers, services, addons, backups, and members — belongs to a team. Think of it like an organization or company account.
- Each team has its own settings, members, and resources
- You can belong to multiple teams
- Team members have different roles and permissions
#Servers
A Server is a machine (typically a cloud VPS) that runs your Odoo instances. You provide the server, and hav.sh handles the setup — installing Docker, configuring databases, and managing networking.
- You can connect multiple servers to a single team
- Each server can host multiple Odoo services
- hav.sh monitors server health and connectivity
#Services
A Service (specifically an "Odoo Service") is a running Odoo instance. Each service runs in its own isolated container on a server, with its own database, files, and configuration.
Services come in different types:
| Type | Purpose |
|---|---|
| Live | Production instances for real business use |
| Test | Sandbox environments for testing and development |
| Demo | Demonstration instances for showcasing Odoo |
| Copy | Clones of existing services for testing changes safely |
#Addons
Addons are extensions that add features to Odoo. hav.sh integrates with GitHub to let you install addons from repositories directly into your services. Each addon is tracked by version, so you always know what's deployed.
#Hostnames
A Hostname is a domain name (like erp.yourcompany.com) pointed at one of your Odoo services. hav.sh manages the reverse proxy configuration so your domain routes correctly to the right service.
#Backups
Backups capture a snapshot of your Odoo service — including the database and all uploaded files. Backups can be created manually or scheduled to run automatically. They're stored in cloud storage (S3-compatible) for safekeeping.
#Actions
An Action is a task that hav.sh runs on a server — like deploying a service, creating a backup, or installing an addon. Actions run in the background, and you can monitor their progress in real time.
Most actions complete in seconds, but larger operations like backups or copies may run longer depending on data size.