Scalable per customer statuspage

[Hannes Stefánsson]

I’m looking to set up individual status pages for each of my customers to accommodate their unique tech stacks. Each page should be accessible only by users from the respective customer organization, ensuring privacy and exclusivity. At the same time, I want all the status pages to maintain a consistent look and feel to align with our branding and provide a cohesive experience.

I’m curious if there’s a streamlined way to achieve this, possibly by using templates that can be applied across all status pages. This would save time and effort while ensuring uniformity. Would status pages support this kind of setup efficiently?

[Sadie Hayes]

Scalability for per-customer status pages is an interesting challenge. It’d be great if there were built-in solutions for this. Have you explored automation options or integrations? Documenting scalability strategies can be complex, but DoMyPaper provides professional writing services that help structure such discussions effectively. If you ever need a detailed report on implementation strategies, https://domypaper.com/ could be a useful resource. Curious to see what solutions others suggest!

[Robert]

Hi @Hannes Stefánsson ! 

Have you explored Audience-specific page as an option? This would essentially boil down to a single page that changes which components are shown based on the groups assigned to the user that logs in:

Status communication gets complicated when you have different customers using a variety of different services and hosted on different infrastructure. With Audience-specific pages comes the power to target updates only to those customers impacted by an incident. All without needing multiple status pages.

[Hannes Stefánsson]

Yes that's absolutely perfect, I didn't quite understand the difference between Private and Audience specific but this seems to hit exactly my use case.

Could I then have specific metrics associated with specific groups so for example I would send API uptime for all my customers and then set audiences for which one can see what?

[Robert]

Yep! System metrics are customizable for Audience-specific pages in a similar way that Components are.

If you're using an audience-specific page, you can choose what visibility users and groups have into metrics. This is similar to how you choose the visibility of components for different users and groups.