Oleqlog

See every event.

Live tail, search, SQL, and alerts — without running a logging stack.

Get Started See the setup

app.ts

import { OleqLog }

const log = new OleqLog()

log.info("ready")

Official SDKs

JS, .NET, and Flutter. Ingest through the SDK only.

LiveSSE

INFOPOST /v1/checkout

OK201 · 42ms

WARNslow query 420ms

ERRORpayment timeout

Live Tail over SSE

Stream as events land. No ClickHouse polling.

⌕type:error env:prod

SELECT * FROM events

WHERE type = 'error'

error128 hits

Search and SQL

Filters plus org-scoped SQL against events.

error spikenow

Email · Telegram · webhook · SMS / WhatsApp soon

latency > 2s2m

Alerts that ship

Email, Telegram, webhook — SMS / WhatsApp on higher plans.

The short version

Logging shouldn't feel like a whole other job.

Most teams don't have time to babysit a logging stack. ELK, random dashboards, YAML jungles — all just to answer what went wrong?

If you're shipping fast — indie, side project, or a small SaaS team — you want errors, requests, and context in one place. Not another system to maintain.

Oleqlog is that place: ingest → durable queue → ClickHouse for history, Redis for live. Drop in @oleq-ai/logs, create an app, and streams show up in the dashboard.

Everything you need. Nothing you don't.

Built around ingest, live tail, history, SQL, and alerts — the same surfaces you'll use in the dashboard every day.

Ingest without a schema

Drop in the SDK from Node or Next.js. Levels from trace to metric, plus optional kind and body for req/res pairs.

Live Tail

Watch production as it happens over SSE. Dense monospace rows with level colors and REQ/RES badges.

History and SQL

Filter historical logs, or run org-scoped ClickHouse SQL against a virtual events table from the Queries page.

Alert rules & channels

Route critical events to email, Telegram, HTTPS webhooks, or (soon) SMS / WhatsApp. Channels are per org; rules stay separate.

Orgs, apps, and API keys

GitHub sign-in, one org superadmin, apps under the org, and scoped API keys. Invite teammates by email.

Full event detail

Click a row for the whole event as JSON — message, kind, body, environment, and the rest. No separate payload column.

Set up in four steps.

Install the SDK, set OLEQLOG_API_KEY, and send.

oleq — install

● session

➜~/api

bun · registryexit 0

Why developers switch to Oleqlog.

Same job — find what broke — without running your own logging cluster.

Without Oleqlog

Too many dashboards and agents to keep in sync.
Hard to set up and easy to break.
Slow searches when you need answers now.
YAML everywhere and confusing config files.
Pay for storage and infra you barely use.

With Oleqlog

Drop in a tiny SDK and stream in minutes.
Live Tail for the stream; Logs for history.
Filters and org-scoped SQL when you need depth.
Email, Telegram, webhook — SMS / WhatsApp coming.
Simple plans that grow with your volume.

Simple, predictable pricing.

Start for free. Upgrade when you grow. Self-serve billing is still rolling out — email [email protected] for Custom volume or retention.

Free

$0 /mo

Side projects and experiments.

10k logs/month
7-day retention
1 seat
No alerts
Live Tail + Logs
SDK access

Start Free

Popular

Starter

$9.99 /mo

Logging for small SaaS teams.

100k logs/month
30-day retention
3 seats
Up to 5 active alerts
email / telegram / webhook
Live Tail + Logs
SDK access

Get Started

Pro

$19.99 /mo

For teams that ship every week.

500k logs/month
3-month retention
10 seats
Up to 15 active alerts
email / telegram / webhook / SMS / WhatsApp
SMS / WhatsApp provider costs extra
Live Tail + Logs
SDK access

Choose Pro

Custom

Volume, retention, and dedicated support.

Custom log volume
Custom retention period
Custom seats, projects & alerts
All notification channels
Dedicated onboarding
Contract & renewal via OleqPay

Focus on your product.
We'll handle your logs.

Get Started View Docs