Monitoring, status pages and incidents in one place. The first to know your systems slipped should be you, not your customers.
One message when we open the doors. Nothing else.
No agent to install, no week of setup. Point it at what matters and VoyagerLog takes it from there.
Drop in a URL, a host, an endpoint or a cron heartbeat. Set how often and from where. That's the setup done.
Every fifteen seconds, day and night. The moment a check fails or slows, an incident can open on its own and the right people hear about it.
Your status page updates itself, subscribers get told, and every figure is sealed so the history stands up later.
Most teams bolt a monitor onto a status page onto an incident tool, then hope the seams hold during an outage. VoyagerLog is the lot, built as one.
One workspace. One bill. No seams for an outage to slip through.
Click through the pieces. Same data underneath, four jobs done without leaving the workspace.
Watch a page, an API, a port, an SSL certificate or a cron job that's meant to run. Not just up or down, but whether it answered the way it should, fast enough, with the right content.
Fast to load and easy to read, on your own domain and in your own colours. Group components, hide the ones you'd rather not show, and let people subscribe so they hear from you first.
Open an incident, mark what's affected and how bad it is, write once. The status page, the timeline and every subscriber move together. When it's over, the write-up is already half done.
Uptime per component over any window, measured against the targets you've set, ready to export. Not a figure typed into a slide, a figure pulled from the sealed record.
Alerts to your team the second a check fails, and updates to your customers the moment you post. You pick the channel for each.
Most status tools keep uptime in a database anyone with access can quietly edit. Ours can't be, not even by us.
A status page that looks like it belongs to you, with ninety days of history in plain sight. The page that answers the ticket before it's raised.
No tier where the basics are held back. The pieces that make a status tool actually useful, all in.
Nothing against the tools you might be stitching together. They just weren't built to work as one.
We needed this for ourselves first. Axenara runs hosting and sites for our own clients, and we wanted one honest place to watch all of it and prove it stayed up. Nothing on the market did the proving, so we built VoyagerLog. Before it goes to anyone else, it watches our own services and earns its keep. If it isn't good enough to run our business on, we won't put it near yours.
VoyagerLog is in active development and already running on our own infrastructure. We're putting it to work watching Axenara's own services first, and it only opens to customers once it's proven there. Leave your email and we'll tell you the day that happens. We won't put a date on it that we can't keep.
Axenara, a web and IT studio in London. VoyagerLog is one of a small family of products we build and run, alongside the hosting and sites we look after for clients.
Yes. Status pages live on your own URL, in your own brand. The page your customers see is yours, not ours wearing a badge.
Each check is sealed into an append-only ledger, chained one entry to the next. Alter any past figure and the chain no longer verifies, so the history can't be quietly rewritten, by anyone. Your SLA numbers come from that sealed record.
It isn't fixed yet, so we won't pretend otherwise. The aim is plain and predictable, without the per-subscriber surprises this category is known for. Join the list and you'll be among the first to see it.
That's the plan. When you join the list, tell us what you're on now and we'll factor it in as we build the way in.
VoyagerLog is on the way. Leave your email and we'll let you know the day it opens up. That's the only reason we'll write.
Built and run by Axenara in London.