Local Console

The Local Console (mvgc-console) is a web dashboard that runs alongside your Axemere gateway. Open http://localhost:7091 in your browser to see live traffic, manage credentials and workloads, inspect execution records, and edit your policy, all running on your own machine with no account or internet connection required.

Starting the console

The Local Console is a separate binary from the gateway. You can run it alongside the gateway or leave it out; it has no effect on gateway operation.

Docker Compose

In the standard Docker Compose setup, mvgc-console is a separate service. Both start together with:

docker compose up -d

To start the gateway without the console:

docker compose up -d mvgc

Native install

Run the mvgc-console binary directly (start the gateway first):

mvgc-console

Accessing the console

Once running, open http://localhost:7091. The console listens on port 7091 by default, separate from the gateway proxy port (7080).

To change the port, set CONSOLE_LISTEN_ADDR:

CONSOLE_LISTEN_ADDR=:8080        # all interfaces, port 8080
CONSOLE_LISTEN_ADDR=0.0.0.0:7091 # explicit all-interfaces bind

In Docker Compose, set it in the mvgc-console service environment block:

services:
  mvgc-console:
    environment:
      CONSOLE_LISTEN_ADDR: ":7091"

The listen address can also be set in the gateway configuration file: see the Configuration Reference.

The Local Console has no built-in authentication. If you expose it beyond loopback, restrict access with a reverse proxy or firewall rule.

Stopping the console

Stop the console independently without affecting the gateway:

# Docker Compose
docker compose stop mvgc-console

# Native
kill $(pgrep mvgc-console)

Two modes

Standalone (Free Gateway)

All pages are fully editable. You create and manage workloads, credentials, providers, and policies directly in the console. This is the default for free self-hosted gateways with no control plane connection.

CP-connected

If your gateway is registered with the Axemere control plane, configuration pages become read-only and a banner appears directing you to the Axemere Cloud Console at console.axemere.ai.

Using a CP-connected gateway? The Cloud Console at console.axemere.ai is the right tool for managing configuration. The Local Console remains useful for live traffic monitoring and record inspection on this node, but all configuration changes, workloads, credentials, and policies, should be made in the Cloud Console.

Pages

Analytics

Monitor

Configure

Govern

Other