Console. One interface for your entire stack.
The Console is where Mezusphere becomes operationally understandable. One management surface for projects, environments, routes, authentication, users, Warpgate status, metrics, and billing, replacing the half-dozen vendor dashboards you are currently jumping between.
What the Console does
The Console lets you do four things well:
Define
Define what exists
Create projects and environments. Set up the organizational structure for your services. Each project represents one service or application, with isolated environments for development, staging, and production.
Configure
Define how traffic should behave
Configure routes, path-based routing rules, redirects, CORS settings, and failover policies. Every aspect of traffic delivery is controlled from a single screen; no YAML files, no proxy configuration.
Secure
Define who should have access
Enable authentication with a toggle. Manage user directories, configure authorization rules, create service accounts for Warpgates, and control access for humans, devices, services, and AI agents.
| Name | Status | IP Address |
|---|---|---|
wg-prod-us-east-1a | Connected | 10.0.1.42 |
wg-prod-us-east-1b | Connected | 10.0.2.18 |
wg-prod-eu-west-1a | Reconnecting | 10.1.3.7 |
| Path | Upstream | Auth |
|---|---|---|
/api/v1/* | localhost:8080 | Auth required |
/health | localhost:8080 | Public |
/webhooks/* | localhost:9090 | Auth required |
Key capabilities
Everything you need to configure, monitor, and operate your Mezusphere deployment, in one place.
Projects and environments
Organize workloads into projects, each with isolated environments. Manage team access and permissions at the organization level. Clear environment model for development, staging, and production.
Routes and traffic control
Define path-based routes to backend services. Configure redirects and manage failover, with custom domains on the roadmap. Three matching modes: prefix, exact, and regexp.
Authentication and authorization
Enable auth with a toggle. Manage user directories, configure per-route authorization rules, and control access for humans, devices, services, and AI agents, all from the same interface.
User management
Create and manage user directories and user accounts. Handle account lifecycle: create, suspend, update, and support actions. The back-office identity surface comes with the platform.
Service accounts and credentials
Create service accounts for Warpgate registration and API access. Each service account has an API key and configurable permissions, scoped to a specific project.
Warpgate status monitoring
See every connected Warpgate, its connection state, IP address, and the environment it belongs to. Know instantly what is deployed and what is actually connected.
Usage and status views
Monitor traffic volume, data in and out, authentication outcomes, and error rates across all Warpgates and routes, with every error attributed to its origin: your workload or the platform. One place answers "what is flowing" and "whose fault is it" instead of stitching together many dashboards.
Usage and spend controls
Track usage in real time with per-project breakdowns. Spend tracking, alerts, and hard monthly cutoffs land with the pricing model ahead of general availability.
Team management and audit
Invite team members, assign roles, and scope permissions to specific projects or environments. A queryable audit log of Console actions is on the roadmap.
Why the Console matters
You don't choose Mezusphere just because the architecture is elegant. You choose it because it reduces operational complexity. The Console is where that reduction becomes visible.
Less vendor-dashboard hopping
Without Mezusphere, teams jump between separate dashboards for routing (Cloudflare), auth (Auth0), API gateway (Kong), security (AWS WAF), DNS (Route 53), and billing (each vendor separately). The Console consolidates these into one interface.
Faster onboarding
Small teams do not want to operate infrastructure by YAML and proxy config alone. The Console provides clear workflows for every step from project creation to production deployment, without requiring infrastructure expertise.
Operational visibility
See what is deployed, what is connected, who is authenticated, and how much you're using, all in real time. The Console turns "a multi-plane cloud platform" into "a simpler way to publish and secure services."
What the Console replaces
The Console is not just a dashboard. It is the coordination surface that replaces the combined use of multiple vendor management interfaces.
| Workflow | Traditional approach | With the Console |
|---|---|---|
| Route configuration | NGINX config, Kong Manager, Traefik dashboard | Visual route editor |
| TLS and DNS setup | ACM + Route 53, Cloudflare dashboard | Automatic, no manual setup |
| Auth configuration | Auth0 dashboard, Cognito console, Keycloak admin | Toggle per route |
| User management | Auth0 user management, Cognito admin APIs | Built-in user directories |
| Connector status | Custom monitoring, cloud health checks | Live Warpgate status view |
| Traffic metrics | CloudWatch + Grafana, Datadog, CDN analytics | Real-time metrics dashboard |
| Billing | Six to ten separate vendor invoices | Per-project usage breakdown; billing at GA |
Key workflows
The Console makes the core Mezusphere deployment workflow straightforward:
1. Create a project
Navigate to your organization, create a project with a name and description. A default development environment is created automatically.
2. Set up environments
Add production and staging environments. Each gets a unique endpoint URL and independent configuration for routes, auth, and connected Warpgates.
3. Create service accounts
Generate API keys for Warpgate registration. Copy the token and use it when deploying Warpgates. Each deployment should use its own service account.
4. Define routes
Configure path-based routing rules for how traffic reaches your workload. Set matching mode, enable authentication, configure CORS, and set up redirects.
5. Enable authentication
Toggle authentication on per route. Choose a user directory, configure required permissions, and set up access policies. Built-in; no external provider needed.
6. Monitor and manage
Watch Warpgate connection status, monitor real-time traffic metrics, track spending, and manage team access, all from the same interface.
One console. Zero vendor-dashboard hopping.
Routes, authentication, users, metrics, and billing, managed from a single interface instead of six separate vendor dashboards. See how Warpgate connects your workloads, or reach out at hello@mezusphere.com to learn more.