Dify Enterprise license activation online and offline
Activating a Dify Enterprise license with a License ID or an offline code from the Cluster ID, why the license is bound to a namespace, and restarting the enterprise service.

Running Dify Enterprise across an organization: licensing, workspaces, staging and production environments, organization-wide logs, telemetry export and admin automation.
Activating a Dify Enterprise license with a License ID or an offline code from the Cluster ID, why the license is bound to a namespace, and restarting the enterprise service.
Creating workspaces per team, assigning owners, archiving and deleting workspaces, and moving people between them from the admin panel.
Promoting app versions from staging to production with Enterprise Environments: separate credentials and variables, shared versus isolated runtime modes, CPU quotas from the license and rollback.
Which app types, nodes and integrations can run in deployed environments, and what must be redesigned before an app that uses knowledge retrieval, agents or human input can be promoted.
Reviewing every app run across the organization: status, duration, tokens, operator and source, filters for failures, and how this differs from per-app logs.
Streaming metrics and traces from Dify Enterprise to your own OpenTelemetry collector for cost allocation and SLOs, and building a separate pipeline for structured event logs.
Automating workspace and member management with the Enterprise Admin APIs: secret key authentication, the resources covered, and safeguards for scripts that change production data.
Applying your own logo and name to the Dify Enterprise console and web apps, and what the Community license says about removing Dify branding.
Deploying the agent-sandbox controller that Agent apps need on Kubernetes, the cluster-admin approval it requires, and the shared sandbox mode for restricted clusters.
Running the three-node Qdrant cluster Dify recommends for production Enterprise: VM sizing, storage, replication and backup.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.