Denovers completely revamped our SaaS application by introducing a new stunning UI, enhancing the overall product experience. A strategic approach to UX design ensured holistic improvements, through which Denovers was able to provide value to the product.
Dizzion had a powerful enterprise DaaS platform, and the product worked — but the interface had been outpaced by the platform’s complexity. The dashboard was a flat list where every data center looked equal. Deep records opened inside overlays instead of dedicated pages. Long workflows exposed raw configuration fields, and finance and support felt like separate tools. The product needed a design system strong enough to carry 100+ screens across light and dark themes. This is what the platform looked like when the engagement began.
Dizzion runs Desktop-as-a-Service infrastructure for regulated enterprise teams across BPO, financial services, healthcare, insurance, and contact centers.
Their platform, Cosmos Control Center, was already live and already important to daily operations. This was not a redesign sandbox. Real customers were using C3, so every design decision had to respect existing workflows, engineering constraints, and operational complexity.
Dizzion first gave Denovers one critical surface: the Data Center dashboard. It was the first screen many users landed on, and one of the places where the product’s complexity became visible. We redesigned it from a flat scrolling list into a command-center experience with a world map, status-coded data center pins, scope filters, list/map toggle, capacity indicators, and direct drill-down paths. That trial proved the direction.
The engagement expanded into a full-platform redesign across 100+ screens. Before redrawing everything, we built the system underneath: tokens, tables, filters, breadcrumbs, tabs, charts, status pills, forms, steppers, modals, and page shells. From there, we rebuilt the product module by module. Every major entity got its own URL. Modals became tabbed deep-dives. Raw configuration became structured wizards. Finance and support started feeling like part of the same product. And the entire platform worked across both light and dark themes.
The C3 dashboard is where operators and customers land first. Previously, it behaved like a flat scrolling stack of identical cards — users had to work too hard to understand which data centers were healthy, which needed attention, and where to go next. We redesigned it around geography and operational scanning: a world map of data centers, status-coded pins, Data Center Type / Location / POD / Health filters, a List/Map toggle, and inline detail cards with capacity, KPIs, service status, and drill-down links. This trial-phase deliverable became the proof point that opened the full redesign.
Below the dashboard, C3 is a hierarchy: Data Center → POD → Customer → Resource Pool. The old experience buried important records inside overlays and disconnected views, so users could reach information but rarely had a strong sense of place. We rebuilt the hierarchy into breadcrumb-driven detail pages — each major entity with its own URL, KPI header, tabs, charts, and status indicators. The Data Center page leads with capacity, service status, and tabs for Summary, PODs, VLANs, Network IPs, and Monitor. POD Management gets its own capacity dashboard. Customer Resource Pool goes deeper with CPU, RAM, DISK, virtual desktops, segments, integrations, and resource-adjustment patterns.
Customer onboarding was one of the heaviest workflows inside C3. The old flow exposed too much raw technical configuration directly in the operator UI — the complexity was necessary, but the interface didn’t need to make it feel heavier. We rebuilt Customer Build as a structured wizard moving through clear stages: PREP → Build → Integrate → App, with nested sub-wizards for technical setup (VPN Name, VPN Details, IKE Phase 1, IKE Phase 2, and Active Directory). The same wizard pattern then extended into Provisioning Requests, Tasks, and Scheduled Maintenance.
Finance and support previously felt like separate apps inside the same platform. Contracts, billing, customer views, service requests, ticket details, attachments, and conversations all needed to feel connected to the rest of C3. We rebuilt these modules on the same component family as the infrastructure views. Finance received Contract View and Customer View tabs, expandable rows, saved filters, status pills, and clearer customer-level contract visibility. Support received breadcrumb-driven ticket pages, structured metadata panels, conversation threads, and attachment grids. Two different jobs. One product language.
None of these surfaces were designed as one-off screens. The dashboard, drill-down pages, customer build flows, finance, support, maintenance, tables, filters, wizards, charts, modals, and status states were all assembled from a component-based design system built from scratch: tokens, typography, colors, tables, forms, breadcrumbs, tabs, filters, steppers, modals, status pills, charts, cards, and page shells. The same primitives rendered both light and dark themes without forking the product experience. That is what kept 100+ screens consistent.
Dizzion came to Denovers with a SaaS product that worked, but an interface that no longer matched the maturity of the platform. We helped turn Cosmos Control Center into a modern enterprise control center for Desktop-as-a-Service operations. The final outcome included 100+ production screens, a design system built from scratch, dual light and dark themes, a dashboard command center, breadcrumb-driven record pages, tabbed deep-dives, a structured customer build wizard, finance and support modules, and reusable tables, filters, charts, forms, and status patterns.
Dizzion did not just get a new UI. They got a scalable product foundation for a complex enterprise SaaS platform.
