Console

The Console is Mezusphere’s web-based management interface. It provides a central place to configure, monitor, and control all aspects of your Mezusphere deployment, with no CLI required and no YAML files to manage.

Overview

The Console is organized around your organization’s projects. From the Console, you can:

• Create and manage projects
• Configure environments and routes
• Create service accounts for Warpgate registration
• Enable authentication and manage users (coming soon)
• Monitor traffic, authentication outcomes, and system status (coming soon)
• Track billing and set spending limits (coming soon)

Key workflows

Create a project

1. Navigate to your organization’s dashboard
2. Click New Project
3. Enter a project name and description
4. Your project is created with a default development environment

Each project represents a single service or application that you want to expose through Mezusphere.

Configure environments

Projects contain one or more environments (production, staging, development). Each environment has:

• A unique endpoint URL (e.g., your-project.mezusphere.app)
• Independent route configuration
• Independent authentication settings
• Its own set of connected Warpgates

To add an environment:

1. Open your project
2. Go to Environments
3. Click New Environment and choose a name

Set up routes

Routes define how incoming requests are directed to your workload.

1. Open your project and select an environment
2. Go to Routes
3. Click New Route
4. Configure the path pattern (prefix, exact, or regexp)
5. Optionally enable authentication and set permission requirements
6. Configure CORS if needed

Enable authentication

This feature is under active development and will be available before launch.

Mezusphere provides built-in authentication, with no external provider required.

1. Open a route’s settings
2. Toggle Require Authentication on
3. Choose the user directory to authenticate against
4. Optionally configure required permissions

Once enabled, every request to that route must include a valid authentication token. Unauthenticated requests receive a 401 response or are redirected to the login page.

Manage users

This feature is under active development and will be available before launch.

When authentication is enabled, you can manage end users through user directories.

1. Go to your project’s User Directories
2. Create a directory or select an existing one
3. View, create, and manage user accounts
4. Set user status (active, inactive, suspended)

Create service accounts

Service accounts provide the API keys that Warpgates use to authenticate.

1. Go to your project’s Service Accounts
2. Click New Service Account
3. Copy the generated API key; this is your Warpgate token
4. Use this token when deploying your Warpgate

Service accounts are scoped to a project. Each Warpgate deployment should use its own service account.

Monitoring

Real-time metrics

Real-time metrics are under development and will be available before launch.

The Console displays real-time metrics for your projects:

• Traffic volume: requests per second, total requests
• Authentication outcomes: successful logins, failed attempts, token validations
• Error rates: 4xx and 5xx responses
• Latency: response time distribution
• Warpgate status: connection state of all registered Warpgates

Billing dashboard

The billing dashboard is under development and will be available before launch.

Track your spending in real time:

• Current period spend: how much you’ve used this billing cycle
• Per-project breakdown: cost attributed to each project
• Usage metrics: bandwidth, authenticated users, Warpgate count
• Spending alerts: notifications as you approach limits
• Hard cutoffs: optional maximum monthly spend that pauses service rather than incurring charges

Team management

Invite team members to your organization and control access:

• Invite by email: team members join your organization
• Role assignment: control what each member can view and modify
• Project-level access: scope permissions to specific projects
• Audit trail: every action in the Console is logged