Your first hour of a Pentaho outage
Most vendors publish an SLA number. This is what actually happens, minute by minute, when you page a senior AceMQ engineer.
You page us
Phone, email, or Slack — any channel reaches the on-call senior engineer directly. No web form, no tier-1 queue.
Named engineer live
A senior engineer who already knows your environment joins a live bridge. Zero cold-start, no re-explaining your topology.
Root cause isolated
Direct broker access, log and metric review, and a working hypothesis with a rollback plan before we touch anything.
Written RCA
Documented root cause, the fix applied, and the prevention steps — delivered after every P1, not just when asked.
SLA tiers, contractually guaranteed
Every tier reaches a senior Pentaho engineer. There is no tier-1 triage layer to get through.
Production down, messages not flowing, cluster or broker failure
Severe degradation, rising error rates, approaching capacity limits
Performance issues, configuration problems, non-critical failures
Questions, guidance, best practices, non-urgent improvements
Pentaho problems we fix every week
These are real symptoms from real Pentaho production environments — and the first thing our engineers check when one comes in.
Pentaho problems we've already solved
Representative engagements showing how these incidents get diagnosed and closed under an AceMQ support contract.
Everything in your Pentaho support contract
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
We support Pentaho wherever it's deployed
Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.
What you get that you don't get elsewhere
Named Engineers, Zero Cold Start
The same senior engineers stay on your account. They know your transformation inventory, your repository structure, and where the fragile jobs are — so a P1 starts with diagnosis, not an environment walkthrough.
No Tier-1 Triage Layer
You reach a senior Pentaho engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no approval process between you and someone who can fix it.
We Still Know Kettle Deeply
Most consultancies have moved on from Pentaho entirely. Our engineers still work in PDI transformations regularly, which matters when the fix requires actually understanding step-level behavior, not just restarting a service.
Genuine Follow-the-Sun Coverage
Engineers across 26+ countries and every time zone. Your overnight batch failure is someone's mid-afternoon — no waiting for a region to wake up.
Honest About Maintain vs. Migrate
We will tell you plainly when a Pentaho deployment is stable and cheap to keep running, and when the maintenance burden or end-of-life risk means migration is the better financial decision. Neither answer earns us more retainer revenue than the other.
Full-Stack, Not Just the ETL Tool
Pentaho problems are frequently JDBC driver, JVM, OS patch, or database-side problems wearing a Pentaho error message. We diagnose across the whole stack because that's where root causes usually live.
Pentaho support questions
Talk to a Support Expert
Send us a message and we'll follow up within one business day — or book a free 30-min consultation directly.
305-204-2607info@acemq.comMiami, FL 33130
Prefer to talk now? Call us directly or use the consultation tab to find a time that works.