Connector Hub
Connector Hub · runtime infrastructure
Connector Hub
Every connection becomes governed runtime infrastructure.
Connector Hub maps OAuth readiness, permissions, diagnostics, topology, and governed recovery guidance.
Connector Hub
Connector Hub · runtime infrastructure
The problem
Disconnected setup screens hide the real operational question: what is connected, what is unhealthy, what it affects, and how safely it can be recovered.
You rely on dozens of SaaS connectors and want to see readiness at a glance.
Incidents in connectors can silently break campaigns, finance, or workflows.
You want governed repair paths instead of ad-hoc reconnect clicks.
Why businesses choose Connector Hub
Connector readiness at a glance
See which providers are healthy, degraded, or blocked across the platform.
Impact-aware diagnostics
Trace how a degraded connector affects modules, workflows, and revenue.
Governed repair posture
Guide operators through safe reconnect and recovery paths without hidden automation.
Connector Hub underpins every OS, keeping marketing, sales, finance, RTW, and growth surfaces honest about dependency health.
Connects to
- OAuth apps
- Provider permissions
- Diagnostics
- Topology
- Recovery paths
How it works
- 1OAuth
- 2Readiness
- 3Diagnostics
- 4Topology
- 5Recovery
Readiness lanes
Group connectors by healthy, attention, blocked, and reconnect-required posture.
Topology context
Show which workflows, capabilities, and product surfaces depend on each connector.
Guided recovery
Make repair paths clear while preserving OAuth, admin, and approval boundaries.
Evidence posture
Logged-out preview only; tenant evidence loads after sign-in.
Outcome
Operators can see readiness, diagnose issues, trace impact, and navigate to existing governed recovery paths.
Signal source
Connector diagnosticsIssue cards show source, freshness, failure reason, and affected modules.
Policy state
Reconnect governedNo connector mutation is launched from public story pages.
Impact source
Topology graphDependency traces show what a connector affects before recovery is considered.
- Permission checks
- Reconnect governance
- Runtime posture
- Topology impact
Evidence rail
Open the console to inspect tenant-scoped evidence for Connector Hub.
Open evidence in console →Related agents
HERMES
Agent profile →HERMES
Surfaces handoff, SLA, and bottleneck posture for operator review without substituting ATLAS orchestration.
Operator console (Next.js)
Agent profile →
Operator console (Next.js)
Primary control-plane experience for pilots and demos; uses cookie-based JWT to `/api/v1/*` (see `apps/web/middleware.ts`).
Marketing OS (MERCURY module surface)
Product story →
Marketing OS (MERCURY module surface)
Primary operator workspace for governed marketing operations; MERCURY domain agent manifests in integration topology.
Sales OS (AUCTOR module surface)
Product story →
Sales OS (AUCTOR module surface)
Primary operator workspace for governed sales and pipeline intelligence; AUCTOR domain agent manifests in integration topology.
Growth Command Center
Product story →
Growth Command Center
Single pane for demand-to-revenue posture when one or both commercial modules are active.
API ingress & identity boundary
Agent profile →
API ingress & identity boundary
Single controlled ingress for the TypeScript kernel; aligns with API-first posture.