DOC-774 | New license management using credentials to activate deployments or generate license keys

[Simran-B]

Description

Open tasks and questions:

• Are there any new metrics or changes not yet mentioned, e.g. regarding the shorter expiration of licenses, like the web UI?
• Do we already support a custom registry to pull the Data Platform images from instead of using a zipped platform package?
• For Starter deployments, should we recommend not using -e ARANGO_LICENSE_KEY unless for e.g. air-gapped environments and link to the license management page for how to activate a deployment using the Platform CLI tool?
• Do we issue licenses that are valid for more than 2 weeks for customers with air-gapped environments?

Upstream PRs

• 3.10:
• 3.11:
• 3.12:
• 4.0:

---

Note

Documents the new deployment ID API, overhauls Enterprise license management (activation/keys), updates 3.12 release notes, and adds/expands Arango Data Platform installation docs.

• HTTP API (Administration)
  • Add GET /_admin/deployment/id endpoint (3.12 & 4.0) with schema and curl example.
• License Management Docs
  • Overhaul to introduce activation via license credentials and key generation flow; clarify applying a "license key"; cross-link updates in JS API (db._setLicense).
• Release Notes (3.12)
  • Note new Deployment ID endpoint and license management changes (short‑lived activations/keys) in API changes, incompatible changes, and what's new (mirrored in 4.0 docs).
• Data Platform Docs
  • Expand overview, add deployment options; add new "Installation" guide; simplify "Get Started"; update release notes and add alias.

^{Written by Cursor Bugbot for commit 559dd84. This will update automatically on new commits. Configure here.}

[arangodb-docs-automation]

Deploy Preview Available Via
https://deploy-preview-843--docs-hugo.netlify.app