The OpenTelemetry backend that doesn't lock you in
Instrument once with vendor-neutral OpenTelemetry SDKs, point your OTLP exporter at AllStak, and get waterfall traces, a service map, and percentile analytics.
Instrument once. Choose your backend freely.
OpenTelemetry solved half the observability problem: one vendor-neutral standard for instrumenting your code, so you never rewrite tracing when you change tools. The other half is where you send the data. Proprietary agents and per-host APM pricing quietly rebuild the lock-in OTel was designed to remove — and on platforms like Datadog, the bill grows with every host and every gigabyte.
AllStak is an OpenTelemetry backend in the simplest sense: it accepts OTLP trace export over HTTP, no proprietary agent required. Point your existing exporter at AllStak and your spans render as waterfall traces with a service map and p50/p95/p99 latency analytics, next to your errors, logs, and uptime in one platform. Your instrumentation stays standard OTel — if you ever want to leave, you change one endpoint. That is what an OpenTelemetry APM should cost you: a config line, not a migration.
What you get when OTLP traces land in AllStak
Standard OpenTelemetry in, full tracing experience out — without trading away the vendor neutrality you instrumented for.
OTLP traces over HTTP
AllStak accepts OTLP trace export over HTTP from any OpenTelemetry SDK or collector — change the endpoint and spans start flowing.
Vendor-neutral by design
No proprietary agent and no custom instrumentation format. Your code speaks standard OTel, so switching in — or out — is a config change, not a rewrite.
Waterfall trace view
Every trace renders as a span-by-span waterfall with timing, so you see exactly where a request spent its time across services.
Service map from your spans
Your OTel spans build a live map of how services call each other, giving you an architecture view that is always as current as your traffic.
Trace analytics & percentiles
p50/p95/p99 latency analytics across your OTel traces show which operations are slow for real users, not just on average.
One platform around your traces
OTel traces land next to error tracking, logs, uptime, and infrastructure monitoring in the same AllStak project — one platform, one bill.
Point OpenTelemetry at AllStak in minutes
- 1Create a free project
Sign up at app.allstak.sa, create a project, and copy your API key. No credit card required on the free tier.
- 2Configure the OTLP exporter
Set your OpenTelemetry SDK or collector to export traces over OTLP HTTP to AllStak with your API key. The full walkthrough is at /docs/guides/opentelemetry.
- 3Deploy & verify
Ship the config change and watch your first traces arrive as waterfalls in the dashboard — your instrumentation itself doesn't change at all.
- 4Explore the map & percentiles
Use the service map and p50/p95/p99 trace analytics to find slow operations, and link traces to errors and logs in the same platform.
Why OTel teams choose AllStak as their backend
- Keep your instrumentation vendor-neutral — standard OTLP in, no proprietary agent, no rewrite if you ever switch.
- Pay a predictable bill instead of Datadog-style per-host APM pricing that climbs with every server you add.
- Get a real tracing experience — waterfalls, service map, percentile analytics — not just raw span storage.
- See traces next to errors, logs, uptime, and infrastructure in one platform instead of an OTel backend bolted onto four other tools.
- SAR pricing and data residency in Saudi Arabia, with a dashboard in English and Arabic.
- Migrating is one config change — and so is leaving. That's the point of OpenTelemetry.
OpenTelemetry backend FAQ
What is an OpenTelemetry backend?
OpenTelemetry SDKs instrument your code and export telemetry in the standard OTLP format, but they don't store or visualize anything — that's the backend's job. AllStak acts as that backend for traces: it ingests OTLP trace export over HTTP and turns your spans into waterfall traces, a service map, and latency analytics.
Does AllStak accept OTLP metrics and logs too?
Today AllStak accepts OTLP trace export over HTTP. Metrics, logs, errors, uptime, and infrastructure data flow in through AllStak SDKs and agents instead, and everything lands in the same platform. See /docs/sdks/opentelemetry for current OTel support.
How do I migrate from Datadog or another APM?
If your services are instrumented with OpenTelemetry, migration is a config change: point the OTLP exporter (or your collector pipeline) at AllStak's traces endpoint with your API key. You can even run both backends in parallel during the switch. The setup guide at /docs/guides/opentelemetry walks through it.
Is AllStak cheaper than Datadog for OTel traces?
Datadog APM is priced per host plus ingestion and retention, so costs scale with your fleet. AllStak uses predictable plans with SAR pricing and a free tier to start, and your traces live in the same bill as errors, logs, and uptime — one platform instead of separately metered products.
Where is my trace data stored?
AllStak offers data residency in Saudi Arabia, which matters for Saudi and GCC teams that need telemetry to stay in-region. You get an OTel-native backend without shipping your trace data overseas.
Explore more
Point your OTLP exporter at AllStak — free
Keep your OpenTelemetry instrumentation exactly as it is, change one endpoint, and get waterfall traces, a service map, and percentile analytics — on one platform with one predictable bill.