Insights & updates from our experts
Quickbase
Download the Case Study
- Challenge 1: A homegrown status tool that needed constant maintenance and code
- Challenge 2: Ownership eroded as employees changed roles over the years
- Challenge 3: A fragile setup dependent on whoever last touched the code
- Challenge 4: No durable, multi-year system of record for availability
- Solution 1: A status page with zero code for the team to maintain
- Solution 2: Fast, customizable dashboard widgets and views, no engineering required
- Solution 3: A durable multi-year record of availability, retrievable on demand
- Solution 4: Responsive vendor support that moved faster than alternatives
How Quickbase retired its homegrown status page for one it doesn't have to maintain
A low-code leader moved uptime reporting for 6,000+ clients onto Xurrent IMR, and stopped maintaining code to do it.
Quickbase spends its days helping companies stop building things by hand. Its low-code platform lets 6,000 clients, many of them Fortune 100, assemble the applications they need without standing up a development team. So there is a quiet irony in how Quickbase used to run its own status page: it had built the thing itself, in code, and was maintaining it by hand for years.
That worked, until it didn't. When it came time to fix it, Quickbase moved its uptime reporting to Xurrent IMR.
Results with Xurrent IMR
Outcome: a self-service status page the SRE team runs without managing code, with a multi-year system of record.
‍
‍
The challenge: a homegrown tool that aged into a liability
Quickbase's custom uptime tool carried an ongoing tax: it needed maintenance and code management to keep working. That was manageable at first, then stopped being so as people changed roles and the knowledge to maintain it grew thin. A status page that depends on whoever last touched the code is a fragile way to keep a promise to 6,000 clients.
The solution: responsive, customizable, and not Quickbase's to maintain
Two things separated Xurrent IMR from the shortlist. The first was responsiveness: the team behind it was notably faster and more agile to work with. The second was ease: simple to implement, with widgets and views straightforward to customize, so Quickbase could shape the page without writing and maintaining code. It also wanted a durable system of record, retrievable rather than reconstructed.
The result: proof of reliability, without the upkeep
Because Xurrent IMR stores and retrieves historical data, Quickbase's site reliability team now runs a status page that communicates uptime and stands as ongoing proof of its commitment to service. Just as important is what the team no longer does: the reporting that once meant maintaining a homegrown tool now runs on a platform Quickbase does not have to keep alive itself. For a company whose value proposition is helping others stop building tools by hand, that is a fitting place to land.
At a glance
Get started with Xurrent today.
See how Xurrent IMR gives you a status page and a system of record without the code to maintain.
‍












.webp)
.webp)













