What Vera can look at

Vera only sees what the signed-in user is allowed to see.

AreaExamples
TelemetryMetrics, logs, traces, services and their dependencies
ReliabilityAlerts, SLOs, silences, incidents, war rooms, on-call
TestingSynthetic tests, network tests, SNMP devices
PlatformsKubernetes, RUM, workbooks, dashboards
IT assetsDevices, software products, usage, licence position, presence
Network investigationTop talkers, path changes, topology changes
DocumentationThe VerOps docs, for how-to questions

How teams use it

  • Investigate

    Ask why a service got slower, what changed before an alert fired, or which hosts are behind on patches, and get an answer built from your own data.

    Documentation
  • Draft dashboards

    Describe the board you want. Vera drafts it, and you review it before it is saved.

  • Propose changes

    When an action would change something, Vera shows an approval card. Nothing runs until a user with the right permission approves it.

  • Share findings

    Export an investigation as a PDF with selectable text and tables.

Governance

  • Your permissions

    Vera works inside the role-based access of the user asking. It cannot see other organisations’ data.

    Learn more
  • Approval before change

    Proposals are applied only when a user approves them.

  • Bring your own model

    Connect Anthropic, OpenAI, Azure OpenAI, Mistral, OpenRouter, Ollama or any OpenAI-compatible endpoint with your own keys.

  • Keys encrypted at rest

    AI provider keys are stored encrypted.

Try it on your own systems

Create a workspace, or tell us about your environment and we will walk you through it.