01 — Platform
PlatformUsage-based pricing
A new billing approach designed around actual platform consumption, with clear visibility into usage and retention.
Introducing OneMinute Logs v2
Applications generate millions of signals. But collecting those signals is only the beginning. OneMinute Logs v2 moves beyond searching through logs, toward understanding application behavior.
01 / Evolution
OneMinute Logs v1 focused on collecting and monitoring application logs. V2 goes beyond traditional logging, bringing intelligent observability, automated problem detection, and developer-first tooling together to help engineers investigate and resolve issues faster.
| Dimension | OneMinute Logs v1 | OneMinute Logs v2 |
|---|---|---|
| Core focus | Centralized application logging. | Understand application health, performance, and user experience from one observability platform. |
| Pricing | Event-based pricing — billed by the number of log events. | Storage-based pricing — billed by the volume of log data ingested, rather than the number of events. |
| Logs | Collection, search, live streaming, alerts | Connect logs with application performance and user activity to investigate what happened and understand the surrounding context. |
| RUM | Understand how real users experience your application through browser sessions, navigation, errors, and performance metrics. | |
| APM | Identify slow API requests, monitor application performance, and investigate bottlenecks across backend services. | |
| Anomalies | Developer-defined threshold alerts | Identify unusual error spikes, changes in request behavior, and unexpected application patterns without manually defining every threshold. |
| Incidents | Track incidents from detection to resolution, keeping related signals and investigation context together. | |
| Instrumentation | Manual SDK integration | Let OneMinute Pilot analyze selected API routes and propose useful monitoring code, with developer-reviewed changes. |
| Developer tools | SDKs and dashboard | Integrate observability into your terminal, IDE, and supported AI coding tools through OML CLI, Pilot, and MCP. |
02 / The new model
The value is no longer only in how much telemetry can be stored. It is in how efficiently an engineer can understand a problem and move toward a solution.
Telemetry sources
Logs
Events
APM
Performance
RUM
Experience
OML / Unified observability
Connected application context
Signals • Services • Sessions • Events
Intelligence and response
Discover unexpected behavior.
Investigate and respond.
Developer workflow
Pilot · CLI · MCP
Bring observability into the engineering environment.
Conceptual product workflow — not a physical infrastructure topology.
03 / Key capabilities
01 — Platform
PlatformA new billing approach designed around actual platform consumption, with clear visibility into usage and retention.
02 — Observability
ObservabilityObserve real user sessions, navigation, browser-side errors, and the experience users encounter in production.
03 — Observability
ObservabilityInvestigate application performance and service-level behavior beyond isolated log events.
04 — Intelligence
IntelligenceMove beyond hand-configured thresholds by identifying unusual patterns and important changes in application signals.
05 — Intelligence
IntelligenceTurn important detections into trackable incidents with context, investigation history, and resolution workflows.
06 — Developer tools
Developer toolsAI-assisted, route-level instrumentation. Pilot inspects a developer-selected route, proposes useful monitoring, and presents code changes for review.
6 of 6 capabilities shown.
04 / Philosophy
Monitoring should support the way developers work — not require them to abandon their workflow to make sense of their applications. OneMinute Logs v2 is designed around that principle.