Illustration: a kit of shared interface parts, outlined in blue, feeds a citizen account card connected to six public-service tiles.

Key figures

registered users across the citizen-service ecosystem
15M+
services delivered through eGov.kz, by public reporting
508M+

One foundation, many services

  1. Interface primitives

    • Shared components
    • Accessibility built in
    • Consistent data display

  2. Citizen account

    • Personal account
    • Data-access surfaces

  3. Public services

    • Built on the same foundation

  4. Citizens

    • One account for many services
Kuan built the shared interface layer that the account surfaces and services use. Kuan’s part

Operating problem

A national e-government personal account surface needed durable interface foundations for citizen-facing data and service workflows.

What changed

A shared set of frontend primitives established consistent account and data-access behavior across public services.

System scope

  • Frontend design foundation and interface primitives
  • Citizen account and data-access surfaces
  • High-traffic public-service usability constraints
  • Durable implementation for long-lived government services

Technical constraints

  • Create reusable interface primitives for citizen account and public-service workflows rather than one-off pages.
  • Support accessibility, high traffic, and long service lives in a national public-system context.
  • Keep the frontend foundation coherent as many services and data surfaces accumulated around it.

Evidence

15M+ registered users reported across the citizen-service ecosystem.
508M+ services delivered through eGov.kz, according to public reporting.

Need a delivery partner for your software project?

Share the market, constraint, current state, and budget reality in writing. If it looks like a fit, you will get a human response with the next step.

Start a project
Next case study Perko A multi-tenant operating system for independent local businesses.