Authenticated Access Control
Private Status Pages
Not every status page should be public. Private status pages give internal teams and enterprise customers visibility without exposing operational details to the world.
When You Need Private Status Pages
Not all status information should be public. Internal services, enterprise customers, and sensitive infrastructure need visibility without public exposure.
Internal Services
Internal APIs, databases, and infrastructure.
Enterprise Customers
Dedicated status for your biggest accounts.
Security-Sensitive
Services you don't want to advertise publicly.
Detailed Views
More granular info than public pages show.
Security Considerations
Private status pages need proper access control:
- ✗Shared passwords via email. Password gets forwarded everywhere.
- ✗No access logging. You don't know who viewed it or when.
- ✗Static credentials. Password never rotated even when employees leave.
- ✗Exposing too much. Internal names reveal architecture to attackers.
upti.my Private Status Pages
Enterprise-ready access controls with multiple authentication options:
SSO Integration
SAML and OIDC for enterprise identity providers.
IP Allowlists
Restrict access to office or VPN IPs.
Access Logs
Audit trail of who viewed the page.
Magic Links
Email-based authentication without passwords.
Getting Started
Set up a private status page for your team or enterprise customers:
- 1
Create Status Page
Click "New Status Page" in your dashboard. Choose "Private" visibility to require authentication.
- 2
Configure Authentication
Pick your auth method: SSO with Okta, Azure AD, or Google. Or use password protection for simpler setups.
- 3
Add Internal Components
List your internal services, databases, and infrastructure. Be as detailed as you want since only authorized users will see this.
- 4
Set Access Controls
Optionally add IP allowlists to restrict access to your office or VPN. Share the link with your team.
Frequently Asked Questions
Use private status pages for internal teams, enterprise customers who need detailed visibility, or when you monitor services that shouldn't be publicly known. They require authentication to view.
upti.my supports password protection, SSO (SAML, OIDC), email-based magic links, and IP allowlists. You can combine methods for layered security.
Yes. Create multiple private status pages, each showing only the components relevant to that customer or team. Each has its own access controls.
Absolutely. Private pages often show internal service names, more granular components, and detailed incident information that wouldn't be appropriate for public pages.
Users visit the status page URL and authenticate via your configured method. With SSO, they're redirected to your identity provider. With password, they enter the shared password.
Related Topics
Run reliability as one connected workflow
Detect failures early, route alerts clearly, coordinate incidents, and keep status updates in sync from one system.