Early access is open. Free plan during early access. Start free
Logthread

Early access · Logs, traces and metrics

The whole story behind every log line.

Send logs, traces and metrics with the tools you already use. Search for anything, and Logthread shows every related event across your services as one timeline, with the first error pinned.

Free plan during early access. Data stored in India.

Explore · Show full storyProduct UI
Product UI recreation of a story: one request across three services, laid out as a timeline with the first error pinned. Sample data.

Product

Built around one question: what happened?

Explore

Search any field without designing labels or indexes up front.

  • Facets
  • Severity histogram you can drag to zoom
  • Expand any event as formatted JSON
  • Surrounding context for any line
  • Shareable URLs
ExploreProduct UI
Product UI recreation of Explore: facets, a severity histogram and matching log lines. Sample data.

How it works

From first log to full story in three steps.

  1. 01

    Create an ingest key

    Sign up and create a key in onboarding. Keys are write-only and shown once.

  2. 02

    Point your collector at Logthread

    Use OpenTelemetry, Fluent Bit, Vector, rsyslog or plain curl. Onboarding gives you copy-paste snippets.

  3. 03

    Search, then open the story

    Find any line, then see every related event across your services, in order.

Send JSON lines with curl
curl -X POST 'https://<your-ingest-endpoint>/v1/ndjson' \
  -H "Authorization: Bearer $LOGTHREAD_INGEST_KEY" \
  -H 'Content-Type: application/x-ndjson' \
  --data-binary $'{"service":"my-app","severity":"INFO","body":"Hello, Logthread"}\n'
Or configure an OpenTelemetry SDK
export OTEL_SERVICE_NAME="my-app"
export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-ingest-endpoint>"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer%20$LOGTHREAD_INGEST_KEY"

Your endpoint and key appear in onboarding after sign-up.

Delivery, security and data

Keys that can only write. Access you control.

Ingest keys can send logs, traces and metrics, never read them.

Delivery you can rely on

  • Logs are acknowledged only after they are durably queued
  • If storage is unavailable, logs wait in the queue and are delivered when it recovers
  • At-least-once delivery

Security and access

  • Write-only ingest keys, shown once
  • Revoke any key at any time; only a hash is stored
  • Email-verified accounts
  • Team roles: owner, admin, member, viewer
  • Invitations by email
  • Active-session management
  • Audit log of account and key changes

Data stored in India

Your logs, traces and metrics are stored in the Mumbai region.

  • Fully managed: nothing for you to run or operate

Integrations

Works with standard tools.

Use the open standards you already run. Onboarding has copy-paste snippets for each.

  • OpenTelemetry SDKNode.js
  • OpenTelemetry SDKPython
  • OpenTelemetry SDKJava
  • OpenTelemetry SDKGo
  • OpenTelemetry SDK.NET
  • OpenTelemetry CollectorOTLP HTTP
  • OpenTelemetry CollectorOTLP gRPC
  • KubernetesOTel Collector Helm chart
  • Fluent Bit
  • Vector
  • PrometheusRemote write 2.0
  • FluentdForward over TLS
  • rsyslog
  • syslog-ngSyslog over TLS
  • curlJSON lines
  • LiveKitServer, SIP, Cloud

Available today

What you can use right now.

Everything here is built and running in every workspace during early access.

  • Available

    Explore

    Search any field with facets, a draggable severity histogram, formatted JSON and surrounding context.

  • Available

    Full story

    Every related event across services, grouped by correlation id, as one timeline with the first error pinned.

  • Available

    Live tail

    Stream logs as they arrive, filtered by service, severity or text.

  • Available

    Patterns

    Repeated lines grouped into templates, with trends and new-pattern detection.

  • Available

    Alerts

    New-pattern, error-spike, scheduled-query, metric-threshold and span-latency rules, delivered to email, Slack, Teams, Discord, PagerDuty, Opsgenie, FireHydrant, webhooks and 90+ more services, each linking to its evidence.

  • Available

    Pipelines

    Parse, filter, sample, deduplicate and route logs before they are stored, with live before/after preview, versions and rollback.

  • Available

    PII redaction

    Mask cards, Aadhaar, PAN, emails, phone numbers and secrets in logs at ingest, before storage.

  • Available

    Collectors

    OTLP over HTTP and gRPC for logs, traces and metrics, Prometheus remote write 2.0, JSON lines, syslog over TLS and Fluent Forward over TLS.

  • Available

    LiveKit

    Plug-and-play LiveKit server, SIP and Cloud: signed webhooks, Prometheus metrics, logs and agent log drains, grouped by room into one story, with ready-made dashboards.

  • Available

    Usage

    Ingest by signal, storage and query usage per workspace, daily charts, CSV export and limit warnings.

  • Available

    Teams and security

    Write-only ingest keys, roles, invitations, session management and an audit log.

  • Available

    Data controls

    Retention settings and workspace deletion with a grace period.

  • Available

    Traces and metrics

    Send OpenTelemetry traces and metrics, or Prometheus remote write, with the same key. Trace waterfalls linked to their logs, and a metrics explorer with rates and percentiles.

  • Available

    Dashboards

    Dashboards of log, metric and trace panels with a shared time range, service filter, auto-refresh and templates.

  • Available

    SQL

    Read-only SQL over your logs, spans and metrics, with a schema browser, parameters, charts and saved queries.

  • Available

    Export

    Download logs, traces, metrics or any SQL result as NDJSON or Parquet, streamed with no row limit.

  • Available

    Collector fleet management

    Manage your OpenTelemetry Collectors from Logthread over OpAMP: live inventory and health, versioned configs targeted by labels, rollout status and one-click rollback.

On the roadmap

What we plan to build next.

These are plans, not features you can use today. Scope and order may change.

  • Planned

    Replay

    Re-ingest a time range from the archive through a pipeline.

  • Planned

    More destinations

    Forward logs to other tools such as Splunk, Datadog, Elastic and S3.

FAQ

Questions

What do I need to install?

Nothing from Logthread. You send logs, traces and metrics with standard tools and a Logthread ingest key: OpenTelemetry SDKs and zero-code instrumentation (Node.js, Python, Java, Go, .NET), the OpenTelemetry Collector over OTLP HTTP or gRPC, Prometheus remote write, Fluent Bit, Vector, rsyslog, or plain JSON lines with curl. On Kubernetes, use the OpenTelemetry Collector Helm chart. Onboarding has copy-paste snippets for each.

How is data stored, and where?

Logthread is fully managed: there is nothing for you to run or operate. Your data is stored in India, in the Mumbai region. On the free plan, data is kept for 7 days during early access.

What happens if something fails?

Logs are acknowledged only after they are durably queued. If storage is unavailable, logs wait in the queue and are delivered when it recovers. Delivery is at-least-once.

What does it cost?

During early access there is a free plan: currently 1 GB/day of ingest, 7-day retention and up to 3 members. These limits may change. Paid plans and pricing will be published before general availability.

Can I invite my team?

Yes. Invite people by email and give each one a role: owner, admin, member or viewer. The free plan allows up to 3 members during early access.

Early access

See the whole story behind your logs.

Logthread is in early access, with a free plan you can sign up for yourself.