Your servers, your data
The full platform — intake, storage, analysis and console — runs on your Linux servers or cloud account. Vendor services are outbound-only and never needed at runtime.
data residency: 100% yoursObserveX is a self-hosted, AI-native platform for metrics, logs, traces and topology. It finds problems deterministically, explains them with evidence, and never sends your telemetry anywhere you didn't choose.
Built on proven, open foundations
SaaS monitoring asks you to ship every log line, trace and metric to someone else's cloud. ObserveX runs the whole platform inside your own network, and stays simple to operate.
The full platform — intake, storage, analysis and console — runs on your Linux servers or cloud account. Vendor services are outbound-only and never needed at runtime.
data residency: 100% yoursProblems come from baselines, anomalies and your live topology, so the same signals always give the same verdict. AI explains what happened and cites the evidence. It never decides on its own.
no language model in the coreMutual TLS 1.3 everywhere, a hybrid post-quantum key exchange, signed configuration, one-time enrollment, and masking of personal data at the source.
zero-trust between every componentEach part is a small, tested module with one job, so the whole platform is easy to reason about, operate and audit.
A watchdog with a lightweight core collects host and process metrics, log files and the systemd journal, and receives OpenTelemetry locally. A bounded disk spool keeps data safe through outages.
One binary, three modes — environment, cluster or embedded. It relays agents from segmented networks with quotas and backpressure.
Every series and record carries an entity ID. Services, processes and hosts are connected by calls, runs_on and instance_of, with a full System History of what changed and when.
Baselines learn normal behaviour for every entity. Anomalies are correlated over the topology into one Problem with one root cause, not an alert storm.
The default model runs inside your network. Every claim links to evidence you can open. Its tools are read-only, and actions always need a person's approval.
Agents send over mutual TLS, straight to a node or through a Gateway. The NGINX Front Door terminates TLS 1.3 on its own port. Three identical nodes, each with a Node Supervisor and one modular ObserveX Server, do the rest.
"checkout-api p95 latency rose from 180 ms to 920 ms at 14:02. It follows deploy #482 of payments-svc, which doubled its queries per request. Connection-pool waits on pg-primary-02 rose at the same moment."
The Agent gathers metrics, logs, traces and events, and masks personal data and secrets before anything leaves the host.
Baselines are calculated for every entity, with seasonality, in plain Go. Same input, same output, every time.
Only sustained deviations from the baseline count, so you don't get paged for a one-off blip.
Anomalies are joined along calls and runs_on relations into one Problem that names its root cause.
The AI Investigator writes the story with citations. Remediation is off by default and always needs a person's approval.
Banks, telecoms, healthcare and government run under strict data rules. ObserveX was designed from the threat model up.
Ask for the threat modelEvery Agent, Gateway, node and store authenticates with certificates. Identity comes only from the verified certificate.
X25519MLKEM768 hybrid key exchange is preferred, protecting today's traffic against harvest-now, decrypt-later attacks.
Agent settings are signed with Ed25519 and refused unless the signature verifies.
Enrollment tokens are single-use, hashed at rest and claimed atomically. Each Agent gets its own certificate.
Query parameters, headers, SQL literals and the fields you choose are masked before data leaves the host.
Every process logs through a redacting handler, backed by leak tests and fuzzing.
ProofChain hash-chains every admin change to an external anchor.
cosign signatures and SBOMs on every package, checked before install.
Keep transaction telemetry inside your regulated perimeter.
Observe large, segmented networks through Gateways.
Mask patient data at the source, before it leaves a host.
Air-gap friendly, with no vendor runtime dependency.
Follow a checkout from browser to database.
Watch on-premise plants and edge hosts from a single console.
"We needed full-stack visibility, but our regulator would never allow telemetry to leave our data centre. A self-hosted platform built on that model was exactly what we were looking for."
"One Problem with a root cause, instead of forty alerts at 3 a.m. That deterministic approach is what won our on-call team over."
"The security model reads like it was written by our own security team: mTLS everywhere, signed configuration, masking at the source."
Every module ships with its own tests and an architecture decision record. Here is where we are.
ObserveX Managed runs on your own infrastructure, so every installation is different. Our experts size the platform with you and send a quote that fits.
Tell us what you need to observe and we'll put together pricing for your setup.
ObserveX Managed is rolling out now. Tell us about your environment and an ObserveX expert will get back to you with pricing, sizing and next steps.
Prefer email? hello@observex.io
Or explore the demo firstOn your own Linux servers or in your own cloud account. A default cluster is three identical nodes. Each one runs a Node Supervisor, the NGINX Front Door, the ObserveX Server and the stores.
No. Intake, storage, analysis and the AI model all run inside your environment by default. Vendor-side services are outbound-only, optional and never needed at runtime.
No. Problems are found deterministically from baselines, anomalies and topology. The AI Investigator explains what happened and cites the evidence. Its tools are read-only, and any suggested action needs a person to approve it.
No. ObserveX uses bounded, disk-backed buffers in the Agent and Gateway, so there is no message bus to run.
Yes. The Agent receives OTLP locally, and code-level modules are OpenTelemetry-first. PromQL and LogQL are supported as query adapters on top of ObserveX's own API.
ObserveX Managed is priced for your environment, based on hosts, data volume and retention, cluster size and support level. Talk to our experts or email hello@observex.io for a quote.
Yes. ObserveX Managed is rolling out now. Our team helps you install it on your own infrastructure. Modules marked "Next" on the roadmap ship as they are completed.
The interactive demo walks through every ObserveX module with live, simulated data. No sign-up needed.