Skip to main content
Lago ships billing updates every 1 or 2 weeks. Keeping your self-hosted instance up to date keeps your billing engine on the latest fixes and features. This guide walks you through the update.

​
Why update your Lago self-hosted instance?

​
Bug fixes and security enhancements

Updates resolve bugs and close security issues. This matters most in metering, billing calculations, tax application, and financial statements, where a defect affects what you invoice. Staying current keeps your instance clear of known problems and vulnerabilities.

​
Access to new features

Each update adds features, such as core billing improvements, tax-related features, and additional settings options. Updating regularly gives you access to them.

​
Determining update frequency

Lago releases updates every 1 or 2 weeks. Watch the release notes to see when an update is available and what it changes, then plan your updates accordingly. Over the course of a year, we’ve completed over 70 releases, culminating in approximately 30 comprehensive product updates.

​
Update process

Follow these steps to move your instance to the latest version:

​
1. Access your instance repository

Navigate to the repository where your Lago open source instance is stored. This is typically where you initially cloned or downloaded the instance.

​
2. Check your current version

In the repository directory, execute the following command to check the current Lago version:

​
3. Check for the bridge releases

Bridge releases are released as mandatory intermediary releases that must be installed before upgrading to higher versions.
Check the migration guides for bridge releases and follow the update instructions for each intermediary release.

​
4. Fetch the latest release

Still in the repository directory, execute the following command to pull the latest release from the remote repository:
These commands fetch the most recent release from the remote repository and check it out locally.
To fetch the code of a specific release, use the following command:

​
5. Restart the updated instance

Once the code is up-to-date, navigate to the directory containing your Docker Compose file. Execute the following command to start the updated instance:
This command will rebuild and launch your Lago instance with the latest changes.

​
6. Test new features

After the instance restarts, test the new features and give feedback to the team.

​
Updating a Helm deployment

The steps above assume a Docker Compose instance tracked with Git. If you deploy with the Helm charts, update the chart instead:
Pin a specific chart version with --version when you want a known release rather than the newest one. The migration Job runs on each upgrade and brings the database schema up to date before the rest of the release restarts.
Moving from chart 1.x to 2.x is the one exception: it is a new install, not an upgrade, because the values schema and the generated resource names both changed. See coming from chart v1.

​
Addressing concerns about breaking changes

Lago reviews database and UI migrations carefully to limit the risk of breaking your instance during an update, so your workflows and user interfaces stay consistent across versions.