Documentation
Console

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 end-user authentication and manage users
  • Monitor traffic, authentication outcomes, and connector health
  • Track usage; spend controls land with the pricing model

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.io)
  • 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

Mezusphere provides built-in end-user authentication at the edge, with no external identity 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. End users sign in with passkeys (WebAuthn) or a password plus TOTP, and your workload receives their verified identity as request headers — see Authentication.

Manage users

When authentication is enabled, you 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)

Each environment with authentication enabled gets its own user directory, so your production, staging, and development user pools stay separate.

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

Usage and operational visibility

The Console gives you a real-time view of your traffic and the health of your deployment:

  • Usage: requests, bytes in/out, sign-ins, and registrations — per organization, project, and environment, in neutral units
  • Connector health: connection state, last-seen time, and active tunnels for every registered Warpgate
  • Route and environment health: per-route and per-environment request and error rates
  • Tunnel and upstream failure rates: where traffic is breaking, broken out by stage
  • Fault attribution: every error is attributed to either the platform or your own workload, so you can tell at a glance whether a problem is yours or ours

Your Warpgates can also expose a standard Prometheus /metrics endpoint for your own monitoring stack — see the Warpgate reference.

Usage and spending

Track your consumption in the Console:

  • Usage metrics: bandwidth, authenticated users, requests, and Warpgate count
  • Per-project breakdown: consumption attributed to each project and environment

Cost reporting, spending alerts, and hard spend cutoffs are finalized alongside Mezusphere’s pricing ahead of general availability.

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: a queryable log of Console actions is planned