Skip to content
Ritele
DocsDownload

Self-hosted OpenTelemetry · one container

See your real system. Know what breaks first.

Ritele maps your architecture from the telemetry your services already send, shows what’s breaking and why, and what gives out first.

docker run -p 4317:4317 -p 4318:4318 -p 8080:8080 -v ./data:/data ritele/ritele

Self-hosted. Free up to 20 services per environment.

Nobody drew this. Every box and line came from live telemetry.

The platform

Metrics, traces and logs, joined on one map of what runs.

What do I run?

A map nobody has to draw.

Every service, database and queue, from the traces you already send, checked against the diagram your team approved.

Explore the system map ↓
What’s wrong right now?

From the status to the line that explains it.

A plain status for every component, the failing request, and the log line it wrote.

See incident investigation ↓
What breaks next?

What gives out at ×5, before it does.

Load and limits from metrics, paths from traces. Each answer says how sure it is.

Explore capacity planning ↓
One week, one team

A payments team. A three‑year‑old diagram. An audit on Friday.

On Monday, the CTO asks a simple question: who understands how checkout actually works, end to end? Follow the week as Ritele connects the architecture, telemetry, and evidence to help the team find out.

Map · Monday · 14:00

Nobody can answer the CTO’s question from the old diagram. Tunde points OpenTelemetry at Ritele instead.

By the afternoon, the team can see what actually runs.

  • Ritele draws services, databases, queues, caches, gateways and external APIs from live traces, grouped by domain and sized by traffic.
  • When traffic comes from a caller it can’t identify, Ritele marks it “?” and counts it. It doesn’t guess.
Next: Tuesday, checkout slows down →
Metrics · Tuesday · 09:46

Checkout slows down, and the cause isn’t on the diagram.

The worst problem is at the top of the list.

  • Every component has a status, with the numbers behind it and the signals it was judged from.
  • Each issue shows when it started, which entry points it hurts, and the deploys around it.
Next: follow one slow request →
Traces + Logs · Tuesday · 09:49

Three minutes later, Tunde opens one of the slow checkouts.

One request, followed to the line that explains it.

  • The trace shows the request crossing each service, with the failing call highlighted.
  • Ritele reads matching lines from your own Loki on demand, masked and audited. Each trace_id links back to the trace.
Next: ask what happened →
Advisor · Tuesday · 10:05

Before writing the incident note, Tunde asks one question.

One answer, with the evidence attached.

  • The Advisor answers from metrics, traces and logs together, and names the components on the map.
  • It’s off by default. Point it at a model inside your network and nothing leaves.
Next: Thursday, planning for ×5 →
Prediction · Thursday · 14:00Growth plan

The fix shipped on Tuesday. Next month’s launch should bring five times the traffic.

What gives out first at ×5?

  • Describe the change, and Ritele lists what fills up, in order, at what multiple and why.
  • Each answer states how confident it is. In simulator tests across 15 system shapes, it was never late on what gives out first.
Next: Friday, the audit →
Map · Friday · 09:00Growth plan

The CTO’s question finally gets an answer.

The auditors get the architecture that actually runs.

  • Import the approved diagram as Structurizr, Mermaid or CSV, and Ritele flags new components and unexpected dependencies.
  • Export the observed map as PNG, SVG, Mermaid or Structurizr for the audit file.
Next: where your data stays →
Security

One container, on your servers. Your telemetry stays put.

Runs on your servers

Embedded storage for small installs; Postgres and ClickHouse for larger ones.

Telemetry stays in your network

Unless you enable the Advisor or an alert channel. Both are off by default.

Licences verify offline

The key is checked locally. No call home to keep it working.

One daily usage ping is on by default. RITELE_USAGE_PING=false stops it.

Security details →
pricing

Start free. Pay when you outgrow it.

One licence per organisation. No per-user seats, no usage metering. Each plan carries its own limits.

A service sends its own traces. Each environment counts its own services, once per service.name. Databases, queues, caches and external APIs are not counted. An environment is one copy of your system — production, staging, and so on.

Billing period

Free

To map one system

$0

No account. No card.

Start

Limits

  • 1 environment
  • 20 services per environment
  • 10 hosts
  • 1 notification channel

Features

  • Snapshots kept for comparison
  • Health of every component
  • Hosts and the machines under each service

Growth

For one platform team

$90/ month

One payment · $1,080 for 12 months

Buy a licence

Limits

  • 3 environments
  • 75 services per environment
  • 50 hosts
  • 5 notification channels

Everything in Free, plus:

  • What-if, on the real graph
  • Intended model, checked against what runs
  • Drift triage when the two diverge
  • Architecture review (Advisor)
  • SLOs on the real graph
  • PagerDuty, Opsgenie and Alertmanager, owner routing and maintenance windows

Scale

For a whole engineering org

$360/ month

One payment · $4,320 for 12 months

Buy a licence

Limits

  • 10 environments
  • Unlimited services per environment
  • 250 hosts
  • Unlimited notification channels

Everything in Growth, plus:

  • Architecture review on your own model endpoint
  • Single sign-on through your identity provider (OIDC)

Enterprise

For terms of your own

Custom

Annual invoice · PO and bank transfer

Talk to us

Limits

  • Environments as agreed
  • Services per environment as agreed
  • Hosts as agreed
  • Notification channels as agreed

Everything in Scale

    In every plan

    • OpenTelemetry traces and metrics on one live map
    • Logs stored and searched in Ritele, or read from your own Loki
    • Architecture drawn from your traces
    • Unlimited users, each a viewer, editor or admin
    • Self-hosted on your own servers

    How is a licence delivered?

    As a text key by email. Paste it into Settings → Licence, or set RITELE_LICENCE_KEY. The key is checked on your install; licensing never calls home.

    What happens when it expires?

    The install drops to the free tier at the expiry date and keeps running. Data is untouched. We warn you 30 days ahead.

    Is there a trial?

    You don't need one; the free version is free for good, with 1 environment and 20 services. Move to Growth when you outgrow it.

    What are Advisor units?

    Advisor is priced in units: one unit is one Advisor message, and larger actions like reviews cost more, as shown on the rate card. Growth includes 150 units a month. They reset monthly and don't roll over. Need more? Top-up packs last 12 months and are used after your monthly units.

    How can I pay?

    By card in naira or US dollars, or by bank transfer in naira to an account we create for your order.

    next monday

    Start your own week.

    One container. Point OpenTelemetry at it. Open the UI.

    docker run -p 4317:4317 -p 4318:4318 -p 8080:8080 -v ./data:/data ritele/ritele
    • Self-hosted, one container
    • Free up to 20 services per environment at launch