End‑to‑End Salesforce DevOps

All the functionality you need to build, manage, automate and operate a full end‑to‑end Salesforce DevOps process.

Manage environments

An environment in OrgFlow is a combination of a Salesforce org (either sandbox or production) and a corresponding branch in your Git repository.

The env:create command automates the creation of new environments — including sandbox creation and branch creation — in a single easy-to-use command that can be started once and left to run unattended.

Mutations made by the platform during sandbox creation are automatically reverted with an initialization deployment as soon as sandbox is ready, to ensure environments are truly identical.

Similarly, the env:delete command automates the deletion of an environment and its resources, while the env:list command provides an overview of all your environments together with useful details about each environment's Salesforce org.

The env:tags:set and env:tags:delete commands enable you to manage tags on your environments. Tags can be used as input in your scripts and CI/CD pipelines to make them more dynamic, and they can also help keep your environments organized.

Create and delete sandbox, Git branch and environment state as a single unit
Start environment creation and leave it to run unattended while sandbox is created in Salesforce
Control advanced sandbox creation parameters such as templates, post-activation and Chatter data
View detailed sandbox information such as instance name and current version
Use tags to organize environments and keep hard-coded environment names out of your scripts

Flow metadata from Salesforce to Git

An inbound flow in OrgFlow syncs metadata from an environment's Salesforce org into its backing Git branch.

The flow:in command automates the entire process of detecting changes in Salesforce, retrieving the metadata, normalizing it for seamless version control, detecting and resolving conflicts, and committing the changes to the appropriate Git branch — all in a single easy-to-use command.

Changes since last sync are detected automatically
No need to write any XML files — retrieval manifests are generated automatically
Deletes are fully supported, and are automatically detected and committed to Git

Normalization

Formatting and element ordering is normalized before commit, using smart and customizable metadata normalization rules, to help reduce insignificant changes and "phantom" conflicts when merging metadata.

Author attribution

OrgFlow can help improve accountability within your team by adding author information from Salesforce into your Git commit signatures, so you can trace changes in your Git history to the actual Salesforce users that made them.

Automatic change detection

OrgFlow automatically detects which changes were made in the Salesforce org since it was last synced with its Git branch — including components that have been deleted. No change forgotten — no change left behind.

Smart merge algorithm

OrgFlow intelligently combines incoming changes with any undeployed changes whenever the Git branch is ahead, which means metadata changes from multiple sources can be merged together instead of overwriting each other.

Unmatched performance

Metadata is split into smaller chunks and retrieved in parallel for unparalleled speed. Large orgs with hundreds of thousands of metadata components are handled with the same simplicity as smaller orgs.

Interactive exclusion

Sometimes changes in an org are made for experimentation or even by mistake. OrgFlow can show a graphical summary of detected changes during inbound flow, and let you selectively exclude those you do not wish to preserve.

Flow metadata from Git to Salesforce

Conversely to an inbound flow, an outbound flow in OrgFlow syncs metadata from an environment's Git branch out to its Salesforce org.

The flow:out command automates the entire process of comparing your metadata between Git and Salesforce, creating a delta deployment archive with the detected differences, generating the necessary package manifests, and deploying it all to Salesforce in a continuous exclude-and-retry loop — all in a single easy-to-use command.

Automatically compares Git branch with Salesforce org and deploys only the difference
Deletes are fully supported, and are automatically deployed to Salesforce
Deployment manifests are automatically generated

Apex tests

You have fine-grained control over which Apex tests are run during deployment — or you can simply rely on the automatic test behavior of the target org type. Test results can be exported in JUnit format for in-depth reporting and analysis.

Partial deployments

OrgFlow supports best-effort partial deployments — even to your production org. Our unique continuous deployment engine keeps track of undeployable components and excludes them from subsequent attempts.

Complete validation

A --checkOnly option runs validation deployment in a continuous exclude-and-retry loop until there are no more failed components, to show you the complete set of failures up front without altering the target org.

Flow metadata between environments

A merge flow in OrgFlow combines inbound and outbound flows with a Git merge to sync metadata between environments in a single atomic operation.

OrgFlow also provides powerful all-in-one operation to flow changes from a source org, via Git branches, all the way to a target org. Essentially an all-in-one deployment tool, the flow:merge command automates the entire process — including inbound flows of both environments, Git merge between the branches, interactive conflict resolution, and outbound flow of the target environment — in a single atomic operation.

Simplifies the complex flow from source org to target org into a single atomic operation
No changes are made to Salesforce or Git if any part of the process fails
Resolve merge conflicts interactively using your favorite graphical merge tool
Skip individual parts of the process depending on your workflow context

Self-healing process

OrgFlow's innovative eventual consistency based approach using partial deployments and undeployable component tracking, enables a simpler and more automatic self-healing deployment process that makes Salesforce DevOps easier, faster and safer.

Learn more

No more code clobber

The merge flow uses clever algorithms to always rely on Git merge — never on copy-paste semantics — so that no changes can ever be accidentally lost or overwritten, even if a Git branch contains undeployable components, or contains changes that have not yet been deployed to its org.

All-in-one validation

Using the --checkOnly option lets you run an orchestrated atomic validation merge flow, for early up-front discovery of any merge conflicts, deployment failures and test failures — without persisting any changes to either Git or Salesforce.

Run Apex tests in Salesforce

In addition to managing test runs during deployment operations, OrgFlow also lets you run Apex tests in any Salesforce org on demand.

The env:test command provides a convenient way to run Apex tests in your Salesforce environments, either manually on demand, or based on schedules or triggers in your CI/CD platform.

Run all tests on a desired test level, or specify individual test suites or test classes
Export test results in JUnit format for integration with your CI/CD platform or other industry-standard tools
Use options to control settings for code coverage, failure limits and other advanced options

Test proactively

Create a script or take advantage of the scheduling features of a CI/CD platform to run Apex tests on a frequent basis. Discovering test failures early makes it easier to identify the change that caused them.

Avoid blocked deployments

Avoid blocked deployments by knowing in advance which tests will fail. Run all Apex tests in your development sandboxes frequently, to weed out any failing tests and fix them before they block your next deployment.

Advanced reporting

Run Apex tests from your CI/CD platform and publish the test results for analysis. Exporting Apex test results in standardized JUnit file format opens up a new level of reporting capabilities.

React to failures

Take advantage of advanced reporting in your CI/CD platform to pinpoint the change that caused a test to begin failing, create work items straight from a failing test, or to associate a change as a root cause of a failing test.

Manage stacks

A stack in OrgFlow is a collection of environments that share the same production Salesforce org, a single Git repository and a single flow configuration.

Some teams require more than one stack, and OrgFlow provides stack:create, stack:delete and stack:list commands, allowing you to effortlessly create and manage multiple stacks in your OrgFlow account.

The first command you will run when you get started with OrgFlow is the stack:create command, which automates the initial setup of your stack — including connecting to your Salesforce environment, configuring your Git repository, and syncing your production environment with your main branch for the first time — with a single easy-to-use command. The stack:setdefault command saves you the trouble of specifying a target stack every time.

Support more than one production org with separate code bases using separate Git repositories
Run separate change streams for different subsets of your metadata

Manage credentials

Credentials in OrgFlow are usernames, passwords and tokens that OrgFlow can use to interact with your Salesforce environments and Git repositories in scenarios where interactive sign-in is not practical.

By default, OrgFlow interacts with Salesforce and Git on your behalf using credential-less techniques like browser-based sign-in or pre-configured SSH keys. But it can also securely store credentials, allowing it to work seamlessly in scenarios where interactive sign-in is not an option.

The auth:key:create and auth:key:save commands enable you to create and store encryption keys on your local computer, and the auth:salesforce:save and auth:git:save commands let you use those encryption keys to store encrypted credentials for different scopes of both Salesforce and your Git repository.

Encrypted credentials can be stored locally on the device where OrgFlow is running, or you can store them securely in our cloud-based state store so they can be shared and reused between different operators and devices.

Support automation scenarios where interactive sign-in is not feasible
Allow OrgFlow to interact with Salesforce using credentials not know to the operator
Allow OrgFlow to interact with Git repositories outside the authentication scope of your CI/CD platform
Encrypt credentials with keys known only by you and those you share them with
No one can retrieve your credentials except you — not even us
Sandbox credentials can be inferred based on saved production credentials

Ready to see what the fuss is all about?

Don't take our word for it — see for yourself! Try OrgFlow free for 2 months. No limits. No strings attached. No credit card or billing information required.

Try Now
Icon For Arrow-up