The app should make API ownership clear. This keeps UI sections honest and prevents unsupported controls from appearing in the dashboard.
Coolify
Coolify can manage:
- Applications
- Services
- Databases
- Deployments
- Environment variables
- Resource domains
- Certificates for Coolify-managed resources
- Coolify-level backups where configured
Coolify should not be treated as the source for provider plans, server creation, or billing lifecycle.
Hetzner and Netcup
Provider APIs can manage:
- Server creation
- Server lifecycle actions
- Provider IDs
- Public IPv4
- Region and location
- CPU, memory, disk, and traffic facts
- Provider-level status
Provider APIs should not be treated as the source for application deployments or runtime resources.
Local app
Techservice owns the customer-facing model:
- Customer account relationship
- Selected offer and service role
- Provisioning job history
- Dashboard labels and support state
- Billing and renewal context
- Normalized events for the UI
The dashboard should show where the data comes from when it affects what the user can control.