Roadmap

What's next for Tailwise.

An honest look at what's already working, what's shipping next, and what's on the table. If something here matters to you, tell me and it'll move up the list.

Now

What's live today

  • One-command install on any server with cron + log read access.
  • Per-minute agent that ships only new log bytes to Tailwise.
  • Server-side classification: fatals, errors, warnings (noise filtered).
  • HTML email alerts from our own infrastructure, throttled by a per-issue cooldown.
  • Multiple sites per subscription, in-place agent upgrades by re-running install.
Shipping next

What I'm working on

Next

Automatic secret & PII redaction

Before log lines leave your server, scrub obvious secrets (API keys, JWT tokens, passwords) and PII (email addresses, IPs). The aim: even if your logs leak something sensitive, Tailwise never sees it.

Next

Resource spike alerts

CPU, memory, disk, and load average sampled by the agent. Alerts when something runs hot before a fatal lands. Same email pipeline, same cooldown.

Next

404 burst alerts (access logs)

Opt-in support for nginx/Apache access logs, with burst detection (a flood of 404s from one IP or to similar paths usually means a broken link or a scanning bot). Grouped and throttled like the rest of the alerts so you don't get spammed.

Exploring

Ideas on the table

Later

Codebase sync for better advice

Optionally link Tailwise to your repository so an alert can show the exact file, line, and recent change that likely caused the issue. Your code stays in EU storage and is only read when matching an alert.

Later

AI analysis on EU infrastructure

Beyond regex: purpose-built models that understand both your logs and (with codebase sync) your code. Running on EU infrastructure, so your data never leaves the EU.

Idea

Hire a developer through Tailwise

When Tailwise spots something broken and you don't have time to fix it, book a vetted developer through Tailwise to take care of it. From "something's broken" to "it's fixed" without leaving the email thread.

Have a request?

I'd rather build what you actually need than what I assume you need. Drop me a line and tell me what should be on this page.

Email Marinus