Your logs,
anywhere.
Forward your build, runtime and app logs to any HTTP sink or Datadog. A durable buffer with a per-drain cursor means a sink that’s briefly down loses nothing. The flat-rate alternative to Vercel Log Drains.
Your logs should live where the rest of your observability does
You already have a place for logs — Datadog, Better Stack, Axiom, an S3 bucket behind an HTTP endpoint. koigrid Log Drains stream your platform logs there: create a drain (HTTP or Datadog), pick which sources to include, and every new log line is delivered in batches. Each drain keeps a cursor over a durable buffer, so if your sink is down for a minute the drain just resumes where it left off — nothing is dropped. Destinations are validated against SSRF, and any app or agent can also POST its own structured logs to the ingest API.
How koigrid compares
| koigrid | Vercel Log Drains | |
|---|---|---|
| Pricing | Flat rate (included) | Per drain |
| HTTP sink | Yes | Yes |
| Datadog format | Native | Via HTTP |
| Durable buffer + cursor | Yes (no loss on outage) | Best-effort |
| Push your own app logs | Yes (ingest API) | No |
| Anti-SSRF on destination | Yes | n/a |
| Manage by AI agent | Native | API |
From public docs, 2026. Drains deliver in batches from a durable buffer; a sink outage resumes without loss.
Reliable log shipping
Any HTTP sink
Logtail, Axiom, Better Stack, your own endpoint — or Datadog with its native format.
Nothing lost
A per-drain cursor over a durable buffer resumes exactly where it left off after an outage.
Filter by source
Include build, runtime, app or system logs per drain.
Push your own logs
An app or agent can POST structured records to the ingest API — they flow to every drain.
Anti-SSRF
Destinations are checked — a drain can never target an internal/private host.
Agent-native
Create and manage drains from Claude Code or any LLM via API + CLI.