Official SDKs for six platforms, a native OpenTelemetry receiver, and a plain HTTP API mean almost anything can log to ZipLogger today, and the list keeps growing.
First-class support via the ZipLogger.Client core package: batching, retries,
backpressure, and automatic release/commit enrichment.
Two lines in Program.cs. Request logs, scopes, and unhandled exceptions flow
automatically through the standard logging pipeline.
.WriteTo.ZipLogger(endpoint, apiKey): structured properties, destructured
objects, and exceptions preserved as searchable fields.
builder.Logging.AddZipLogger(...): an ILoggerProvider with scopes,
config-file binding, and per-category level filtering.
A dependency-free logging handler: pip install ziplogger, add
ZipLoggerHandler, and extra= values become searchable fields;
tracebacks feed regression detection.
npm install ziplogger: a zero-dependency core client plus first-class
Pino and Winston transports with the same batching and retry semantics as
the .NET packages.
go get a standard-library-only client with a first-class log/slog
handler: attributes become searchable fields, err attrs feed regression
detection.
A JDK-only client (Java 17+) with a java.util.logging handler. Zero dependencies,
same batching and retry semantics as every other SDK.
@ziplogger/browser captures uncaught errors and unhandled rejections, flushes
on page unload, and ships a React error boundary with component stacks.
Native OTLP/HTTP receiver for logs and traces (protobuf + JSON, gzip). Point
OTEL_EXPORTER_OTLP_ENDPOINT at ZipLogger; spans become request waterfalls on the
Traces page, and resource attributes, trace IDs, and exceptions map to first-class fields.
One-click GitHub App connect (or a fine-grained token) powers regression detection: blame the stack trace's files through the GitHub API, no cloning, revocable anytime.
gitlab.com or self-managed. Add a project access token with read_repository and
regression blame works exactly as it does on GitHub.
ZipLogger is a Model Context Protocol server, so your AI assistant can search logs, cluster errors, walk traces, and read regressions itself. One command to connect.
SMS and voice-call alerts work out of the box with a monthly allowance, or bring your own Twilio account for unlimited sending at your own rates.
Use the otlphttp exporter to fan logs from any language or agent into ZipLogger,
the door to Python, Node.js, Java, and Go today.
One authenticated endpoint accepts a single event, a JSON array, or NDJSON streams. If it can POST JSON, it can log to ZipLogger: cron jobs, shell scripts, legacy apps.
Alert notifications deliver to Slack incoming webhooks or any HTTP endpoint. Wire firing alerts into PagerDuty, Teams, or your own automation.
We operate the platform, you connect apps. AWS, Azure, GCP, a VPS, or the machine in your rack: if it can make outbound HTTPS calls, it can log to ZipLogger.
Logs and metrics are isolated per workspace, encrypted in transit and at rest, never sold and never used to train models. Export any time, deleted on request.
The same hosted platform serves a side project and a production fleet logging millions of events a day. Search stays fast, and there is no capacity planning to do.
Tail files and containers from apps you can't modify; the http output ships
NDJSON straight to ZipLogger. Copy-paste pipeline →
High-performance pipelines with remapping: rename keys, set severities, and stream to the ingestion endpoint. Copy-paste pipeline →
Filebeat, syslog relays, custom scripts: if it can POST newline-delimited JSON with a header, it can feed ZipLogger.
Native Logger/Monolog integrations. Today: the OTel Collector or HTTP API route works for both.
Query ZipLogger from dashboards you already have. Today: the REST API covers custom panels.
Native alert routing. Today: both accept ZipLogger's webhook notifications via their APIs.
Tell us what your stack looks like. Integrations are prioritized by real demand.