Observability · IT asset management · AI assistant

Observability and IT asset management, in one platform

VerOps collects traces, metrics and logs over OpenTelemetry, tests your services from the cloud or inside your network, and inventories every machine with the Scout agent. Vera, the built-in assistant, answers questions across all of it.

  • OpenTelemetry (OTLP over HTTP)
  • Linux and Windows agents
  • Cloud or self-hosted test locations
  • ClickHouse storage with rollups
app.verops.io/dashboardsIllustration · sample data

Dashboards: service KPIs, latency, host CPU, synthetic results and alerts on one screen.

Dashboards: service KPIs, latency, host CPU, synthetic results and alerts on one screen.

Platform

One account, one data store, one set of agents

Application monitoring, infrastructure, testing and IT assets share the same tenant, permissions and agents, so the application view and the asset view of a machine are the same machine.

Observe

Traces, metrics and logs, from one request to the whole fleet

Ingest over OpenTelemetry or the VerOps agents. Telemetry is stored per organisation in ClickHouse and queried from dashboards, explorers, SQL and Vera.

  • APM and distributed tracing

    Java auto-instrumentation for Servlet, Spring MVC, JDBC, Kafka and HTTP clients; other languages through OpenTelemetry SDKs. Service map, trace waterfall and flame graph.

  • Metrics and logs

    OTLP metrics with 5-minute, 30-minute and daily rollups for long ranges. Logs over OTLP or from the machine agent’s file collector, searchable by text, service, level and time.

  • Hosts, Kubernetes and real users

    Machine agent for Linux and Windows, a Helm-installed Kubernetes agent, and a browser SDK for Core Web Vitals, errors, sessions and funnels.

Trace and logsIllustration · sample data
POST /checkouterror512 ms · 6 spans
0 ms128256384512 ms
api-gateway POST /checkout
auth-svc verifyToken
cart-svc GET /cart/{id}
postgres SELECT cart_items
payment-api POST /charge
kafka publish order.created
Logs for this trace
INFOcart-svccart 81f2 loaded, 3 items
WARNpayment-apicard processor slow, retrying (1/2)
ERRORpayment-apicharge failed: upstream timeout after 250 ms
Test

Test from the outside and from inside your network

Active checks catch what passive telemetry cannot: a broken login, a slow DNS resolver, a path that drops packets.

  • Synthetic monitoring

    Browser journeys in Playwright and API checks. Failed runs keep screenshots and video, and TOTP-protected logins are supported.

  • Cloud or self-hosted locations

    Run checks from VerOps cloud agents, or from self-hosted agents inside your own network to test internal services.

  • Network monitoring

    Ping, traceroute, TCP, UDP, DNS, HTTP, TLS, MTU and bandwidth probes; SNMP v3 polling and traps; LAN discovery and a topology view.

Synthetic runIllustration · sample data
Checkout journeyBrowser · Playwrightrun #2,114
Cloud agent Self-hosted · office LAN
  1. 1. Open storefront0.84 s
  2. 2. Sign in with TOTP1.21 s
  3. 3. Add item to cart0.66 s
  4. 4. Submit payment3.90 s
4 screenshots Video HAR
Network probesbranch-office → api.example.com
Ping18 ms
DNS9 ms
TLS41 ms
HTTP212 ms
Traceroute11 hops
MTU1500
Manage assets

Know every machine you run, not only the ones you monitor

IT asset management on the same platform and the same tenant, reported by the lightweight Scout agent.

  • Hardware, software and users

    Scout reports hardware, installed software, users and patch posture for each machine.

  • Products, licences and risk

    Software is grouped into products, with licence position, asset financials and known vulnerabilities matched from OSV.

  • Presence and reports

    Office or remote presence per host from network classification, with daily to yearly history and exportable inventory reports.

AssetIllustration · sample data
ENG-WS-114Windows 11 23H2 · a.karim
Office today
Hardware
16 cores · 64 GB · 1 TB NVMe
Software
142 installed · 96 products
Patch posture
Up to date · checked 2 h ago
Vulnerabilities
2 known (OSV)
Licences
CAD Suite 2025 · assigned
Financials
Purchased 03/2024 · cost recorded
Presence this week
M
T
W
T
F
OfficeRemote
Respond and automate

From the first alert to the fix, in one place

Route the right signal to the right person, then work the incident with the evidence already attached.

  • Alerting, on-call and SLOs

    Alert rules, silences, on-call schedules with overrides, escalation policies and SLO burn-rate alerts. Notify by email, Slack, Microsoft Teams, PagerDuty, Opsgenie, Jira, SMS, Discord or webhook.

  • War rooms

    A war room collects the affected topology, a timeline and related evidence, and can open automatically after repeated synthetic failures.

  • Workbooks

    Multi-step runbooks across browser, API, trace, log, database and network steps, with branches, approvals and actions. Results can gate a CI pipeline.

IncidentIllustration · sample data
Incident timelinepayment-api
  1. Alert: error rate above 2%payment-api · critical
  2. Paged primary on-callEscalation step 1 · Slack, PagerDuty, SMS
  3. War room openedTopology, timeline and related evidence attached
  4. Workbook “Checkout smoke” ran6 of 6 steps passed after the fix
  5. ResolvedSLO error budget: 71% remaining
SLO burn rate · 1 h
AI

Vera: an assistant that works from your own data

Ask in plain language. Vera answers with tools over your dashboards, inventory and network data, and drafts dashboards for you to review.

  • Vera

    Questions across services, hosts and assets in one conversation. Drafts stay drafts until you review them.

  • Sentinel

    Evaluates AI agents and LLM endpoints with an LLM judge and rule-based checks, scored across quality, safety, grounding, reliability and custom dimensions.

  • Monitor discovery

    Opens your application in a real browser, records the API calls it makes and drafts a monitoring workbook from them.

Vera and SentinelIllustration · sample data
Vera
Why is checkout slow since 14:00?
dashboards · checkout network · paths

p95 on POST /checkout rose from 410 ms to 812 ms at 14:02. Most of the time is inpayment-api calls to the card processor; network paths from both sites are healthy.

Sentinel · support-botLLM judge + rule checks
Quality92
Safety98
Grounding84
Reliability95
3 answers not grounded in the provided context
How it fits together

From signal to action

One path for every kind of data, so an alert, a dashboard and a Vera answer all read from the same place.

  1. 01

    Collect

    OpenTelemetry SDKs and collectors, the Java agent, the machine, Kubernetes, network and Scout agents, synthetic checks and the browser SDK.

    • OTLP HTTP
    • Java agent
    • Machine agent
    • Scout
    • Helm
  2. 02

    Store and query

    Telemetry is stored per organisation in ClickHouse and queried from dashboards, explorers, SQL and Vera.

    • ClickHouse
    • 6 h and daily rollups
    • SQL
    • Data Explorer
  3. 03

    Act

    Alerts route through on-call schedules and escalation policies; war rooms and workbooks take it from there.

    • On-call
    • Escalations
    • War rooms
    • Workbooks
Security and access

Controls built into the platform

  • Tenant isolation

    Every query is filtered to the signed-in organisation.

  • Role-based access

    Permissions per module, for example view versus manage.

  • Multi-factor sign-in

    TOTP authenticator apps for user sign-in.

  • Encrypted credentials

    Stored secrets, such as integration credentials, are encrypted at the field level.

See VerOps on your own systems

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