Competitor MappingReference node
Projects (flat, no organization hierarchy above project level)
Competitor mapping for Hetzner Cloud.
This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.
Details
- Provider
- Hetzner Cloud
- Service term
- Projects (flat, no organization hierarchy above project level)
- Provider documentation
- External reference
Behavioral divergences
Projects (flat, no organization hierarchy above project level)
Quake AI concept: Organizations
- Hetzner has no organization or team hierarchy above the project level. Multiple Hetzner accounts cannot be grouped into an organization; access sharing across projects requires inviting individual accounts to each project separately.
- Hetzner API tokens are project-scoped bearer tokens with no cross-project token or service account concept. Keystone application credentials are user-scoped and work across projects when the user has appropriate roles.
- Hetzner projects are billing containers invoiced separately even under the same account; there is no consolidated billing across projects. OpenStack has no native billing hierarchy.
- Hetzner projects have no RBAC beyond owner vs. member; members cannot be restricted to specific resource types. OpenStack Keystone roles (admin, member, reader) provide granular per-project access control.
Related
Diverges from (incoming)
Citations
- Hetzner Cloud
- Hetzner Cloud
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.