Salesforce org connections by plan: draw the coverage map before you pick a tier

The tier a Salesforce team should buy is decided by how many orgs it must reach over the next five quarters, through Q4 2027, not by the per-month price on the plan card. Count the Salesforce org connections first, then read which plans cover that count. Every coverage map strands a segment. The question is whether the stranding was chosen.

What coverage question does a plan answer?

The question that binds the year: which orgs must someone change, compare or deploy to before the next budget review, and does the plan reach them all? A plan with five Salesforce org connections against a map of six has not saved money. It has stranded one org that someone carries by hand.

The attribute to cut on is the org itself: production and sandbox lists are visible in Setup.

Salesforce org connections per plan, as the vendors publish them

The current map, read from vendor pages on 1 Oct 2026:

• FlowSprite AI Professional, EUR 99 per month: 10 users, 6 Salesforce connections.
• FlowSprite AI Enterprise, EUR 199 per month: 25 users, 20 Salesforce connections. Beyond that, a Custom tier by conversation.
• Gearset Automation (CI/CD) Starter, $550 per team per month: 5 orgs on CI/CD and 1 production org and no multi-org pipelines.
• Gearset Automation Teams, $1,100 per team per month: 15 orgs. Enterprise is quote-only.
• Hutte Core, from EUR 75 per user per month billed yearly, includes 1 project; Growth, from EUR 150, includes up to 2; each further project is EUR 115 per month, per the Hutte pricing page.

The units differ: that is the first finding. FlowSprite AI counts Salesforce org connections directly. The Gearset pricing page counts orgs per team on its automation line. Hutte counts projects, and its page does not translate a project into a number of orgs. Salto's pricing page prices by environment size and apps managed, with no public figures. Gearset's page shows "$" without naming the currency; FlowSprite and Hutte are in EUR.

A constructed map: six orgs today, nine next year

The following team is constructed, not observed. Four admins run one production org and five sandboxes: six Salesforce org connections today. A second business unit planned for Q3 2027 adds one production org and two sandboxes: nine orgs by Q4 2027. The assumption, dated 1 Oct 2026, is that one connection or one CI/CD org equals one Salesforce org.

Today's cut:

• FlowSprite AI Professional covers 6 of 6. EUR 99 x 12 = EUR 1,188 per year.
• Gearset Automation Starter covers 5 of 6, so the map forces Teams: $1,100 x 12 = $13,200 per year for the automation line. This excludes Gearset's per-user line, which the page prices separately ($215 per Gearset user per month on Starter).
• Hutte Core for four users is at least 4 x EUR 75 = EUR 300 per month, billed yearly, if the six orgs sit in one project.

Next year's cut, at nine orgs:

• FlowSprite AI moves to Enterprise: EUR 199 x 12 = EUR 2,388 per year. Nine of twenty connections are used, so the price per connected org is 199 / 9 = EUR 22.11 per month.
• Gearset Teams lists 15 orgs, so nine fit. The production-org allowance for Teams is not in the figures recorded here, so confirm two production orgs are allowed. Per org: 1,100 / 9 = $122.22 per month.
• Hutte, if the second business unit becomes a second project, is at least 300 + 115 = EUR 415 per month on Core, or 4 x 150 = EUR 600 on Growth, billed yearly.

Currencies differ, so these figures place plans on the map, not into a verdict.

What the flat connection cut optimises for, and what it gives up

A flat price capped on Salesforce org connections optimises for the admin team whose org count moves faster than its headcount: three more orgs cost one tier step, and another admin costs nothing until the user cap. On this map, FlowSprite AI Professional is the lowest listed tier whose cap covers all six orgs at today's count; on Gearset's automation line that takes Teams. The team's own AI drafts a Salesforce metadata change; FlowSprite AI lands it as a GitHub pull request in the customer's private repo. Changes are tested in a sandbox first, and a human approves before anything deploys. Production is never auto-touched, and the record lives in a repo the customer owns. Professional carries cross-org compare and drift detection; Enterprise adds separation-of-duties approvals and audit log export.

The limits are real. A team past twenty connections is back in a conversation for Custom pricing. Teams that need scratch-org pooling should look at Hutte, whose Core plan includes it, per its pricing page read 1 Oct 2026. Gearset and Hutte offer 30-day trials with no card, according to their pricing pages read 1 Oct 2026, against FlowSprite AI's 14 days with no card. Flosum and AutoRABIT pitch enterprise-scale release work, per their sites, read 1 Oct 2026. Copado's full DevOps platform is quote-only, according to its pricing page read 1 Oct 2026.

Observed versus inferred

Observed on 1 Oct 2026: the caps, prices and units above, from each vendor's page. Inferred: that connections, CI/CD orgs and orgs in Setup are the same thing; how Hutte maps orgs to projects; and Gearset Teams' production-org allowance. Confirm all three with the vendors in writing before acting.

The decision, its reversal cost, and the review date

The map supports buying the tier that covers the Q4 2027 count of Salesforce org connections, not today's. Reversal cost is the constraint: moving a pipeline and its history to another tool costs roughly one to two quarters of reduced change throughput for four admins, an illustrative estimate, not a measurement.

Review this map on 1 Apr 2027. Review earlier if a second production org is approved, because in this map that single event takes the org count past FlowSprite Professional's six connections and may add a Hutte project; on Gearset the map is already on Teams.