Follows the trail
Traces from every service stitched into one timeline, so you see what happened in the order it happened. Revolutionary, we know.
The bug walked in at 2 a.m. It had production written all over it.
Slowburn tracks incidents down the slow, thorough way – through logs, traces and that config file everyone swears they never touched. When we close a case, it stays closed.
First case is on the house. The rest we can discuss over coffee.
Trusted by companies that would rather stay anonymous.
Names blacked out at their lawyers' request. The logos slipped through: legal ran out of marker.
How a case gets solved
The call
Tell us what happened. All of it, including the part where someone deployed on a Friday afternoon.
The legwork
We follow the trail through logs, traces and commit history. Every witness gets questioned, the intern's cron job included.
The report
A plain account of what broke, why it broke and what keeps it from breaking again. We check DNS first. It's always DNS – until it isn't.
What you get for your money
Knows everyone in town
Plugs into your repositories, chat, CI and monitoring. Has a contact in every department, and none of them ask questions.
Connects the dots
Groups incidents that share a cause. The detective calls it the fundamental interconnectedness of all bugs. We've stopped arguing.
Keeps his mouth shut
Your data stays in the region you choose, encrypted at rest and in transit. What happens in production stays in production.
Writes it all down
Every case ends with a report people actually read: short, clear and free of blame. Blame costs extra.
Works nights
Watches your systems around the clock. Sloths are famous for sleeping through most of the day. Not this one, not on shift.
Closed cases
Case 1187
The vanishing checkout
Orders disappeared every Tuesday at noon. Turned out to be a cron job with ambitions. Fixed before the next Tuesday, which is more than our last vendor managed in a year.
Priya N., head of platform, Hollow Pine Outfitters
Closed
Case 2040
The midnight leak
Our API put on a gigabyte of memory every night, like a rumour gaining weight. Slowburn found it in a cache we had all forgotten about. We named the fix after the detective.
Marco D., CTO, Tidewater Logistics
Closed
Case 404
The missing page
Half our readers hit a dead end after the redesign. The trail led to a redirect map written in a hurry and a hope. Solved by lunch – his lunch, which takes a while.
Jo W., product lead, Lantern Books
Closed
Rates
Honest rates for honest work. No retainers, no surprises, no small print. The large print is fine.
Small-time
For side projects and the occasional mystery.
$0Free, for as long as you like
- One project
- Three open cases at a time
- Seven days of history
- Email support, answered eventually
Regular
For teams that ship every day and sometimes regret it.
$29Per seat, per month
- Ten projects
- Unlimited open cases
- Ninety days of history
- Traces and every integration
- Support on weekdays, with a pulse
The whole city
For when you run the city, or at least its payments.
Let's talkPriced to the size of the trouble
- Unlimited everything
- Single sign-on and audit log
- Your own data region
- A detective on call, awake
Questions people ask the detective
Why a sloth?
Fast is how you got into this. We look carefully, change one thing at a time and leave the place tidier than we found it.
How slow is slow?
Most cases close within a day. Slow is about method, not about your pager going off for a week.
Do you need access to production?
Read-only, and only to what you allow. The detective doesn't pick locks. Usually.
Can we blame the intern?
You can. The report will still show who approved the pull request.
Is Slowburn real?
No. It's a demo template for Prastora, a CSS framework. The sloth abides, though.
Every bug has a story.
Let's hear yours.
Open a case
The office is open. The coffee is terrible.