Skip to content
Zentro
Console

For users & teams

Product demo

Use the interactive tour below to explore core product workflows.

Interactive tour

1 / 8

Use Prev / Next or keyboard arrows. Links open the real console route (sign in if required).

/

Hook — problem and promise

Teams need guardrails when automation touches production. Zentro pairs incidents, approvals, and audit so changes stay accountable.

Review checklist

  • Use representative sample data in product walkthroughs.
  • Keep customer and credential information out of shared recordings.
  • Follow your organization’s review and publishing standards.
  • Use the scene list below to present workflows consistently.
  1. Scene 1

    Hook — problem and promise

    ~0:20

    /

    Do

    • Start on the marketing home page at 1280×720 or 1920×1080.
    • Scroll slowly through hero and one proof section.

    Say (guide)

    • Teams need guardrails when automation touches production. Zentro pairs incidents, approvals, and audit so changes stay accountable.
  2. Scene 2

    Enter the console

    ~0:25

    /hub

    Do

    • Sign in (or use local dev without Supabase if you are demoing offline mode).
    • Land on Hub and pause on the module grid so viewers see scope.

    Say (guide)

    • From Hub you reach overview, incidents, services, automations, approvals, governance, and settings — one shell for operations.
  3. Scene 3

    Operational picture

    ~0:35

    /overview

    Do

    • Open Overview and highlight error budget or summary widgets relevant to your deployment.

    Say (guide)

    • Overview surfaces burn and triage signals so leaders and operators share the same picture before anyone executes work.
  4. Scene 4

    Incidents end-to-end

    ~1:00

    /incidents

    Do

    • Open Incidents list, click one incident or create a short example.
    • Show timeline, status, and optional export or evidence actions available in your environment.

    Say (guide)

    • Incidents tie monitoring signals to ownership and narrative — exports support reviews and evidence packs when the database is wired.
  5. Scene 5

    Guarded automations

    ~0:45

    /automations

    Do

    • Open Automations, select a playbook if present, run or describe dry-run then guarded execution paths.

    Say (guide)

    • Dry-run and policy checks exist to block risky execution — we log what happened for audit, not just the UI state.
  6. Scene 6

    Approvals and governance

    ~0:40

    /approvals

    Do

    • Show a pending approval or create a low-risk example; approve or deny once.
    • Optional: open Governance → Policies for policy blocks or suggestions if configured.

    Say (guide)

    • Human approval stays in the loop where policy requires it; audits capture who decided and when.
  7. Scene 7

    Integrations and keys

    ~0:35

    /settings/connectors

    Do

    • Open Settings → Connectors or API keys; show connector health or token surfaces without revealing secrets on screen.

    Say (guide)

    • Reasoning and robot backends proxy same-origin; alert ingest and API keys stay server-side — viewers should never see live tokens in a recording.
  8. Scene 8

    Close — docs and API

    ~0:20

    /docs/api

    Do

    • Open public docs or HTTP API reference in a new tab; scroll the group list briefly.

    Say (guide)

    • Full route catalog lives under Docs — start at Zentro docs API for integration planning.

← Learn hub