is there a free plan?

No, but Starter is $9/mo — less than a coffee habit. Cancel anytime.

One npm install (or pub.dev add). One line of init code. You're live.

how is this different from sentry?

Sentry is for error reporting. logmonitor is for live debugging. We stream your raw console logs in real-time, not aggregated crash reports.

will it slow down my app?

No. Our SDK is tiny, asynchronous, and batches logs intelligently. Zero impact on your app's performance.

what frameworks do you support?

Flutter and React with native SDKs. Plus a REST API for everything else.

Kamal — a developer who ships apps and got tired of expensive, bloated monitoring tools. Say hi on Twitter.

Multi-Service Log Aggregation

Bring logs from every service, environment, and runtime into one unified, searchable feed.

>_ the problem

Your product has grown beyond a single codebase. You have a React frontend, a Node.js API, a Python worker, a cron job running on a VPS, and maybe a Flutter mobile app. Each one generates logs in a different format, stored in a different place, with a different retention policy. When an issue spans multiple services, you end up with five terminal tabs open, each tailing a different log source, trying to mentally piece together the timeline. Which service logged the error first? Did the API return an error before or after the worker crashed? Was the mobile app sending bad data, or was the backend rejecting valid requests? You need a single pane of glass where every service's logs land in one feed, with consistent structure and instant search across all of them.

>_ why traditional tools fall short

$Most logging platforms charge per source or per GB, making it expensive to aggregate logs from many small services that individually generate low volume.
$Setting up log forwarding from different runtimes and environments requires different agents, plugins, and configurations for each one.
$Proprietary log formats across services make correlation difficult without custom parsing rules and normalization pipelines.
$Cloud provider logging is siloed by service: CloudWatch for Lambda, Stackdriver for GCP, App Service logs for Azure, with no unified view.

>_ how logmonitor solves this

Unlimited Apps on Scale

The Scale plan supports unlimited apps for $99/mo. Register every service, environment, and runtime as its own app without worrying about per-source charges.

Unified Dashboard

All logs from all services appear in one clean feed. Filter by app, severity, or metadata to focus on a specific service, or view everything together to trace cross-service issues.

HTTP API for Any Runtime

Services in any language can send logs via HTTP POST. Your Python worker, Go CLI tool, and Bash cron job all send logs to the same dashboard as your Node.js API.

Structured Metadata

Attach consistent metadata (request IDs, user IDs, service names) across all services. Search for a single request ID and see its journey through every service it touched.

>_ quick setup

app.js · javascript

import { logmonitor } from 'logmonitor-js';

logmonitor.init({ apiKey: 'your-api-key' });

// The SDK auto-patches console.log/info/warn/error/debug

// Logs are only sent in production (process.env.NODE_ENV === 'production')

console.log('App started', { version: '1.0.0' });

>_ pricing for this use case

For teams aggregating logs from many services, the Scale plan at $99/mo with unlimited apps and 5 million logs per month is the best value. Smaller setups with up to 25 services fit on the Pro plan at $19/mo.

View all plans →

>_ frequently asked questions

$ Can I aggregate logs from services in different languages?

Yes. Use the native JavaScript or Flutter SDK for those environments, and the HTTP API for everything else. Python, Go, Ruby, Java, or any language that can make HTTP requests can send logs to LogMonitor.

$ How do I trace a request across multiple services?

Include a shared request ID or correlation ID in the metadata of every log call. Then search for that ID in the LogMonitor dashboard to see all related log entries from all services in chronological order.

$ Is there a limit on the number of apps I can register?

The Starter plan supports 2 apps, Pro supports 25, and Scale supports unlimited. Each service or environment you want to log separately counts as one app.

$ Can I separate logs by environment (staging vs. production)?

Yes. Register staging and production as separate apps. This keeps their logs cleanly separated in the dashboard while still being accessible from one account. You can easily switch between them.

$ What if one service generates far more logs than the others?

All apps share the plan's monthly log quota (50K, 1M, or 5M). If one noisy service dominates, you can adjust its log level to only send errors and warnings while keeping verbose logging for less chatty services.

$ Do logs from different services have consistent timestamps?

Yes. LogMonitor timestamps each log entry on ingestion, providing a consistent, comparable timeline across all services regardless of server clock differences.

Multi-Service Log Aggregation

>_ the problem

>_ why traditional tools fall short

>_ how logmonitor solves this

Unlimited Apps on Scale

Unified Dashboard

HTTP API for Any Runtime

Structured Metadata

>_ quick setup

>_ pricing for this use case

>_ frequently asked questions

>_ related pages

Microservices Observability

DevOps Log Management

API Monitoring and Logging

>_ about logmonitor