Robin Suite

Robin Admin / Operations Platform

Your infrastructure.
Visibility meets action.

Monitor services, explore telemetry, investigate email authentication reports, and operate your mail estate from one self-hosted workspace.

Use Admin independently for monitoring, metrics, or reporting—or bring those capabilities together with service operations. The Robin suite is one way to deploy it, not a requirement.

Self-hosted · Apache 2.0 · No Robin MTA required

Robin Admin mascot

Four Ways to Put Admin to Work

More than a mail-server panel.

Start with the capability you need. Monitoring, Telemetry, and Reports do not require Robin MTA or a registered fleet of mail services.

Monitor

Checks & Incidents

Track reachability, email delivery, and availability. Investigate issues, send alerts, and publish a customer-facing status page.

Explore Monitoring
Measure

Telemetry & Dashboards

Bring in Prometheus-compatible infrastructure metrics. Build dashboards, explore with PromQL, and understand resource behavior.

Explore Telemetry
Investigate

Email Report Intelligence

Understand sending sources, domain conformance, and transport security through DMARC, TLS-RPT, and forensic evidence.

Explore Reports
Operate

Mail-Service Fleets

Move from fleet health to queues, protection, sessions, logs, and managed settings across supported service types.

Explore Fleet Operations

Notice the Issue. Investigate the Evidence. Take the Next Action.

Keep monitoring, metrics, email intelligence, and supported service controls in one operational workspace—without treating an availability check, a resource graph, and a delivery report as the same signal.

See It Running

The real console. A working local suite.

These captures come from a running Robin suite. Operator and mailbox identities are fictional; mail flow and scanner activity come from synthetic samples processed by real services. Health, monitoring, and resource measurements are actual local observations—not production benchmarks.

Robin Admin operational dashboard with fleet health, mail flow, external monitoring, service summary, telemetry sources, and protection pressure
Six suite services, eight passing checks, and delivery of synthetic test messages in the local demo. View Full Size

Select any screenshot to inspect the full-resolution capture. Report workspaces are documented below but are not shown in this demo tour.

Fleet Operations

Go beyond observing your mail estate.

Operate supported mail services with service-specific controls. Combine queues, protection, mailbox administration, and operational settings with fleet-wide health and capacity context.

Accounts

Mailboxes & Routing

Manage users, aliases, and auto aliases against your compatible PostgreSQL mailbox tables.

  • Create accounts and reset passwords.
  • Maintain role addresses and forwarding.
  • Apply domain-wide alias rules.
Mailbox Guide
Delivery

Queues & Service Operations

Inspect Robin queues and run delivery tests. Operate Postfix queues, Dovecot sessions, and database services where your deployment supports them.

  • Investigate delayed delivery.
  • Look up mailbox quota and sessions.
  • Read service metrics and logs.
Fleet Guide
Protection

Scanning, Rules & DKIM

Work with Rspamd and ClamAV as independent services. Investigate scanner results and manage the supported protection settings.

  • Run scan labs and classifier experiments.
  • Manage Rspamd rules and training.
  • Manage DKIM keys and selectors.
Service Capabilities

Your Managed Stack

One fleet. Service-specific controls.

Connect the Robin suite's services or register supported components from an existing estate. Integrations remain independent; you don't need Robin MTA to operate Rspamd or monitor a Postfix host.

Fit the Controls to the Topology

Available capabilities depend on service endpoints, credentials, agent access, and the way services are deployed. Host-side actions need a suitable agent; metrics and logs need a reachable source.

Admin hides unsupported controls rather than presenting a workspace that can't work.

Explore the Capability Matrix

Shared Defaults. Instance-Level Control.

Manage operational settings with shared defaults and per-instance overrides. Connect mailbox administration to your PostgreSQL account tables.

Mailbox Integration Guide

Monitoring & Incident Management

Check the service.
Communicate its status.

Monitor external endpoints and email delivery independently of Fleet metrics. Follow availability and response-time history, investigate issues, and configure alert delivery.

  • Probe locations, confirmation and recovery windows, and location history.
  • Certificate validation and expiry-warning policies for TLS checks.
  • Issue lifecycles and alert delivery history.
  • Public status pages with selected components, incidents, updates, and maintenance windows.
Monitoring & Status Page Guide
Monitoring workspace with eight passing real service checks and configurable check actions
Availability checks and service status in the local demo. View Full Size

General-Purpose Telemetry

Your metrics.
Your dashboards.

Explore infrastructure metrics beyond the mail stack. Collectors such as Vector push Prometheus-compatible samples; Admin gives operators a workspace to discover sources, build dashboards, and query with PromQL.

  • Build and edit dashboards in the UI.
  • Investigate metric series in PromQL Explore.
  • Use bundled VictoriaMetrics or configure a supported external store.
  • Keep ingest authenticated and the metrics store behind Admin.
Telemetry Guide
Host telemetry dashboard showing real CPU, memory, storage, and network measurements
Live measurements captured from the local Docker Linux host, not a production benchmark. View Full Size

DMARC & TLS Reporting Intelligence

Know who sends for your domains.
Understand the evidence.

Make email authentication and transport-security reports useful to operators. Investigate sending sources, domain conformance, and TLS posture without needing Robin MTA to handle your mail.

Start With the Operational Question

Use reporting intelligence to review sender inventory, examine domain posture, triage issues, and plan remediation.

  • Overview for a timeframe-scoped view.
  • Sources and Domains for sender and conformance investigations.
  • A record-level Explorer for focused analysis.

Drill Into the Raw Evidence

Keep raw report workspaces alongside the intelligence layer. Inspect the underlying records when a summary is not enough.

  • DMARC aggregate reports.
  • TLS-RPT transport-security reports.
  • AFRF / forensic evidence, with filters and drill-down.

Reports require configured ingestion and report data. Report screenshots are not included in this tour.

Reporting Intelligence & Evidence Guide

Operator Access

Control who can do what.

Role-aware navigation, scoped API keys, session authentication, configurable access policies, and activity history support accountable administration.

  • Browser sessions with CSRF protection.
  • Revocable API keys with scopes, optional expiry, and network restrictions.
  • Login lockouts and configurable IP allowlists.
  • Audited administrative actions.
Authentication & Access Guide
Extend the Workspace

Robin Tools, Inside Admin

Add diagnostics without leaving your administrative workflow. Robin Tools runs as a separately deployed module; Admin provides navigation, authenticated proxying, and operator identity.

The module appears when its runtime is reachable and the required trust and proxy configuration is in place.

Explore Robin Tools Module Setup Guide

Deployment

Start with your use case.
Not a particular mail server.

Deploy independently for monitoring, telemetry, or email reporting. Connect an existing mail estate when you need fleet controls—or join the Robin suite. Admin runs with an HTTPS gateway, UI, API, PostgreSQL connectivity, and bundled telemetry storage.

Join the Robin Suite

Start the mail stack first, then deploy Admin with its suite overlay to join the shared network and connect to the suite's database and services.

docker compose -f docker-compose.yaml -f docker-compose.suite.yaml up -d
Suite Deployment Guide

Run an Independent Operations Platform

Start with the standalone layout and its own database. Enable Monitoring and configure checks, enable Telemetry and connect collectors, or configure report ingestion. No mail fleet or Robin MTA is required for those workspaces.

For service operations, register supported services and configure their access. A host-networked layout is also available for existing mail hosts.

docker compose up -d
Getting Started Guide

The getting-started guide walks through deployment, first-boot setup, service connections, and capability configuration.

Independent by Design

Your operations platform.
Your choice of infrastructure.

Use the capabilities you need. Add the Robin suite for self-hosted mail infrastructure, or Robin Tools for interactive diagnostics.