Allow Self-Hosted Administrators to Disable and Hide Unused Features

Feature Request: Feature Visibility and Disable Controls for Self-Hosted Instances

Summary

Allow self-hosted administrators to disable specific OneUptime modules/features and automatically hide them from the user interface.

Problem

Self-hosted deployments often do not use every available OneUptime feature. For example, an organization may only use monitoring and incident management while not using Kubernetes monitoring, Traces, Logs, or Status Pages.

Currently, unused features remain visible in the UI, which can:

• Create confusion for end users.
• Increase UI complexity.
• Expose functionality that is not configured or supported by the organization.
• Make onboarding and navigation more difficult.

Proposed Solution

Introduce a feature management section in the admin settings that allows self-hosted administrators to enable or disable specific modules.

Example:

• Monitoring ✅
• Incidents ✅
• Status Pages ✅
• Kubernetes ❌
• Traces ❌
• Logs ❌
• Metrics ✅

When a feature is disabled:

1. The related navigation menu items should be hidden from all users.
2. Related pages and routes should be inaccessible.
3. API endpoints for disabled features may optionally be disabled as well.
4. The UI should behave as if the feature is not installed.

Benefits

• Cleaner user experience.
• Reduced UI clutter.
• Better customization for self-hosted deployments.
• Easier adoption for organizations that only require a subset of OneUptime functionality.
• Improved security and governance by limiting access to unused modules.

Additional Considerations

• Support feature flags through environment variables and/or admin settings.
• Allow changes without requiring a full redeployment.
• Provide sensible defaults where all features remain enabled for backward compatibility.