Service Types

When creating a service, you choose a type that defines its intended purpose. This helps you organize your services and signals their role to your team.

#Available types

#Live

Live services are your production instances — the ones your business runs on every day. They contain real data and are accessed by your team and customers.

Best practices for Live services:

• Always have automated backups enabled
• Assign a custom domain for professional access
• Test changes on a Test or Copy service before applying them here

#Test

Test services are sandbox environments for trying things out. Use them to:

• Evaluate new Odoo modules before deploying to production
• Test addon updates
• Train new team members
• Experiment with configuration changes

Test services are not meant for real business data.

#Demo

Demo services are designed for showcasing Odoo to potential users or clients. They typically contain sample data and are used for:

• Sales demonstrations
• Client presentations
• Training sessions

#Copy

Copy services are clones of an existing service. When you create a copy, hav.sh duplicates the entire database and file storage, giving you an exact replica to work with.

Common uses for copies:

• Testing upgrades on a mirror of your production data
• Debugging issues without affecting the live system
• Creating training environments with realistic data

#Preview

Preview services are automatically created when a GitHub pull request is opened on a connected repository with previews enabled. They are always neutralized to protect sensitive data.

Preview services are temporary and are automatically destroyed when the PR is closed or merged. See Preview Deployments for setup instructions.

#Choosing the right type