Skip to main content
Upgrade policies determine how new provider versions are deployed to your workspace. You choose a policy when installing a provider.

​
Policies

​
Manual (Default)

With the manual policy, you control exactly when upgrades happen. New versions are not deployed until you explicitly run the upgrade command or trigger an upgrade from the web UI. 
pragma store install qdrant --upgrade-policy manual
To upgrade: 
pragma store upgrade qdrant
Manual upgrades give you full control over when changes are applied, which is useful when you need to coordinate upgrades with other changes in your environment.

​
Auto

With the auto policy, new versions are deployed automatically when published to the store. The platform periodically checks for updates and performs rolling upgrades with zero downtime. 
pragma store install redis --upgrade-policy auto
Auto-upgrade is useful for providers where you want to stay on the latest version without manual intervention.

​
Choosing a Policy

ScenarioRecommended Policy
Production workloads requiring stabilityManual
Development and testing environmentsAuto
Providers you want to keep currentAuto
Regulated environments with change controlManual

​
Viewing Current Policy

pragma store installed

Provider   Version   Tier       Upgrade Policy   Installed At          Upgrade Available
qdrant     1.2.0     standard   manual           2026-02-20 14:30:00   -
redis      1.0.0     standard   auto             2026-02-20 14:35:00   -

​
Changing a Policy

To change the upgrade policy of an installed provider, uninstall and reinstall with the desired policy: 
pragma store uninstall qdrant
pragma store install qdrant --upgrade-policy auto
If the provider has active resources, uninstall will fail. Use --cascade to delete all managed resources first. See Uninstalling a Provider for details.