Is OpsMerge for shops as small as Action1 fits?

It can be. We do not have a free tier comparable to Action1. The cost calculus only makes sense once you need a real PSA and recurring billing.

Can I run OpsMerge alongside Action1?

Yes during a pilot window. Both agents will co-exist on endpoints. Typically Action1 is uninstalled once OpsMerge patching has been validated.

What does OpsMerge add over Action1?

A real PSA, a billing engine, a client portal, asset-based auto-counting, domain monitoring, reporting and integration with QuickBooks Online. Action1 is a patch tool, not a platform.

Will OpsMerge ship a free tier?

Unlikely. We would rather charge fairly than gate the product behind feature limitations. The closed beta substitutes for a free tier during the lead-up.

OpsMerge vs Action1

A platform beats a patcher.

Action1 is a genuinely good patch tool with a generous free tier. It's also a patch tool, not a full RMM, no PSA, no billing engine, no client portal. OpsMerge ships the platform you actually run an MSP on.

Apply for closed beta

Action1 has built a real following with two simple choices: free up to 100 endpoints and a focused patching product that does its job well. If you're a micro-MSP running 30 endpoints across two clients, Action1 plus a generic helpdesk plus a spreadsheet might be all you need. We'd respect that and tell you so.

The moment you outgrow that, multiple clients, recurring contracts, ticket SLAs, asset-based billing, a branded client portal, you're past Action1's scope. The platform is built for endpoint hygiene, not for running an MSP. OpsMerge is built for running the MSP.

Feature-by-feature

OpsMerge vs Action1 feature comparison
Capability	OpsMerge	Action1	Notes
Full RMM agent (telemetry, scripts, remote)	Yes	Partial	Action1 is patch-led, full RMM telemetry surface is thin
Real PSA / ticketing	Yes	No	No PSA in Action1, you need a separate tool
Asset-based auto-billing	Yes	No	No billing engine in Action1
Client portal	Yes	No	No portal, clients have nowhere to log in
Patch management	Yes	Yes	Action1 is genuinely good at this, credit due
Scripts & automation	Yes	Partial	OpsMerge: PowerShell / Bash / Python on every endpoint
Domain monitoring built-in	Yes	No	SSL / DNS / WHOIS / DMARC server-side checks
Region-based data residency	Yes	Optional	OpsMerge: EU and US regions live; AP on the roadmap
Free tier	Closed beta	Yes (≤100 endpoints)	Honest concession, Action1 has a real free tier
Best fit MSP size	1-30 techs	Single endpoint admin / micro-MSP	Different scopes entirely

Where Action1 is better

Free tier, genuinely free up to 100 endpoints. No card. No catch.
Patch focus, does one thing well rather than trying to be everything.
Onboarding speed, sign up, install agents, you're patching.
Solo IT use case, if you're an internal IT admin patching 60 endpoints, you do not need OpsMerge.

If your "MSP" is one person, three clients, and 80 endpoints, Action1 plus a Trello board genuinely is enough.

Where OpsMerge wins

It's a platform, RMM, PSA, billing, portal, automation, all on one database. Action1 is one slice of that.
Real billing engine, recurring contracts, asset-based auto-counting, void-with-rollback, QBO push.
Real PSA, SLAs, time tracking, email-to-ticket, asset linking, branded portal.
Client portal, your clients log in with an invite-and-password link. Passwordless magic-link in design.
Regional data residency, EU and US regions live; AP on the roadmap.
One bill, you stop paying for four tools that don't talk to each other.

Pricing posture

OpsMerge vs Action1 on pricing

Action1 is free up to 100 endpoints and offers paid tiers above that. The headline price is genuinely attractive, the full-stack cost is what you pay for the PSA, billing, portal and reporting tools you bolt around it.

Action1: Free at small scale + paid above 100 endpoints
OpsMerge: Flat per-MSP, public in GBP at GA
Action1: Patching only, bring your own PSA / billing / portal
OpsMerge: Full platform on one database
Action1: Multi-tool reconciliation tax
OpsMerge: One bill, one platform, no reconciliation

Migration

Coming from Action1? Here's what changes.

Action1 isn't a like-for-like migration, you're upgrading from a patch tool to a full platform. Most Action1 users keep it running for a window while OpsMerge takes over patching plus everything else.

Asset import
Action1 endpoint export → OpsMerge asset register. Hostname-keyed merge.
Agent swap
OpsMerge agent installed alongside. Both can co-exist during a pilot ring; Action1 uninstalled when confident.
Patch policy rebuild
Action1 patch policies translate cleanly to OpsMerge patch policies. KB blocklists transfer.
Stand up the bits Action1 doesn’t have
PSA, billing contracts, portal branding, client onboarding, done during OpsMerge onboarding.

Realistic timeline: 1-2 weeks for a 100-endpoint, 2-client micro-MSP.

What MSPs moving up from Action1 tell us

Beta is closed and quiet. Once we have real customer quotes, they'll land here. We don't fake them.

Common questions

Is OpsMerge for shops as small as Action1 fits?
It can be. We do not have a free tier comparable to Action1. The cost calculus only makes sense once you need a real PSA and recurring billing.
Can I run OpsMerge alongside Action1?
Yes during a pilot window. Both agents will co-exist on endpoints. Typically Action1 is uninstalled once OpsMerge patching has been validated.
What does OpsMerge add over Action1?
A real PSA, a billing engine, a client portal, asset-based auto-counting, domain monitoring, reporting and integration with QuickBooks Online. Action1 is a patch tool, not a platform.
Will OpsMerge ship a free tier?
Unlikely. We would rather charge fairly than gate the product behind feature limitations. The closed beta substitutes for a free tier during the lead-up.

Outgrowing Action1?

Apply for the beta. Tell us how many clients you have and we'll tell you whether OpsMerge fits your shape yet.