About

About LogShare

LogShare is a small, focused tool for getting a log, a code snippet or a config file in front of a teammate without pasting four hundred lines into chat.

What it does

You paste content, choose how long the link should live, and share the URL. Whoever opens it gets line numbers, syntax highlighting, search and word wrap instead of a wall of text. When the link expires, the content is deleted.

Four modes cover the usual cases: Log Share for logs and stack traces, Code Share for a live collaborative editor, Private Room for a live room that opens only with a PIN, and Text Share for anything else.

Alongside sharing there are 22 developer tools, from a JSON formatter to a Kubernetes manifest validator, each with a step-by-step tutorial. Every tool runs entirely in your browser; nothing you paste into a tool is sent to a server.

Who it is for

Developers, SREs and support engineers, especially during incidents and code reviews: the moments when someone needs to see exactly what you are seeing, right now, and nobody wants to sign up for anything.

Principles

  • No accounts. There is no signup, login or email capture. A share is a link and nothing more.
  • Nothing lives forever. Every share has an expiry between 30 minutes and 7 days, and idle code rooms are removed after 7 days.
  • Tools never upload. Formatters, validators and converters run client-side. Tokens, manifests and .env files stay on your machine.
  • Minimal footprint. No tracking cookies, no analytics scripts and no advertising at the time of writing. Fonts are served from this site, not from a third party.

How it is built

LogShare is a single Node.js service with a SQLite database and local disk storage, fronted by Caddy for HTTPS. It is deliberately simple so that it is cheap to run and easy to reason about. Limits are generous for real work: pasted content up to 5 MB, and up to 20 files of 50 MB each per code room.

Contact

A public contact address is published on this page once the service launches.

Security issues can be reported through the address in /.well-known/security.txt when one is published there.