Per-endpoint creep
Per-endpoint pricing punishes you for growing. Quote calls hide what you actually pay.
Appearance
Built by an MSP, for MSPs
One platform. One bill. No middleware to babysit.
RMM, PSA, billing, automation, reporting and the customer side of the shop. The bits that should talk to each other actually do.
Run tickets, endpoints, billing, automation and the customer-facing stuff from one screen. Closed beta · UK MSPs first · EU and US regions live · AP next.
Closed beta in motion. We don't fake customer logos.
Pricing
Two plans. The price is on the page.
Flat per-MSP. Not per-endpoint. Not per-tech. Onboard a new client and the bill stays put. Pounds, monthly or annual, no quote call, no auto-renew traps.
See the pricingThe problem
Tool sprawl is the MSP tax.
Most MSP stacks split RMM, PSA, billing, automation, reporting, and customer workflows across separate vendors, glued together with brittle integrations and a Zapier subscription that nobody owns. The work flows through every tool; the data and the bill don't. When one vendor hikes its price, you eat it. When another gets bought, you eat it. When the integration breaks at 2am, you eat it.
Brittle glue
More tools means more release cadences and more places for the integration to break overnight.
Vendors get bought
Once a tool is acquired, the roadmap drifts and the support email goes quieter. We took notes.
Before vs after
The contrast, in one screen.
No charts. No buzzwords. Just the day-to-day.
Before, your current stack
- 4 tools. RMM, PSA, billing, accounting glue.
- Per-endpoint pricing. Growth is taxed.
- Manual billing. Spreadsheet reconciliation each month.
- Re-key everything. Quote → invoice → accounting → ledger.
- Threading bugs. Tickets lost to Re: Re: Re: chains.
- Broken integrations at 2am. Six release cadences, six places to look.
- Quote-call pricing. Sales motion before you can compare.
- Vendor gets bought. Roadmap drifts. Support gets quieter.
After, OpsMerge
- 1 platform. One SPA, one data model, one event bus.
- Flat per-MSP. Grow without re-quoting.
- Auto billing. Live agent fleet auto-counts to invoice lines.
- Atomic quote acceptance. One click spawns invoice, ticket and project.
- Message-Id threading. Replies match the right ticket. Always.
- One place to look. One release stream. One inbox. One platform.
- Public pricing. GBP on the page at GA. No quote call. Ever.
- Bootstrapped, founder-led. Ex-MSP at the wheel. Nobody to sell us to.
Product tour
Three pillars. One platform. One screen.
RMM, PSA and billing share rows, jobs and the same SPA. Click a tab to see them sit next to each other.
248 endpoints across 12 clients. Always-connected, real-time.
SLA timers running. Tickets reference live agents.
Invoice lines auto-counted from the live RMM fleet.
What's in the box
Twelve pillars. One platform. No middleware to babysit.
RMM, PSA, billing and the rest share one data model and one screen. They fit because we built them to fit, not because we wired them up later.
A real workflow
The monthly billing run.
No fluff. Just the flow.
- 01
Agents check in
Endpoints report in across the month. Asset rows update with hostname, OS, patch state, the lot.
- 02
Assets counted
Billing day arrives. Each contract line counts its billable assets off the live fleet and writes a snapshot you can audit later.
- 03
Invoice generated
Invoice writes with the snapshotted lines and VAT computed from the mapped tax codes. Pushes to QuickBooks or Xero in the same step.
- 04
Invoice sent
PDF goes out to the client. Payment lands in QuickBooks or Xero, the webhook tells OpsMerge, and the invoice closes itself.
No spreadsheet reconciliation. No copy-paste between tools. No "wait, did we count the new endpoints?" The fleet is the register. The register drives the invoice. That's it.
Architectural numbers
Boring choices, on purpose.
0
OS targets covered (Windows, macOS, Linux)
0
shared data model across the platform
0
per-endpoint surprises
0
regions live today (EU + US), AP next
From the field
What beta operators are saying
Beta is closed and quiet. Once we have real customer quotes, they'll land here. We don't fake them.
How we compare
We built this because the alternatives didn’t fit.
Common questions
The bits people email us about
Is OpsMerge production-ready?
The platform is in closed beta with paying-on-pause status. The core RMM agent and ticketing flows are running production workloads at the founding MSP today. We are admitting beta participants in small cohorts so we can fix things fast.What is the pricing going to be?
GBP, monthly or annual, flat per MSP — not per endpoint. RMM, PSA, or bundle. Public on the pricing page when GA pricing unfreezes. No quote call ever.Where is the data hosted?
Cell-based. The EU cell is live today on EU infrastructure, behind a managed edge / DDoS layer. Account data, agent telemetry and ticket email traffic stay inside the cell you signed up to. UK Data Protection Act + EU GDPR for the EU cell. US and AP cells on the roadmap.Will OpsMerge replace my existing PSA / RMM?
That is the goal. Migration tooling is being built per integration (NinjaOne, Atera, SuperOps, HaloPSA next). If you are coming from one of those, flag it on the application — we will tell you exactly where we are.Who is behind this?
Brindleford Technologies Ltd, UK company 16871436, founded by Doug Hall — ex-MSP owner / operator with seventeen years running a UK shop.
Fancy a go on the closed beta?
Tell us your shop size, what you're using today, and what you'd want to move across first. We reply to every application, even the ones we can't take this round.
Closed beta is open. UK MSPs first.Join the Beta