When a minor release drifts a DAC and the customization breaks at 6pm Friday, it's not Acumatica's phone that rings — it's yours. AcuOps is the team you weren't hired to be. Twelve probes, 146 post-publish tests, a CI/CD pipeline through the Customization API. Read-only API, session-gated. Credentials stay in your vault, not ours.
You've tried internal scripts. You've SSH'd into the instance when the client complains. Maybe a NetSuite-style monitoring add-on that doesn't know what a PXException is. None of them survive an Acumatica minor release.
Infor CloudSuite ships built-in environment monitoring. Sage Intacct has runbook integrations. Microsoft Dynamics 365 Business Central has AppSource partners that watch tenants. Acumatica has VARs stitching it together.
AcuOps is the thing that should have come in the box.
Twelve health probes. 146 post-publish tests. A CI/CD pipeline that pushes customizations through the Customization API. All three read-only against your clients' instances.
Continuous checks across Acumatica, HubSpot, MCP servers, and the infrastructure behind them. Acumatica doesn't tell you when a DAC field flips enum order. We do — within 90 seconds of the change landing.
Acumatica and HubSpot field changes caught automatically. A Slack alert fires the moment the environment your customization relies on moves under it. You find out before the backfill breaks.
Push to GitHub. Import and publish through the Customization API. Co-publish conflict checks, post-publish polling, automatic rollback signal. No manual uploads. No RDP to the instance. No "did it actually publish?"
Playwright runs the suite after every deploy. Schema checks, custom-field verification, pipeline validation, UI renders. If the customization broke the screen, you know 90 seconds after publish — not when the client finds out Monday morning.
Run the 146-test suite against the Acumatica upgrade candidate before it hits your client's production. You get the diff in Slack before the release notes land. If something breaks, it breaks in sandbox.
Every customization project, every pipeline, every health probe versioned in GitHub. Branch protection, PR gates, audit trail. "Who changed that field?" becomes git blame.
Point AcuOps at your client's Acumatica instance. Read-only API access, session-gated. Credentials live in your vault — we don't hold keys, we don't hold sessions between runs.
Twelve health probes run continuously. The CI/CD pipeline deploys customizations when you push to GitHub. 146 tests validate every publish against the live screen.
Slack notifications fire before your client does. You see every alert across every client. Your client sees only their own instance. Drill into dashboards for the stack trace.
AcuOps installs directly into your client's Slack workspace. They see their own alerts. You see everyone's. One event, two audiences, zero manual forwarding.
AcuOps drops into your client's existing Slack. No shared channels. No cross-workspace noise. Two dedicated channels, scoped to their instance:
Each client's data stays in their workspace. They never see your other clients or your internal channels.
Every notification also posts to your operator workspace. All clients, all alerts, one place:
One event, two audiences. Zero manual forwarding.
We send your client a one-click install link during onboarding.
They approve AcuOps in their Slack workspace. Ten seconds, no meeting required.
Channels are created automatically. Alerts start flowing immediately.
Not per seat. Not per transaction. Not per alert. The meter is the instance — one number, one invoice. Every capability included. Volume discounts at 10+ and 25+ instances.
We've priced this product three different ways. This is the one that survived first contact with our own client portfolio.
Your client's AP clerk and your VAR's senior architect are both running drift checks against the same DAC. Per-seat billing doesn't reflect the work. Instance-count does. One Acumatica tenant = $300/mo, regardless of who logs in or how many clerks open SO301000.
We thought about $0.10 per test run. We thought about a tier-bump at 50 deploys per month. Then we ran the numbers on our own portfolio. The cost-to-serve variance between a quiet month and a wild one is close to nothing. A flat meter means you know the invoice before the month starts.
Twelve probes running every few minutes. A 146-test Playwright suite against every publish. A CI/CD pipeline that handles Import, publishBegin, co-publish, publishEnd polling, and rollback signals. An on-call rotation that catches the indexer when it times out. Priced at what it takes to actually run the thing — which is the only price that survives a year.
Some VARs bill it straight through at cost. Some mark it up to $500 and make it a managed-service line item. We don't care. The meter is your Acumatica instance count — not seats, not clients, not end-customer invoices. What you do with the margin is yours.
If you're asking these, you're the right audience.
30-minute demo. We point AcuOps at a sandbox of your choosing and walk through what the probes, pipeline, and test suite catch. No slide deck.