Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

API Token

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: API Token
Provider documentation: External reference

Behavioral divergences

API Token

Quake AI concept: Credentials

Generated via console UI per project (Security > API Tokens), not via keystone POST /auth/tokens.
Fixed permissions: Read (GET-only) or Read & Write (all methods), no granular role/scopes like admin/user per service.
Non-viewable post-creation; must copy immediately vs keystone tokens retrievable.
Project-bound by creation context; switch projects by changing token vs single token with project scope.

API Tokens (project-scoped Bearer tokens)

Quake AI concept: Authentication

Hetzner API tokens are project-scoped: each token is valid only for the project it was created in and must be separately generated per project. OpenStack Keystone application credentials are user-scoped and can be used across projects when the user has appropriate roles.
Hetzner has no OAuth2/OIDC integration for API access; all programmatic access requires a static bearer token. Keystone supports OIDC federation, LDAP backends, and federated identity (SAML2).
Hetzner tokens have no built-in expiry and must be manually rotated; there is no token TTL or refresh concept. Keystone tokens have configurable TTLs (default 1 hour) and support re-authentication.
Hetzner tokens are either read-only or read-write with no fine-grained scope. OpenStack roles (admin, member, reader) provide service-level access control per project.

Documentation

Related

Maps to

Analog of (incoming)

Diverges from (incoming)

Citations

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.