User interfaces
The current interface, legacy SPA and internal portal serve different parts of the service.
Energy, broadband and mobile plans in one comparison platform.
Youtility connects household requirements with supplier offers. The platform combines guided energy-switching forms, broadband and mobile comparisons, supplier integrations and background data updates.
The journey identifies the supply address, energy service, current provider, tariff and payment method. Usage can come from a bill or a household estimate, so the form does not depend on one type of record.

The form distinguishes gas, electricity and dual-fuel supply, then asks about prepayment and Economy 7 meters. These inputs establish the conditions for the energy comparison.

Customers can use their bill amount, consumption in kWh or an estimate. The comparison therefore supports both households with exact records and those without a recent bill.

Low, medium and high usage options are explained through household size. The estimate supplies a starting value when the customer cannot provide measured consumption.
After selecting a plan, the customer provides contact and identity details, address history, employment and residential status. Separate steps cover smart-meter acknowledgement, billing preferences and Direct Debit setup.
Postcode, address and current provider frame the search. The results expose both service characteristics and the charges that change during the contract.
The catalogue includes network and seller information for each offer, with sorting and filters for device specifications.
Comparison journeys and supplier data run across more than 15 containerised microservices.
The current interface, legacy SPA and internal portal serve different parts of the service.
APIs, shared packages and scheduled workers support supplier synchronisation and exports.
Relational, document and geospatial stores support the service, with shared caches and reporting.
Messaging, APIs and file exchange connect supplier data and communication.
Identity moved from IdentityServer4 to Entra ID; workload identity and rate limits support service access.
GitOps manages Kubernetes releases, while infrastructure code defines separate environments.
Application diagnostics, API checks and performance tests support operation and delivery.
Start with one service: its supplier feeds, customer questions, price components and application steps. We can define the comparison logic, data updates and handover to the selected provider.
Discuss your comparison platform