Try all features of OrgFlow without limits completely free for 2 months. No credit card or billing information required. Finished trialling? Starter Edition is free — and always will be.
The same download and binaries are used for both trial and subscription licenses.
Run the downloaded .msi file to install OrgFlow on your computer.
OrgFlow is not yet signed. When running the .msi installer, you may see warnings about running an unrecognized app or installing software from an unknown publisher. We plan to start signing our binaries and installer with a publisher certificate in the future.
By downloading and using OrgFlow you are agreeing to our End User License Agreement.
| universal | x64 | arm64 | |
|---|---|---|---|
| Installer (.pkg) | |||
| ZIP archive |
The universal build runs on both Intel and Apple Silicon processors and is recommended. Please note that the x64 version will not run reliably on Apple Silicon processors.
To use the installer, run the downloaded .pkg file to install OrgFlow on your computer. If you prefer to use the ZIP archive, OrgFlow can be run using the orgflow executable file from the extracted directory.
Both the installer and the OrgFlow binary are signed and notarized by Apple.
By downloading and using OrgFlow you are agreeing to our End User License Agreement.
OrgFlow can be run using the orgflow executable file from the extracted directory. For more convenience, consider adding the directory to the PATH variable of your shell, or create a symlink to the orgflow executable in a location such as /usr/local/bin.
By downloading and using OrgFlow you are agreeing to our End User License Agreement.
Docker images for OrgFlow can be found here:
https://hub.docker.com/r/orgflow/cli
To run OrgFlow in a Docker container interactively:
$ docker run --interactive --tty --rm orgflow/cli
$ orgflow --helpPlease see our docs for more advanced Docker scenarios.
We currently publish Docker images for linux/amd64 and linux/arm64 platforms only. To run OrgFlow in a Docker container on Windows, your system must be configured to use Linux containers.
By downloading and using OrgFlow you are agreeing to our End User License Agreement.
OrgFlow for GitHub Actions:
https://github.com/marketplace/actions/orgflow-salesforce-devops-for-github
You are not required to use our actions in order to use OrgFlow in your GitHub Actions workflows, but they do a lot of heavy lifting for you and ensure OrgFlow is configured and invoked in a way that ensures an optimal experience in GitHub Actions.
See our demo template repository for complete sample workflows and a guided tutorial.
Our setup action downloads, installs and configures OrgFlow in your GitHub Actions workflow using a single step:
steps:
# Download and install latest version
- uses: orgflow-actions/setup@v1
with:
license-key: ${{ secrets.ORGFLOW_LICENSEKEY }}
env:
ORGFLOW_ACCEPTEULA: "true"
# Run any OrgFlow command
- run: orgflow stack:listBy installing and using OrgFlow in GitHub Actions you are agreeing to our End User License Agreement.
Yes, OrgFlow requires a valid license key to run. The first time you run an OrgFlow command, you’ll be asked to either provide a valid license key or request a trial license key.
If you already have a paid subscription, enter the license key you received when starting your subscription.
To request a trial license key, simply provide your email address when prompted. A trial license key will be issued and sent to the email address provided. No credit card or other billing information is required. A trial license key lets you use OrgFlow completely free for 2 months, with no limits. To continue to use OrgFlow after your trial license expires, visit our pricing page to find the right subscription plan for your team.
A trial license key entitles you to use OrgFlow for free for 2 months (also for production/commercial use) with an unlimited number of stacks and orgs. This is essentially equivalent with our Enterprise plan, except without the SLA for technical support. We will provide technical support to you during your trial period, but without a guaranteed SLA or response time.
Download OrgFlow from this page and get started. The first time you run an OrgFlow command, you’ll be asked to either provide a valid license key or request a trial license key.
To request a trial license key, simply provide your email address when prompted. A trial license key will be issued and sent to the email address provided. No credit card or other billing information is required. A trial license key lets you use OrgFlow completely free for 2 months, with no limits.
No, you only need to provide a valid email address to which the free 2-month trial license should be sent.
Whether you have a paid subscription or want to try OrgFlow for free, you download the product from this page. The same download and binaries are used for both trial and paid licenses.
To use OrgFlow, you also need:
We do not provide Salesforce accounts and Git repositories as part of our services.
OrgFlow uses the Metadata API to connect to your Salesforce orgs, in order to flow metadata changes between Salesforce and your Git repository.
OrgFlow supports any Salesforce org where the Metadata API is available, including:
OrgFlow requires:
When running OrgFlow from our Docker images, all requirements are already provided by the images.
Visit our support page to get in touch with us for technical support.
Our installer packages and binaries are not yet digitally signed or notarized.
.msi installer package you may see warnings about running an unrecognized app or installing software from an unknown publisher..pkg installer package, in order to bypass Gatekeeper in macOS Catalina or later.We plan to start signing and notarizing our binaries and installer packages with a publisher certificate in the future.
Not currently. However, installation through Homebrew will be provided in the near future.
Not currently. Installation through Windows package managers such as Chocolatey or winget may be provided in the future. If this feature is important to you, please reach out to us at support@orgflow.io.
Not currently. Installation through Linux distro package managers may be provided in the future. If this feature is important to you, please reach out to us at support@orgflow.io.
| Version | Release notes |
|---|---|
| 2.6.15 (2024-11-19) | Fixes and improvements
|
| 2.6.14 (2024-11-12) | Fixes and improvements
|
| 2.6.12 (2024-10-19) | Fixes and improvements
|
| 2.6.11 (2024-10-12) | Fixes and improvements
|
| 2.6.10 (2024-10-08) | Fixes and improvements
|
| 2.6.8 (2024-08-19) | Fixes and improvements
|
| 2.6.3 (2024-07-15) | Fixes and improvements
|
| 2.6.2 (2024-07-15) | Fixes and improvements
|
| 2.6.1 (2024-07-14) | New features and functionality
Fixes and improvements
|
| 2.5.9 (2024-06-23) | Fixes and improvements
|
| 2.5.7 (2024-06-12) | Fixes and improvements
|
| 2.5.6 (2024-05-23) | Fixes and improvements
|
| 2.5.5 (2024-05-13) | Fixes and improvements
|
| 2.5.3 (2024-04-22) | Fixes and improvements
|
| 2.5.1 (2024-03-03) | Fixes and improvements
|
| 2.5.0 (2024-02-04) | New features and functionality
Fixes and improvements
|
| 2.4.1 (2023-12-30) | Fixes and improvements
|
| 2.4.0 (2023-12-05) | Introducing partial clone 🏎️Ever since our first release, OrgFlow has been utilizing Git's shallow clone functionality as a performance optimization when cloning your repo to the local machine. OrgFlow first creates a shallow clone (very quick) and then asynchronously "unshallows" the repository in the background while simultaneously working on other tasks. As the commit graph becomes larger over time, however, this unshallowing operation can start to put significant stress on the remote Git server and introduce performance and reliability issues. So, because two of the most popular Git hosting services - GitHub and Azure DevOps - have since added support for the newer blobless clone, we have added support for this in OrgFlow, too! The result is significantly improved execution times in many scenarios involving repos with large commit graphs, in addition to putting significantly less strain on the remote Git server which benefits everybody. The functionality is completely automatic and falls back to shallow clone if the remote Git server lacks support for blobless clone. Other new features and functionality
Fixes and improvements
|
| 2.3.0 (2023-10-27) | Introducing semantic merge 🧠OrgFlow can now recognize merge certain conflicts in the context of a metadata component, and suggest conflict resolutions based on its knowledge and understanding of the component's metadata schema. We've also added new We've started off with support for auto-resolving the most common conflict type - Other new features and functionality
Fixes and improvements
|
| 2.2.4 (2023-08-30) | Fixes and improvements
|
| 2.2.1 (2023-05-25) | Fixes and improvements
|
| 2.2.0 (2023-05-24) | New features and functionality
Fixes and improvements
|
| 2.1.1 (2023-03-29) | Fixes and improvements
|
| 2.1.0 (2023-03-24) | Fixes and improvements
|
| 2.0.0 (2023-03-01) | Second major version of OrgFlow 🎉Version 2.0 of OrgFlow is finally here after several months of development and testing. In addition to dozens of quality improvements around performance, reliability, usability, bug fixes and general clean-up, this release also contains several major new features, including:
See our article Introducing Source Tracking in OrgFlow 2.0 for a more in-depth description of some of these features. Migration from 1.x to 2.0There's a small number of breaking changes between 1.x and 2.0, so we've prepared a migration guide to help you make the transition. |
| 1.11.0 (2022-12-08) | Introducing history diffing ⚡️Previously, during outbound flow, OrgFlow would always retrieve the full target org for comparison with the repository in order to generate a deployment delta. This retrieve could be a major performance bottleneck during outbound flows, especially with larger orgs. This release introduces a new diffing method called history diffing where, instead of retrieving the target org, OrgFlow uses the Git branch history to build an accurate diff target, based on the recorded commit hashes at which each component was last successfully deployed. This results in significantly faster outbound flows. It also significantly reduces the risk of overwriting changes in the target org that have not yet been flowed into the Git branch. The new history diffing is the default for outbound flows during both Other new features and functionality
Fixes and improvements
|
| 1.10.2 (2022-11-11) | Fixes and improvements
|
| 1.10.1 (2022-10-28) | Fixes and improvements
|
| 1.10.0 (2022-10-25) | Introducing environment branch switchingEnvironment branch switching allows you to change the backing Git branch for an OrgFlow environment, which means that you can share a sandbox between several long-running feature branches. See our documentation on branch switching for more details.
New features and functionality
Fixes and improvements
Other notesWith this release of OrgFlow we had to make a breaking change to one of our APIs in order to prevent multiple future breaking changes. Previous versions of OrgFlow are now unable to verify your license key, and you will need to update to version 1.10.0 to continue to use OrgFlow. Why will previous versions stop working? The OrgFlow CLI connects to some of our cloud based APIs to facilitate things such as the environment state store, update checks, and license validation. We always strive to maintain backwards compatibility between previously released versions of OrgFlow and these APIs. However, as OrgFlow has grown, we've realized that our licensing API cannot keep up as we add new features and functionality. As a result, we have had to redesign this API so that we can continue to add new features in a reliable way. Unfortunately, there was no way to maintain backwards compatibility with versions of the CLI below 1.10.0. Will I need to update again? Although this required update might be an inconvenience, it helps to put in the groundwork to prevent further breaking changes between the CLI and our APIs. We always recommend that you keep up to date with the latest versions of OrgFlow. By keeping up to date you get access to the latest features, as well as bug fixes and performance improvements. We adopt semantic versioning, so you can be confident that updating to the same major version (v1.x.x) will not break any of your scripts or workflows. How do I update? If you have manually installed the OrgFlow CLI, re-download and install the latest version from the top of this page. If you are running OrgFlow in an automated context with the Docker image or the setup action, then you need to make sure that you are not pinned to a version below 1.10.0. The Docker tag |
| 1.9.0 (2022-10-17) | New features and functionality
Fixes and improvements
|
| 1.8.2 (2022-10-09) | Fixes and improvements
|
| 1.8.1 (2022-10-01) | Fixes and improvements
|
| 1.8.0 (2022-09-04) | Introducing Environment TagsTags are arbitrary name/value pairs that you can set on the environments in your OrgFlow stack. Their meaning and use are completely up to you and the processes and pipelines you build around them. Tags are a simple but powerful new automation feature of OrgFlow. They allow you to develop automation that treats environments differently without having to hard-code environment names. Instead, you can set different tags on different environments and base your automation logic on those tags. See our documentation on environment tags for more details. New features and functionality
Fixes and improvements
|
| 1.7.2 (2022-08-20) | Fixes and improvements
|
| 1.7.1 (2022-07-21) | Fixes and improvements
|
| 1.7.0 (2022-07-20) | New features and functionality
Fixes and improvements
|
| 1.6.1 (2022-06-16) | Fixes and improvements
|
| 1.6.0 (2022-05-27) | Introducing Snapshots and RollbackSnapshots automatically save copies of important state data about your Git repository and Salesforce metadata at key points, to allow an environment to later be rolled back to one of those points. Snapshots are automatically created after every successful inbound and outbound flow (starting from version Rollback allows you to roll back Salesforce metadata (in your Git branch and your Salesforce org) to match the state it was in at the time a snapshot was taken. New features and functionality
Fixes and improvements
|
| 1.5.0 (2022-05-13) | SnapshotsStarting with this release, snapshots are saved after successful inbound and outbound flows. New features and functionality
Fixes and improvements
|
| 1.4.1 (2022-04-12) | Fixes and improvements
|
| 1.4.0 (2022-03-24) | New features and functionality
Fixes and improvements
|
| 1.3.1 (2022-02-25) | Fixes and improvements
|
| 1.3.0 (2022-02-01) | New features and functionality
|
| 1.2.5 (2022-01-28) | Fixes and improvements
|
| 1.2.3 (2021-12-15) | Fixes and improvements
|
| 1.2.2 (2021-12-08) | Fixes and improvements
Other notes This release also moves the CLI from .NET 5 to .NET 6. This change should not impact you, but it may be worth while noting that the |
| 1.2.1 (2021-11-24) | Fixes and improvements
|
| 1.1.2 (2021-10-25) | Fixes and improvements
|
| 1.1.1 (2021-10-20) | Fixes and improvements
|
| 1.1.0 (2021-10-14) | New features and functionality
Fixes and improvements
|
| 1.0.4 (2021-09-17) | Fixes and improvements
|
| 1.0.3 (2021-08-28) | First public release 🎉 |