LogNorth
PulseGate's liveness check found it on 3 Oct 2026; it is registered on GitHub and has been in the index since 3 Oct 2026. How this is checked
LogNorth is a self-hosted observability tool for collecting and querying application logs, detecting errors, configuring alerts, and monitoring uptime. It runs on infrastructure controlled by developers and can expose application data to coding agents through MCP.
Inferred · not functionally tested
Overview
6 featuresPurpose: Monitoring application logs, errors, alerts, and uptime without metered hosted logging costs.
Inferred · not functionally tested
Audience: developers and small engineering teams
Inferred · not functionally tested
Functions: monitoring
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: freemium · license: Proprietary · platforms: API, CLI, WEB · deployment: browser, cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: lognorth.com · rubygems.org · github.com. These links do not verify the individual claims.
LogNorth sits in PulseGate's Other observability category. Inferred · not functionally tested: It focuses on monitoring application logs, errors, alerts, and uptime without metered hosted logging costs. Inferred · not functionally tested: It is built as a B2B product for developers and small engineering teams. Basis unknown · not verified: There is a free tier, and paid plans start at $99. Basis unknown · not verified: It runs on the web and the command line, and it can be self-hosted.
LogNorth first shipped in 2026. The project is developed in the open on GitHub with 24 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are log collection, log querying, and error tracking. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Log collection
- Log querying
- Error tracking
- Alert rules
- Uptime monitoring
- MCP access
Topics: Inferred · not functionally tested
Built with & integrations
- Astro
- /_astro/ in the HTML
- Netlify
- x-nf-request-id header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed3 Oct · 10:42 UTClognorth seen via RubyGems newly publishedSource: RubyGems newly published · Open
Frequently asked questions about LogNorth
- What is LogNorth?
- Inferred · not functionally tested: LogNorth focuses on monitoring application logs, errors, alerts, and uptime without metered hosted logging costs. It is catalogued under Other observability on PulseGate.
- Who is LogNorth for?
- Inferred · not functionally tested: LogNorth is a B2B product built for developers and small engineering teams.
- How much does LogNorth cost?
- Basis unknown · not verified: Paid plans start at $99, and a free tier is available.
- What platforms does LogNorth run on?
- Basis unknown · not verified: LogNorth runs on the web and the command line. It can also be self-hosted.
- Is LogNorth still maintained?
- PulseGate's liveness check found it on 3 Oct 2026. Its GitHub repository shows 24 commits in the last 90 days.
- What are alternatives to LogNorth?
- Similar projects tracked by PulseGate include scietex.log-aggregator-service, Telemetry Machine, and Errorgap.scietex.log-aggregator-serviceTelemetry MachineErrorgap
- How long has LogNorth been around?
- LogNorth first shipped in 2026.
- Is LogNorth open source?
- Basis unknown · not verified: LogNorth has a public GitHub repository.
Also in Other observability
Same category — not a similarity match