Comparison · Migration guide · 2026
Lumen Apex Cloud
Apex Cloud is a polished, batteries-included platform — and for many teams it is the right call. Lumen is the better fit if you want your telemetry in plain SQL, the option to self-host, and pricing that does not surprise you. Here is the honest, line-by-line comparison.
The comparison
Line by line, no spin
Where Apex Cloud is stronger, we say so. 7 of 10 rows are genuine differences — flip the switch to hide the ties.
| Capability | Lumen | Apex Cloud | Notes |
|---|---|---|---|
| Pricing model | Usage-based, capped Advantage | Per-host + per-seat Partial | Apex bundles more out of the box; Lumen bills on ingested volume, so spikes are predictable and idle hosts cost nothing. |
| Self-hosting | Full, OSS core Advantage | SaaS only Not available | Apex is SaaS-first by design and very good at it. If data residency or air-gapped installs are a requirement, only Lumen can run in your VPC. |
| Query language | Standard SQL Advantage | Proprietary DSL Partial | Apex’s DSL is expressive once learned. Lumen exposes telemetry as tables you query with the SQL your team already writes. |
| Time to first dashboard | ~1 day Partial | Minutes Advantage | Credit where due: Apex’s guided agents and prebuilt dashboards are genuinely faster to a first signal. |
| Integrations catalog | 90+ sources Partial | 600+ sources Advantage | Apex’s ecosystem is larger and more mature. Lumen covers the common stack and speaks OpenTelemetry natively. |
| Data retention | 30 days, tunable Parity | 15 days, extendable Parity | Both let you extend retention for a fee; defaults differ but the ceilings are comparable. |
| Alerting & on-call | Rules + anomaly Parity | Rules + anomaly Parity | Roughly at parity. Both ship rule-based and statistical alerts with the usual paging integrations. |
| Data portability | Export anytime Advantage | Export via API Partial | Apex supports export through its API. Lumen stores in open columnar formats you can copy out with no gatekeeping. |
| Support | Community + paid Partial | 24/7 enterprise Advantage | Apex’s 24/7 enterprise support and named TAMs are a real strength for large orgs. Lumen offers paid SLAs on top of an active community. |
| Compliance (SOC 2, ISO) | SOC 2 Type II Parity | SOC 2, ISO 27001 Parity | Both meet the bar most procurement teams ask for; confirm the specific certifications you need. |
The migration
Switch without a maintenance window
Migrations fail when they are a big-bang weekend. This one runs both platforms in parallel, so you can back out at any step.
-
Dual-ship, zero downtime
Drop the Lumen collector next to your Apex agents. Telemetry flows to both — nothing is turned off yet.
lumen agent install --alongside apex -
Import your dashboards
Convert existing Apex dashboards and monitors automatically. Review the diff before you keep them.
lumen import --from apex --dry-run -
Validate in parallel
Run both stacks for one billing cycle. Compare alerts and numbers side by side until you trust Lumen.
lumen verify --against apex --window 30d -
Cut over and retire
Point your on-call routes at Lumen, then remove the Apex agents. Your history came along in step 2.
lumen cutover --retire apex-agents
The switchers
Teams that made the move
Placeholder quotes — swap in real, named customers before launch.
We kept Apex for a quarter while we trusted Lumen. The dual-ship made it a non-event — no one outside the platform team noticed the switch.
Querying telemetry in plain SQL meant our analysts could self-serve dashboards. That alone paid for the migration.
Apex was great, honestly — we left for data residency, not because it was bad. Self-hosting Lumen in our own VPC closed that gap.
The objections
The honest answers
The four reasons teams hesitate — addressed without the sales gloss.
Will I be locked into Lumen the way I worry I am with any vendor?
No. The Lumen core is open source and stores in open columnar formats. You can export your data at any time and self-host the whole platform. The honest counterpart: Apex also lets you export, but only through its API and on its terms.
How does pricing actually compare?
Lumen bills on ingested volume with a hard cap you set, so a traffic spike will not produce a surprise invoice. Apex bills per host and per seat, which is simpler to predict for stable fleets but scales with headcount. Model both against your real volume — neither is universally cheaper.
My team knows Apex’s query DSL. How steep is the learning curve?
If your team writes SQL, Lumen needs almost no new query language — telemetry is just tables. The trade-off is real, though: Apex ships more prebuilt dashboards, so you reach a first signal faster there. We narrow that with the dashboard importer in step 2.
What about support once we have left Apex?
This is where Apex is genuinely strong: 24/7 enterprise support and named TAMs. Lumen offers paid SLAs and an active community, and self-hosting means your team can inspect and fix issues directly. For some orgs that is more control; for others, Apex’s white-glove support is the better fit — be honest about which you are.
Ready when you are
Start the migration — keep Apex running
Dual-ship in an afternoon, validate for a cycle, cut over when you trust the numbers. No weekend maintenance window, no rip-and-replace.
Static demo — the form does not submit anywhere.