My2Cloud 3.3 Release Notes

Released: August 2026

My2Cloud 3.3 introduces Mia, the My2Cloud intelligence assistant that answers plain-language questions about your resilience estate using your own data. This release also renames the platforms to their engine (vendor) names, adds outbound webhooks for service alerts, and brings a consistency pass to every engine's live views.

Mia - the My2Cloud intelligence assistant

Mia is a new, optional assistant embedded in the portal, reached from an Ask Mia button in the header. Mia answers from the portal's own data and never invents figures. It returns composed answers - a short narrative alongside charts, KPI tiles, tables, baseline comparisons and citations - rather than plain chat text. Mia is enabled by an administrator.

Ask Mia - conversational answers

• Ask a question in plain language ("how much Asigra storage am I using", "which VMs missed their RPO", "is anything failing") and Mia streams the answer as it is composed.
• Answers render as rich, branded blocks: a narrative, KPI bands, charts, ranked tables, baseline and month-on-month comparisons, alert lists and source citations. Storage figures are shown in human units (GiB/TiB) and every block is themed for light and dark mode.
• Mia decides whether a question is best answered from the live view or from historic snapshots, answers quickly, and offers a deeper investigation as a one-click follow-up.
• Conversation history: past chats are kept in a history drawer, long chats are summarised as they grow, and a New chat control starts a fresh thread.
• Ask Mia in context: an Ask Mia action appears on a service-alert notification and on the Asigra log and HYCU task-report views, opening Mia already primed to explain that item and recommend a fix.
• Mia only ever sees the engines you have enabled and the data your service filter allows.

What Mia can look up

Mia answers across every engine, plus support and billing:

• Capacity and usage (all engines): current consumed storage, capacity trend over time, and comparison to a baseline.
• Protected workloads (Asigra, CloudAlly, Veeam, HYCU): what is protected and how well.
• Backup health: Asigra backup-set types and at-risk sets, CloudAlly failing or stale sets, HYCU source breakdown, job summaries and job failures, Veeam backup jobs, licence usage and commit utilisation.
• Disaster recovery (Zerto): VPG, RPO and RTO adherence, protected VMs, replication performance and recovery activity.
• Live alerts and health: current alerts across Asigra, Zerto, Veeam and HYCU with per-entity log drill-down, and a fleet or per-engine health roll-up.
• Support and billing: your Freshdesk tickets (with the latest notes) and your Zoho Books invoices (with line items), honouring your support and billing permissions.

Grounded in the knowledge base

When Mia surfaces a problem, it consults the relevant engine's knowledge base and recommends how to remediate it, citing its sources so advice is grounded in vendor guidance rather than guessed.

Voice (optional)

• Dictate your questions and have Mia read answers back sentence by sentence as they stream, using natural voices. Voice is off by default.
• Dictation runs on-device and is preloaded for a fast first use, with mobile devices falling back to the browser's built-in dictation, and vendor names (HYCU, Zerto, Veeam) are transcribed correctly.

Reports (Mia Advanced)

Mia has two tiers. The Advanced tier adds reporting on top of the standard conversational assistant:

• Report composer: generate board, operations and partner reports on demand, view them in the portal, and export a PDF in the Assurestor house style.
• Scheduled reports: have the monthly board, operations or partner report emailed on a schedule. Off by default.
• Daily brief: an optional once-a-day roll-up of what changed (new alerts) across your estate. Unlike report generation, the daily brief is available whenever Mia is enabled, on either tier.
• Reports and briefs are delivered as individually subscribable notifications.

Engines - the service-brand to vendor-name change

My2Cloud now refers to each platform by its engine (vendor) name throughout the interface, replacing the "2Cloud" service brands. This is a naming change only; the underlying services, data, access and links are unchanged.

• The Services area is now Engines, and each platform is shown by its engine name: Asigra (was Backup2Cloud), Zerto (was DR2Cloud), CloudAlly (was SaaS2Cloud), HYCU (was SaaS2Cloud NG) and Veeam (was Veeam2Cloud).
• Engine names are used consistently across the navigation, page URLs, dashboard widgets, the Last Data Collection panel, and alert emails.
• Existing integrations and tenant links continue to work unchanged. Any saved bookmarks to the old service URLs should be updated to the new engine names.

Service alerts by webhook

Service alerts can now be delivered to an external HTTP endpoint, in addition to in-app and email notifications, so alerts can feed a help desk, SIEM or automation.

• Webhook subscriptions: subscribe an endpoint to service-alert events through a management page with a friendly event picker and event badges. Subscriptions are scoped to your own tenant.
• One event type covers every engine, and each alert is delivered once per tenant.
• The in-app alert inbox gained a service filter, now shows the engine name in the email subject, and defaults to the last 30 days.

Live views - KPI bands, filters and scale

Every engine's live views gained a KPI summary band and consistent, searchable filters, and the largest lists now load faster.

• KPI summary bands were added across the live views of every engine: Asigra (Accounts, Backup Sets, Monitoring), Zerto (Zorgs, VMs, Storage, Sites, Monitoring), CloudAlly (Users, Backup Sets, Tasks, Billing forecast), Veeam (Companies, Backup Jobs, Protected Data, Alarms, Backup Resources) and HYCU (SaaS summary, Sources). The bands track the active table filters, so the headline figures always reflect what is shown.
• Consistent filtering: searchable dropdown filters, a compound health filter on Zerto VPGs, a region filter on HYCU accounts, and company and status filters on a flattened Veeam Companies table. Date-range presets (Today plus a segmented range control) are standardised across the portal.
• The largest live grids (Veeam companies, Asigra and CloudAlly backup sets) now search and sort across the whole dataset rather than the loaded page, keeping large estates fast.

HYCU refinements

Building on the HYCU service introduced in 3.2:

• A HYCU service-alert source raises alerts for entity health and task failures, with clear entity names and friendly source types.
• Availability handling was improved: a clear "HYCU unavailable" message instead of raw timeouts, and greater resilience when HYCU is busy or briefly unreachable.
• Improvements to catalogue accuracy and billable-user classification.

Administration and notifications

• Feature and permission trees: a parent now shows an indeterminate half-tick when only some of its children are enabled (a full tick when all are), so a partially enabled group is clear at a glance. This is purely visual.
• Notification settings are grouped into System, Service alerts and Mia reports. Each service-alert option is shown only when you have that engine enabled, and Mia report and brief options appear only for entitled tenants.
• A session-timeout warning with a countdown and explicit stay or continue actions replaces the abrupt sign-out.