Orgbench

End User License Agreement

Orgbench — plugin for IntelliJ IDEA and extension for Visual Studio Code Effective date: August 22, 2026 Licensor: CleverVerve Consulting LTD, 42 Tsentralna St., Maidanivka, 07824, Ukraine ("we", "us")

By installing or using Orgbench (the "Software") you agree to this Agreement. If you do not agree, do not install it, and remove it if you already have.

1. What you may do

We grant you a non-exclusive, worldwide, revocable right to install and use the Software for your own purposes, commercial ones included, on any number of machines you personally use or that your organization operates, subject to the rest of this Agreement.

The Software is licensed, not sold. We keep all rights in it that we do not grant here.

2. Tiers, and what is gated today

The Software has a free tier and a paid tier. In the current release nothing is gated: every feature is available to everyone, whether or not you hold a license key. That is a statement about this version, not a promise about all future ones.

When the paid tier is enabled in a future version, exactly three capabilities will require a key, and this Agreement will be updated before that version ships:

  1. transferring field-level security into permission sets and profiles;
  2. deploying more than ten components in a single run;
  3. importing and exporting package.xml manifests.

Everything else stays free permanently: comparing any of the supported metadata types, reviewing the differences, the diff view, git repositories as either endpoint, dependency auto-selection, Apex test selection, and all three deployment modes.

The ten-component limit is about the size of a run, not about the mode or the endpoint, and it counts components rather than files: several selected elements of one page layout are one component. It applies to any run that writes — including a validate-only run against a git repository, which produces a commit — and not to a validate-only run against an org, which writes nothing.

Enabling the paid tier does not reach backwards. Which features a copy of the Software gates is fixed when that copy is built, so a version you have already installed keeps behaving exactly as it behaves today, whatever later versions do.

3. Safety is never a paid feature

Every safety property of the Software applies in every tier, permanently, and we will not introduce a tier that relaxes one. Concretely: never deleting a component that exists only in the target — one missing from the source produces no row and is never touched — never deploying standard-object definitions, never using --ignore-errors against an org the Software has recognized as production, excluding namespaced metadata, keeping authentication inside the Salesforce CLI, and stripping secrets from diagnostics.

--ignore-errors is used by exactly one deployment mode, Best-effort, whose whole purpose is partial success on a test or UAT org. That mode is not offered against an org the Software has recognized as production, and the Software refuses it there even if a modified client asks for it; the plugin asks the target org which kind it is at comparison time, and when that question cannot be answered the mode stays available rather than the Software guessing. The quick-deploy of an already validated package never carries the flag at all.

That guarantee is about components. What a deployment may replace inside a component it does deploy is a different matter, and section 6 describes it.

4. License keys

A key is a signed text string. It records the email address it was issued to, the tier, the issue date, a seat count, and — except for a founder key — an expiry date. It is verified on your machine by a signature check; verifying it requires no internet connection and contacts no server of ours at any time.

  • Keys are portable. A key is not tied to a machine, and the Software counts no installations. You may use your key on every machine covered by your subscription and move it freely between them.
  • A key covers the number of seats it records. The seat count is the maximum number of individual people who may use the paid tier under that key — counted as people, not as simultaneous sessions. The Software enforces no seat count and counts no installations — we rely on you here rather than on a technical measure, which is precisely why this term matters: if more people in your organization need the paid tier, purchase the corresponding number of seats.
  • Do not publish or share a key beyond the people it covers. Posting a key publicly, reselling it, or distributing it is a breach of this Agreement.
  • Do not forge or circumvent keys, patch the Software to bypass tier checks, or distribute tools for doing so.
  • A subscription that expires stops granting the paid tier at the moment it expires, with no grace period. The Software does not stop working: it returns to the free tier and tells you why. Work you already produced is unaffected — nothing is locked, hidden or removed.

If you buy a subscription, the terms of that purchase are set out separately at https://orgbench.io/legal/terms; this Agreement governs your use of the Software either way.

5. What you may not do

You may not:

  • remove or alter our copyright and licensing notices;
  • redistribute the Software as your own product, or sublicense, rent or resell it;
  • use it to build a competing product from our source, if you obtain access to it.

Reverse engineering. You may not decompile or disassemble the Software, except to the extent that applicable law gives you that right regardless of contract — in particular for interoperability, and for observing or testing how it works while using it normally. Nothing in this section limits rights you have that cannot be waived by agreement.

6. Deployments are your decision

This is the part worth reading twice. The Software writes metadata into Salesforce orgs and commits into git repositories that you select, from your selections.

  • You choose the target. The Software refuses a comparison whose source and target resolve to the same Salesforce org, and re-verifies each org identity before deploying, but it cannot know whether the org — or the repository and branch — you picked is the one you meant. Two git endpoints are never refused for being the same repository: comparing two branches of one repository is a normal thing to do.
  • Some deployments replace content, and the Software tells you before they run. Deploying a bundle replaces that bundle entirely; deploying a page layout in whole-layout mode replaces the target document; a selected related list replaces the target's version of that list. Anything present only in the target's copy is gone afterwards. Every one of these is visible as a row in the comparison table before you start.
  • You are responsible for your data. Take backups, prefer sandboxes, and use validate-only runs. We are not liable for metadata changed, replaced or lost by a deployment you chose to run, nor for the behaviour of a Salesforce org after one.
  • The Salesforce CLI is a separate product with its own terms, which you accept from its vendor. The Software runs it on your behalf and never handles your Salesforce credentials.

7. Privacy

The Software collects nothing and sends us nothing. See the Privacy Policy at https://orgbench.io/legal/privacy; it is part of your agreement with us.

8. Third-party components

The Software bundles a native binary built from Rust source, together with open-source libraries distributed under permissive licenses (MIT, Apache-2.0 and BSD-3-Clause), and, in the IntelliJ IDEA plugin, the Jackson JSON libraries under Apache-2.0. Those components are governed by their own licenses; nothing in this Agreement restricts rights they grant you. The full list, with versions and license texts, is at https://orgbench.io/legal/notices.

9. Support and updates

We may provide support and updates but do not commit to any response time or release schedule. The support site is https://orgbench.io/. Nothing is sent there automatically — the Software opens it only when you click.

10. No warranty

The Software is provided "as is", without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that it will be uninterrupted or error-free, or that it will fit your particular Salesforce configuration.

Where you deal with us as a consumer, mandatory consumer-protection law of your country of residence may give you rights that this section cannot exclude; nothing here limits them.

11. Limitation of liability

To the maximum extent applicable law permits, we are not liable for indirect, incidental, special or consequential damages, for lost profits, lost data, lost metadata, or business interruption, arising out of your use of the Software — even if we were told such damage was possible.

Our total liability under this Agreement is limited to the greater of USD 50 and the amount you paid us for the Software in the twelve months before the claim.

Nothing here excludes liability that cannot be excluded by law, including for death or personal injury caused by negligence, and for fraud.

12. Term and termination

This Agreement applies for as long as you use the Software. It ends automatically if you breach it materially and do not fix the breach within 30 days of us telling you. On termination, stop using the Software and remove it. Sections 5, 6, 10, 11 and 13 survive.

13. General

No affiliation with Salesforce. Salesforce is a trademark of Salesforce, Inc. Orgbench is an independent product, not affiliated with, endorsed by or sponsored by Salesforce, and Salesforce is not responsible for it.

Marketplace operators are not parties. This Agreement is between you and the Licensor only. The operators of the marketplaces through which the Software may be distributed — including JetBrains s.r.o. (JetBrains Marketplace) and Microsoft Corporation (Visual Studio Marketplace) — are not parties to this Agreement, and they have no responsibility or liability to you with respect to the Software.

Changes. We may change this Agreement for future versions of the Software. A change never applies retroactively to a version you have already installed — the terms you accepted when you installed a version continue to govern that version.

Assignment. You may not assign this Agreement without our consent. We may assign it as part of a merger or sale of the business.

Severability. If any provision is unenforceable, the rest stays in force.

Entire agreement. This Agreement, together with the Privacy Policy, is the whole agreement between us about the Software.

Governing law. This Agreement is governed by the law of Ukraine, and the courts of Ukraine have jurisdiction — without depriving you, as a consumer, of the protection of mandatory rules of your country of residence.

14. Contact

support@orgbench.io