Monoscope¶
Open-source observability platform (formerly APItoolkit) that stores all telemetry in the user's own S3 buckets. Combines OpenTelemetry-native ingestion with LLM-powered natural language querying and scheduled AI agents for anomaly detection.
Why Monoscope¶
- BYOS (Bring Your Own Storage) — all telemetry stored in your S3-compatible bucket; no vendor lock-in, you own the data forever
- No sampling or dropping — every request, log, span, and database query is captured and searchable
- Natural language querying — ask "Show me all 500 errors from the payments service yesterday" in plain English, get instant answers with charts
- AI agents on a schedule — configurable agents (hourly/daily/weekly) detect anomalies and deliver email reports
- Built on TimeFusion — purpose-built open-source time-series database (Rust + Apache DataFusion + Delta Lake) with PostgreSQL wire protocol
- 780+ integrations via OpenTelemetry ecosystem
When Monoscope Fits¶
| Scenario | Fit |
|---|---|
| Team wanting full-fidelity log/trace storage without sampling | Excellent — BYOS + no sampling is the core differentiator |
| Replacing expensive Datadog/Elastic bills | Strong — S3 storage is orders of magnitude cheaper |
| Natural language observability for on-call teams | Strong — LLM query engine is first-class |
| Small team wanting simple Docker Compose observability | Good — docker-compose up quickstart |
| Enterprise with strict data sovereignty requirements | Good — self-hosted with your own S3 bucket |
Use Cases¶
- Production debugging — full-fidelity traces, logs, and session replay
- API monitoring — automatic endpoint discovery, change detection, error fingerprinting
- On-call incident response — AI-powered anomaly detection with Slack/Discord/PagerDuty alerts
- Customer support — session replay synced with backend telemetry
- Cost optimization — replace Datadog/Elastic with S3-native storage
Licensing & Pricing¶
| Edition | License | Cost |
|---|---|---|
| Self-hosted Community | AGPL-3.0 | Free |
| Self-hosted Enterprise | Commercial | Starts at $500/month |
| Monoscope Cloud | Proprietary | $29/month (20M events, +$2/M overage) |
| Monoscope Cloud + BYOS | Proprietary | $199/month (100M events, unlimited retention) |
Ecosystem & Connections¶
- TimeFusion (
monoscope-tech/timefusion) — purpose-built TSDB (MIT license, Rust + DataFusion + Delta Lake) - TestKit (
monoscope-tech/testkit) — YAML-based API testing DSL (Rust) - SDKs: Go, Python (Flask, Django, FastAPI), Node.js (Express, Fastify, tRPC), Java (Spring Boot), PHP (Laravel, Symfony), .NET, Elixir (Phoenix), Next.js
- OpenTelemetry-native — uses OTLP/gRPC on port 4317 for all ingestion
- Alert channels: Slack, Discord, PagerDuty, email, webhooks
Compatibility & Requirements¶
- S3-compatible storage (AWS S3, MinIO, etc.) for telemetry data
- PostgreSQL + TimescaleDB for metadata (pg18)
- Kafka for ingestion buffering
- Docker Compose for quickstart; Kubernetes via OTel Operator
Latest Version¶
v0.5.0 (2026-04-12) — pre-1.0 but actively developed with ~2-3 week release cadence. 473 GitHub stars.
Alternatives¶
| Tool | Key Difference |
|---|---|
| SigNoz | ClickHouse backend, more mature, no BYOS |
| OpenObserve | Rust-native, Parquet + S3, no LLM features |
| Datadog | Commercial SaaS, expensive, vendor lock-in |
| Elastic | Mature ecosystem, Java-heavy, costly at scale |
| Grafana/LGTM | Broad ecosystem, no AI query engine |
Tech Stack¶
| Layer | Technology |
|---|---|
| Backend | Haskell (~80% of codebase) |
| Storage Engine | TimeFusion (Rust, Apache DataFusion, Delta Lake) |
| Metadata DB | PostgreSQL + TimescaleDB (pg18) |
| Frontend | HTMX + Tailwind CSS v4 + DaisyUI v5 |
| Ingestion | OpenTelemetry Protocol (OTLP/gRPC) |
| Caching | Foyer adaptive cache (512MB memory + 100GB disk) |
| Charts | ECharts |
Community Health¶
| Metric | Value |
|---|---|
| GitHub Stars | 473 |
| Forks | 12 |
| Open Issues | 24 |
| Contributors | 8 human |
| License | AGPL-3.0 |
| Primary Language | Haskell |
| Based In | Berlin, Germany |
Sources¶
Sources¶
Official Documentation¶
| Source | URL | Authority | Retrieved Via |
|---|---|---|---|
| Monoscope GitHub Repository | https://github.com/monoscope-tech/monoscope | Official | GitHub |
| Monoscope Website | https://monoscope.tech | Official | Web |
| Monoscope Releases | https://github.com/monoscope-tech/monoscope/releases | Official | GitHub |
| TimeFusion Repository | https://github.com/monoscope-tech/timefusion | Official | GitHub |
| TestKit Repository | https://github.com/monoscope-tech/testkit | Official | GitHub |
| Monoscope Pricing | https://monoscope.tech/pricing | Official | Web |
SDKs & Integrations¶
| Source | URL | Authority | Retrieved Via |
|---|---|---|---|
| Go SDK | https://github.com/monoscope-tech/monoscope-go | Official | GitHub |
| JavaScript SDK | https://github.com/monoscope-tech/monoscope-js | Official | GitHub |
| Python SDK | https://github.com/monoscope-tech/monoscope-python | Official | GitHub |
| Express SDK | https://github.com/monoscope-tech/apitoolkit-express | Official | GitHub |
| Flask SDK | https://github.com/monoscope-tech/apitoolkit-flask | Official | GitHub |
| Django SDK | https://github.com/monoscope-tech/apitoolkit-django | Official | GitHub |
| Spring Boot SDK | https://github.com/monoscope-tech/apitoolkit-springboot | Official | GitHub |
| Laravel SDK | https://github.com/monoscope-tech/monoscope-laravel | Official | GitHub |
| .NET SDK | https://github.com/monoscope-tech/apitoolkit-dotnet | Official | GitHub |
| Phoenix SDK | https://github.com/monoscope-tech/apitoolkit-phoenix | Official | GitHub |
Comparisons & References¶
| Source | URL | Authority | Retrieved Via |
|---|---|---|---|
| Monoscope vs Datadog | https://monoscope.tech | Official | Web |
| Monoscope vs Sentry | https://monoscope.tech | Official | Web |
| Monoscope vs Elastic | https://monoscope.tech | Official | Web |
| OpenTelemetry Registry | https://opentelemetry.io/ecosystem/registry/ | Standards Body | Web |
Community¶
| Source | URL | Authority | Retrieved Via |
|---|---|---|---|
| Discord Community | https://discord.gg/904634773329297429 | Official | Web |
| GitHub Issues | https://github.com/monoscope-tech/monoscope/issues | Official | GitHub |
Questions¶
Answered¶
How does Monoscope differ from OpenObserve?¶
Both use S3-native storage, but Monoscope adds LLM-powered natural language querying and scheduled AI agents for anomaly detection. Monoscope's backend is Haskell; OpenObserve's is Rust. Monoscope uses its own TimeFusion TSDB; OpenObserve uses its own Parquet-based engine.
What is TimeFusion?¶
A purpose-built open-source time-series database (MIT license) written in Rust. Uses Apache DataFusion as the query engine, Delta Lake for ACID transactions on S3, and exposes a PostgreSQL wire protocol so any Postgres client can query it. Benchmarked at 500K+ events/sec per instance.
Can I use my own S3 bucket with Monoscope Cloud?¶
Yes — the BYOS (Bring Your Own Storage) plan at $199/month lets you point Monoscope Cloud at your own S3 bucket for unlimited data retention at no extra cost.
How does Monoscope handle multi-tenancy?¶
Projects provide tenant isolation. Each project has its own API key, S3 partitioning, and access controls. Multi-tenant workspace support is on the roadmap.
Open¶
How does the Haskell backend handle production reliability?¶
Haskell is uncommon for production observability platforms. How does the team handle operational concerns like debugging, profiling, and incident response in a Haskell codebase?
What LLM provider powers the natural language query engine?¶
The documentation mentions LLM-powered queries but does not specify which provider or model. Is it OpenAI, Anthropic, or self-hosted? Can users configure the LLM backend?
How does TimeFusion handle schema evolution?¶
As OTel attributes change (new fields added, old fields deprecated), how does the Delta Lake schema adapt? Is there a migration mechanism or is it schema-on-read?
What is the production readiness level at v0.5.0?¶
Being pre-1.0, what are the known limitations? Is there a stability guarantee or backwards compatibility commitment for the v0.x releases?
How does the AI agent scheduler interact with the LLM at scale?¶
If many users schedule AI agents that all trigger simultaneously, how is LLM API rate limiting and cost managed?