Virtum

Virtum Operations

Requests and incidents, evidence attached.

Run IT as a service, day to day: requests, incidents, people, access and cost, with the evidence attached.

Become a design partner See all 115 features

Private development Design partners Q1 2027 · wider access Q2 2027 (targets)

Why it exists

IT runs in silos, so every answer means asking around.

The service desk, incident tools, identity administration and cloud bills usually live apart, so nobody sees the whole picture. Operations connects them: an alert becomes an owned incident, a request is fulfilled and checked, starters and leavers are handled end to end, and managers see cost, service and risk on one page.

How it works

Receive → Act → Verify → Report

  1. 01ReceiveRequests, alerts, tickets, starters and leavers arrive in one place.
  2. 02ActRunbooks, fulfilment and changes run with approval.
  3. 03VerifyVirtum checks each outcome actually happened.
  4. 04ReportCost, service and risk, on one page and in monthly reports.

In practice

An incident, end to end

  1. Payment latency breaches its objective. An incident opens itself.

  2. On-call is paged. A change made at 13:40 is linked as the likely cause.

  3. A runbook to restart the payment workers is proposed. You approve it.

  4. Latency recovers. The status page updates customers.

  5. The postmortem is drafted into Docs, with follow-up actions as tasks.

Who it's for

Built for the people who run it.

  • Service desks and IT operations

    Requests and incidents handled with the context attached.

  • Service providers

    Run many clients from one place.

  • Managers

    Cost, reliability and risk at a glance.

How it connects

Connected to everything else.

Work passes between Virtum's services on its own. Nothing is retyped, and nothing falls between tools.

  • Deploy → Operations · alerts, cost

    Deploy

    Alerts, changes and cloud cost come from Deploy.

  • Operations → Docs · postmortems

    Docs

    Incidents leave postmortems; reports are built from evidence.

  • Operations → Planner · owned work

    Planner

    Tickets and incidents become owned work.

  • Operations → Security · access risks

    Security

    Identity and access findings feed security posture.

See it end to end →

What it does today

Everything in Operations.

115 features across 15 areas. Search them, or open an area. The roadmap shows what comes next.

115 features
Command centre Your whole estate, live.7
  • Overview of service health, incidents, latency and error budgets
  • Estate map as topology or heatmap
  • Map views for health, latency, saturation, errors, cost and SLOs
  • Activity timeline linking changes to incidents
  • Correlated security and operations signals
  • Alerts inbox and collector freshness
  • Executive overview with a board-ready narrative
Incidents From first signal to postmortem.10
  • Declare incidents with a severity matrix
  • Escalate to a major incident; suggested when alerts cluster
  • A timeline that cannot be quietly altered
  • Status updates to customers and status pages
  • Approve or reject proposed automated fixes
  • Recent changes linked as likely causes
  • Follow-up actions tracked to closure
  • Postmortems, evidence packs and incident reports
  • Response analytics by service and responder
  • Incidents declared automatically from monitoring
On-call, SLOs and status pages Reliability you can measure and promise.6
  • On-call schedules, rotations and overrides
  • Escalation that pages the rota
  • SLOs with error budgets and burn-rate alerts
  • Releases held when an error budget runs out
  • Public, branded status pages
  • Synthetic journey and uptime checks
Runbooks and automation Procedures that run themselves, safely.5
  • Versioned runbooks from templates
  • Runs with inputs, approval gates and evidence capture
  • Pause, resume or abort runs
  • Scheduled runbooks
  • Runbooks triggered by events
Service desk Requests answered, with the context attached.6
  • Ticket queue with workload view
  • Replies, internal notes, classification and assignment
  • Tickets linked to devices, deployments, findings and changes
  • Bulk actions
  • Customer support portal with satisfaction surveys
  • Problem management and known errors
Changes and capacity Change with confidence.5
  • Change calendar and freeze windows
  • Maintenance windows
  • Change audit log
  • Change risk shown before approval
  • Capacity headroom and growth scenarios
Self-service Requests fulfilled and checked automatically.7
  • Employee self-service portal and request catalogue
  • Requests offered only to eligible people
  • Approver queue with requests for more information
  • Catalogue administration from templates
  • Automatic fulfilment through connected systems
  • Checks that each request actually worked
  • Knowledge suggestions alongside requests
Identity and access Who has access to what, and whether they should.8
  • Entra and Google Workspace directories in one inventory
  • Third-party app (OAuth) permission review
  • Identity posture score with fixes
  • Conditional access gaps
  • Privileged activity monitoring
  • Access reviews with outliers
  • Stale accounts and segregation-of-duties rules
  • Service accounts with credential rotation
Microsoft 365 Microsoft 365 run from Virtum, every change approved first.12
  • Choose which areas of Microsoft 365 Virtum may change
  • Create users with their licences and groups in one approval
  • Leavers blocked, signed out and handed over, mailbox and OneDrive included
  • Conditional Access baselines, trialled in report-only mode first
  • Conditional Access drift checked daily, with rollback
  • Licences assigned, removed and swapped per person, with approval
  • Microsoft 365 Backup policies for mail, OneDrive and SharePoint
  • Restore a mailbox, OneDrive or site, or single emails
  • Teams Phone numbers ordered, ported in and assigned to people
  • Email domain checks for SPF, DKIM and DMARC, with fixes
  • Takeover audit of a previous provider's admin access, apps and mail forwarding
  • Remove the previous provider's access, with a handover checklist
Devices with Intune Microsoft Intune managed from Virtum.8
  • Baselines for Windows, macOS, iOS and Android, with drift and rollback
  • Encryption, antivirus and local admin password baselines
  • Device actions: sync, restart, locate, retire, wipe and more
  • Wipes need a second person to confirm the device name
  • Findings with fixes: non-compliant, stale and unencrypted devices
  • Autopilot device import, group tags and deployment profiles
  • Assign Store apps and Microsoft 365 Apps
  • Password rules that meet Cyber Essentials v3.3
Joiners, movers and leavers Starters set up, leavers locked out, both verified.11
  • Lifecycle cases: plan, approve, schedule, execute, verify
  • Access profiles with versions
  • Licences reserved before a joiner starts
  • Changes pushed to Entra, Google Workspace and AWS IAM
  • Licence inventory and reclaim
  • Leaver device wipe
  • Hostile leaver lockdown: sign-in blocked, sessions ended, MFA cleared
  • Applications register with each app's joiner and leaver steps
  • Bitwarden invites joiners and removes leavers under the same approval
  • Password manager checks for leavers and members without two-step login
  • Bulk people import
Cloud and cost oversight The manager's view of spend.7
  • One overview across AWS, Azure and GCP
  • Month-to-date spend, change and month-end forecast
  • Owner and business purpose for every resource
  • Spend assigned to teams and customers
  • Budgets, anomalies, waste and rightsizing
  • Showback reports
  • AI spend and caps
Client management For service providers running many customers.9
  • Switch between client organisations
  • Delegated, time-boxed access to clients
  • Per-client markup and monthly statements
  • Client portal with status and reports
  • Per-client branding
  • Ownership coverage and a CMDB per client
  • Service coverage per client: who looks after each part of their IT
  • Coverage gaps you add to your catalogue, exclude or leave with a third party
  • Monthly reports and QBR exports
Sales and CRM Find, win and hand over customers.7
  • Discover businesses and score prospects
  • Accounts, contacts, meetings and activity
  • Opportunity pipeline with forecast
  • Quotes and proposals with approval
  • Outreach and sequences you approve before sending
  • Replies inbox and campaign attribution
  • Sale-to-delivery handoff
Growth Your web presence, measured and improved.7
  • Website estate with ownership verification
  • SEO crawls and search performance
  • Content briefs and AI drafts in your brand voice
  • Site changes with approval
  • Ads with budget and creative approval
  • Conversion tracking and experiments
  • Growth reports

Connected today

Works with what you already run.

Every integration runs through the same approvals and audit trail, and new ones are added as data, so the list keeps growing. How integrations work →

Directories and identity

  • Microsoft Entra ID
  • Google Workspace
  • AWS IAM
  • Intune

Cloud

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud

Advertising

  • Google Ads
  • Microsoft Ads
  • Meta

Microsoft 365

  • Microsoft 365
  • Exchange Online
  • Microsoft 365 Backup
  • Microsoft Teams Phone

Telephony

  • Telnyx

Password managers

  • Bitwarden

Shared by every service

Plus the whole Virtum platform.

Put Operations to work.

Design partners get early access and help shape what comes next. Or let Virtum run it for you as a managed service.

Become a design partner Prefer we run it for you?