Self-hosting Apidog
  1. Maintenance & Upgrades
Self-hosting Apidog
  • Introduction
    • Installation Overview
    • System Requirements
  • Licensing
    • Obtaining Apidog On-premises License
  • Deployment
    • Running Apidog on Docker
    • Running Apidog on Kubernetes
    • Running Apidog Multi-Container Deployment without Kubernetes
    • Privacy
  • Initial Setup
    • Admin Panel
    • Installing Apidog Client
    • Access Apidog Web
  • Configuration
    • Environment Variables
    • Configuring the application database
    • Configuring the application storage service
    • Configuring the git connection environment
    • Authentication Providers
      • Using LDAP for authentication
      • Using OKTA for authentication
      • Using OAuth2.0 for authentication
  • Maintenance & Upgrades
    • Updating Apidog
    • Backing up Apidog
    • License Renewal
    • System Data Flow
  • Troubleshooting
    • Troubleshooting
    • FAQ
  • Apidog API (coming soon)
  1. Maintenance & Upgrades

License Renewal

Upgrading from Trial to Full Version#

When upgrading from the trial version to the full version of Apidog, all your data is preserved, no migration is required. For on-premises deployments, simply update the LICENSE environment variable in your deployment with the full-version license.

Renewing Your License#

Renewing the Apidog license does not affect your data, no migration is required. To maintain uninterrupted access in on-premises deployments, update the LICENSE environment variable in your deployment.
If your license was about to be expired and needs to be updated, follow the instructions below.
1.
Stop and remove the running apidog container:
2.
Following the Installation Guide, update the LICENSE environment variable to the new Server License and start the apidog container again. Important: Keep the JWT_SECRET environment variable unchanged, or sign-in will be affected.

About Zero-Downtime Deployment#

For Docker, refer to Running Apidog Multi-Container Deployment without Kubernetes and upgrade containers one by one by adjusting the upstream backend.
For Kubernetes, use Helm chart configuration or your Deployment manifest and add the following strategy at the same level as replicas:
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0
Modified at 2025-11-24 15:57:02
Previous
Backing up Apidog
Next
System Data Flow
Built with