Opportunities › Observability platform for development teams › Proposed app
Fernlog
OpenTelemetry logs, metrics and traces with phone-ready incident triage
- Score
- 67
- confidence 80
- Evidence
- 39
- items on the page
- Rivals
- 17
- named in sources
- First version
- 70 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2010
- Mature market · AI estimate
ScreensConcept
Desktop and mobile: Engineering teams review complex traces and dashboards on desktop, but on-call engineers need to triage incidents and access context from their phone when away. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Incident 214
Open, unassignedp95 3.8s
About this appAI proposal
Fernlog takes logs, metrics and traces over OpenTelemetry and puts them in one place, so a small team can see what broke without running three separate tools. Point your existing OTLP exporter at it and data shows up in minutes.
It is built for the moment someone is paged. The phone-ready app groups related errors into one incident, links each to its trace and log lines, and offers a plain-language summary of the likely cause that you can check against the raw data.
Run it in our cloud, or self-host it if data must stay with you. Because it speaks OpenTelemetry only, you can switch away without re-instrumenting your code. Pricing is flat per team, not per host or per gigabyte of ingest.
- Tagline
- One OpenTelemetry inbox for logs, metrics and traces. Fixed from your phone.
- Voice
- CalmDirectPractical
- Why this name
- A fern grows in shade and unfurls in a clear pattern, like a trace tree. Fernlog is short, easy to say, and reads as logs without sounding like a monitoring tool.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
OpenTelemetry in, nothing else
Accepts OTLP logs, metrics and traces over HTTP and gRPC. No proprietary agent, so you can leave without re-instrumenting.
No member yet
Incident view from any signal
An alert opens one page: the failing trace, nearby logs and the metric that moved, lined up on a shared timeline.
No member yet
Checkable AI summaries
Each incident gets a short suggested cause. Every claim links to the log line or span it came from.
No member yet
On-call in your pocket
Installable app with push alerts. Acknowledge, mute, assign or share an incident in two taps.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#14463ADeep Fern · primary#F5F2EAPaper · surface#1B2622Ink · text#E8A317Signal Amber · accent#B8432FAlarm Clay · error data#6FA89AMist Teal · secondary data
Typography
Aa
Fernlog
PricingAI proposal
Based on pricing pages in the material: Grafana from $19 a month, Sentry $26 to $80, Splunk $6 to $100, all with free plans. ClickHouse lists prices on request. These tiers are a starting point to test.
Free
Free
- 1 project
- 3 users
- 3-day retention
- Push alerts
Team
$29 a month
- 10 users
- 14-day retention
- AI incident summaries
- Spend cap
- Shared incident links
Scale
$79 a month
- 30 users
- 30-day retention
- Longer history add-on
- Self-hosted license
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$190,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Engineers share incident links and read-only timelines with teammates, support and customers in chat and postmortems. The shared page shows the trace, logs and timeline with a Fernlog footer.
- Do they become customers?
- Viewers are often engineers on other teams who could set up their own project, but support staff and customers may only look. Test whether shared-link viewers start a free project.
- First customers
- Teams of 3 to 15 engineers at seed to Series A software startups that already use OpenTelemetry and have no dedicated SRE.
- Where to reach them
- OpenTelemetry community: Answer migration questions in community forums and publish collector config recipes that send data to Fernlog.
- Open-source observability users: Offer a Prometheus and Jaeger migration guide to users of self-hosted stacks who are tired of maintaining them.
- Dev newsletters and posts: Write cost breakdowns comparing flat team pricing against per-host billing.
- First milestone
- Ten teams send production data for 30 days, and five pay for a Team plan.
Why people already pay for this
- VerifiedGitHub repository gained 32311 stars in 2104 days
- Public claimSigNoz provides unified observability combining logs, metrics, and traces in a single platform with APM, distributed tracing, log management, and infrastructure monitoring features.
- Public claimThe platform is OpenTelemetry-native, indicating built-in support for industry-standard instrumentation.
- Public claimSigNoz offers both self-hosted and cloud deployment options with AI-assisted capabilities.
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Telemetry storageColumnar database for logs, metrics and tracesTelemetry is high-volume and high-cardinality. Postgres is kept for accounts, alerts and incidents only.
- This app · IngestOpenTelemetry Collector with OTLP endpointAccepts standard exporters and applies redaction and sampling before data is stored.
RisksAI inference
- TechnicalTelemetry volume is heavy. Postgres cannot hold it, so a separate columnar store is needed, and cost per customer must stay under the flat price.
- CommercialCrowded market of free open-source and large vendors. Buyers may stay on self-hosted tools if the mobile incident view is not a clear reason to switch.
- AIIncorrect cause summaries could send on-call engineers the wrong way. Every claim must cite raw data, and the summary must be clearly labelled as a suggestion.
- DataLogs often contain personal data or secrets. Customers need redaction rules, region choice and clear retention settings before they will send production data.
- PlatformPush notifications on iOS PWAs depend on installation and Apple's rules, so critical pages may need SMS or chat fallbacks.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.