True DevOps DNA

Open, portable, unopinionated, scriptable, integratable and firmly rooted in Git — OrgFlow is Salesforce DevOps built by DevOps engineers, for DevOps engineers.

A man is thinking. Around him are thought bubbles with Salesforce and Git logos, a CI/CD diagram and a command-line interface.

Designed for DevOps engineers

Rather than yet another web-based point-and-click DevOps monolith, OrgFlow is designed from the ground up as an open and portable CLI tool, better optimized for the needs and preferences of DevOps engineers.

DevOps engineers are tech savvy. They see shell scripting as a great way to build things, often feel that a terminal can be an extremely production environment, and are usually familiar with concepts like CLI tools, Git version control, scripting, automation, integration and CI/CD. Where most other solutions are optimized for non-technical users, OrgFlow is designed to make sense to, and unleash the engineering creativity of, those who are more technically minded.

2 persons are building a sand castle in a sandbox while 1 person looks at blueprints and directs the work.

DevOps for org-based development

OrgFlow is designed specifically for bringing true DevOps to org-based development.

Before OrgFlow, real DevOps was mostly reserved for those doing package-based development and using Salesforce DX. But the reality is that many teams — large and small — are doing org-based development for good reason, and we don't think they should be forced to change this just because there's no adequate DevOps tooling to support them.

That's where OrgFlow comes in. OrgFlow provides similar capabilities for org-based development, to what Salesforce DX provides for package-based development — and so much more.

Learn more in our article introducing OrgFlow

A woman is sitting on a beach in the shade of an umbrella, using her laptop to make changes in her company's Salesforce production org.

Supports changes in production

Are changes in production inherently bad practice and incompatible with DevOps? We don't think so, as long as there is tooling that can properly and safely support it — like OrgFlow.

Many businesses using Salesforce are used to being able to customize it directly in production. This is one of the long-time strengths of Salesforce, because it makes the system so easy to tailor, with minimum ceremony. Many teams find it sensible to allow some smaller, simpler and more atomic metadata changes directly in production, without the added hassle of deploying them from a sandbox.

OrgFlow fully supports this, with its ability to flow changes between environments bidirectionally, using the inherent merging and conflict resolution mechanisms in Git to safely reconcile the differences.

Two colleages designing a Salesforce DevOps process on a whiteboard in an office environment. One of them is using a whiteboard marker to cross out one sandbox environment from the process.


OrgFlow has no opinions about how you structure your Salesforce DevOps workflow — you decide which types of environments you want in your stack, what roles they should play, and how changes should flow between them.

Your process should not be dictated by your tools. OrgFlow places no restrictions on where your team can make changes — whether that's in your production org, in a sandbox, or even pushed directly to your Git repository.

You want a workflow with just your production org and a hotfix sandbox used only for Apex changes that cannot be done in production? OrgFlow is perfect for that.
You want a full multi-tiered pipeline with development, QA and staging environments and approval gateways with strict rules for how changes are promoted downstream? OrgFlow is perfect for that too!

An operator in the control room of a power plant is looking through an observation window into the reactor room where Git is generating power.

Git at the core

OrgFlow is built on Git as a deeply integrated and necessary component, and puts all the goodness of Git at the core of the process, not just in the periphery or as an after-thought.

Several other Salesforce DevOps products integrate with Git, but most treat it as a bolted-on or somewhat peripheral element. By ensuring that metadata changes always flows through Git — never directly between Salesforce orgs — OrgFlow brings to your Salesforce environments all the power and safety of Git, incluing line-level change history, rollback ability, branching and merging, change detection and conflict resolution.

And while your Git repository at the core of OrgFlow, you are still free to manage and interact with it outside of OrgFlow in any way you please.

A human and a robot are both standing behind a big toolbox with the OrgFlow logo on it.

A delight for both humans and machines

OrgFlow is easy to use hands-on for a deployment manager, but is also designed to be easily scripted, automated and integrated into the CI/CD platforms DevOps teams already love and use.

We built OrgFlow to be a great user-friendly CLI with detailed help screens, interactive prompts, rich animated progress reporting, and neat structured and color-highlighted terminal output.

But we also designed it to be great for scripting, automation and integration with rich structured JSON output, extensive support for environment variables, best-practice POSIX signal handling, and conscious management of output streams and process exit codes.

Two persons are sitting on the same side of a conference table working together on a Salesforce DevOps jigsaw puzzle.

Built for integration and composition

OrgFlow is deliberately designed to not be an all-inclusive Salesforce DevOps monolith that forces you to use it for everything. Our philosophy is to not reinvent wheels that others have already perfected.

Instead, being a portable and cross-platform CLI, OrgFlow is designed to be open, flexible and composable, so you can easily integrate it with anything you want.

Use your favorite Git service, CI/CD platform, or work tracking system. Integrate static code analysis into your workflow. Visualize your Apex test results in your test analysis and reporting tooling of choice. Notify your users in Slack or Teams when a deployment has failed. Your engineering creativity is the only limit.

Eventual consistency

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

Because OrgFlow is clever about it, deployment errors don't always have to be painstakingly avoided at all cost, and they don't always have to block a deployment. OrgFlow keeps track of failed components as a first-class concept, and knows how to continuously retry and safely deploy the rest. If some components fail in one deployment, it's not the end of the world: they can either be fixed later and included in the next one, or you can choose to ignore them.

Learn more in our article about eventual consistency

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