It’s the real Seq
Not a clone, not a compatible API. The genuine Seq server — so Serilog, NLog, OpenTelemetry and seqcli work with zero client changes.
Fully managed Seq hosting — your log server, run for you.
Fully managed Seq log servers in the cloud. Spin up a production-ready instance in minutes — we handle TLS, backups, upgrades and monitoring. It’s the real Seq, so every library, signal and dashboard works exactly as documented.
Not a clone, not a compatible API. The genuine Seq server — so Serilog, NLog, OpenTelemetry and seqcli work with zero client changes.
A buffering gateway sits in front of your instance. Restart, upgrade, resize — even a cluster incident — and your events queue, then replay. You can’t build this around a single self-hosted box.
An account-owned ingestion endpoint and API key that outlive the instance behind them. Upgrade, resize, restart — or rebuild onto a brand-new instance — and your loggers never notice, with no DNS or certificates for you to stand up and maintain.
Daily backups with restore, managed version upgrades, and 24/7 health monitoring. We watch the log server so you don’t have to.
Flat per-instance plans sized by compute and storage. No per-GB ingestion metering — log as much as your disk holds.
A dedicated, single-tenant instance with its own disk and in-region backups. No shared Seq, ever. EU residency is on the roadmap.
How it works
No infrastructure to stand up. Pick, provision, point — then read your logs.
Choose a US region and an instance size — Dev for side projects up to Business for busy production. Change your mind later with a resize.
A pipeline provisions real Seq with TLS and a dedicated ingestion endpoint. In minutes you have a live URL.
Aim Serilog, NLog, OTLP or seqcli at the ingestion endpoint. No client changes — it speaks native Seq.
// Serilog
var log = new LoggerConfiguration()
.WriteTo.Seq("https://acme-prod.in.us1.seqhost.net",
apiKey: "<your-key>")
.CreateLogger(); The ingestion gateway
Your logger points at one managed gateway instead of the instance directly. When the instance restarts — upgrade, resize, even a cluster-level incident — the gateway keeps accepting your logs, buffering them and replaying the moment it’s back. Buffered and drained, never dropped. This is the part you can’t rebuild around a single self-hosted box.
Baseline buffering covers every maintenance operation we run, and because the gateway runs split-homed it keeps accepting logs even through a cluster-level incident. Your events queue and replay — they don’t hit a connection-refused and vanish.
The endpoint belongs to your account, not the instance — so we can flip it onto a fresh instance after a restore, clone or full rebuild without your hostname or API key ever changing. Self-hosting, that stable indirection is yours to build and operate — DNS, certificate renewal, preserving the key across rebuilds; here it’s included.
Why hosted
Seq is the best structured log server for .NET and beyond. But Datalust ships it as software you run yourself — and running it well in production means owning all of this:
// early access
Be one of the first teams running Seq without the servers.
Customer logos land here after launch. No fake testimonials in the meantime.
Get early access
The portal isn’t open yet. Leave your email and we’ll let you know the moment you can spin up your first instance — plus the occasional launch update.
no card · no spam · unsubscribe anytime