Free vs Pro — when does it pay off?
Honest math on when the $99/mo Pro plan becomes obvious vs. when Free is still fine.
The Free tier is genuinely usable, not a 14-day trial. The Pro plan exists for people whose actual workload no longer fits inside Free's limits. This page is the honest math on when you've crossed that line.
What you get on Free
- 3 sources. CSV uploads, SQL DBs, OAuth-backed apps — any combination.
- 1 concurrent long-running job. You can queue more; they run one at a time.
- Full feature parity on everything else: workbench, review queues, audit log, lineage, exports, all 9 MCP tools, full survivorship-rule editor.
- No row caps. Golden Suite doesn't bill on data volume. Whether you dedupe 100 customers or 1.2 million, Free covers it.
Free is not time-limited. People run on Free indefinitely; that's fine.
What you get on Pro
- 25 sources (vs. 3 on Free).
- 5 concurrent long-running jobs (vs. 1).
- Priority dispatch on the shared Arq worker pool — your jobs land in front of Free users' queue. Not a separate cluster, but a meaningful latency win during busy periods.
- Direct email support instead of the public issue tracker.
$99/mo or $948/year (20% off annual). No row caps, no per-source surcharge, no overage bill.
When Pro pays off
The honest break-points:
You have more than 3 actual sources
"More than 3" doesn't mean "I might add a fourth eventually". It means right now, you have 4+ systems that need to land data in Golden Suite. CRM + Stripe + HubSpot + warehouse export = 4 sources. Add a support tool's contact dump = 5. Once you're past 3 and not pruning, you've crossed the line.
Don't upgrade pre-emptively. Stay on Free until you're hitting the quota_exceeded error in real use.
You're running parallel pipelines
1 concurrent job means: kick off a goldenmatch.dedupe on the customer dataset, wait for it, then kick off the goldenflow.standardize on the vendor list. If your team's workflow is "dedup customers, then while that's running, profile the new product feed, then re-run when both are done" — that's a 3-concurrent-job week, and Pro saves you literal hours per week.
You want priority in the shared pool
On Free, your jobs run alongside everyone else's on the same Arq worker pool. Most of the time this is fine — the pool is sized to handle multiple Free customers comfortably. During busy windows (Monday mornings, end-of-quarter data refreshes), Pro's priority dispatch jumps you to the front. If your team has a daily SLA for "the dedup'd customer feed is in BI by 9am", that's a Pro feature.
You're shipping to production
The dollars matter less than the support path. Pro gets direct email; Free gets the public issue tracker (still responsive, but not SLA'd). If you're putting Golden Suite into a workflow your team depends on, the support upgrade is the easiest justification — far cheaper than building the same tool internally.
When Pro is not worth it
- You're evaluating. Stay on Free. The product is the same; the only thing you're saving is time.
- You have ≤3 sources and one user. Pro's quota lifts don't matter to you.
- Your matching scope is "an occasional one-off CSV cleanup". That's a Free use case, and we'd rather keep you as a happy Free user than push an upgrade you don't need.
Upgrading
/pricing → "Get Pro" button. Stripe checkout, no sales call required. Cancel any time from the Clerk billing portal; downgrades take effect at the next billing cycle (you keep Pro features through the period you've already paid for).
If your situation needs concurrent caps higher than 5, or you have privacy/PPRL requirements, that's the Enterprise tier — different shape, different pricing.
A simple decision rule
If you're reading this page and asking "should I upgrade?", you probably should — that question doesn't come up unless your workload is starting to feel the friction.
If you're not asking, Free is fine. Stay there.