🧠 Platform Mental Model
Understanding the platform starts with understanding the Atlas platform picture — what each part is responsible for, and how they relate to each other.
For Atlas Wiki, the Byte Capabilities lens is focused on the Atlas Commerce + Portal picture. Atlas is KFC's global front-end, built on Byte Helium as the Yum! enterprise front-end foundation. Behind it, Byte Commerce + Byte Portal power transaction handling and operational configuration, while Byte Connect sits in the middle whenever a market POS is not Byte POS.
The Atlas Platform Picture
In the Atlas context, the Byte Stack is best understood as four connected parts:
- Atlas on Byte Helium — Atlas is KFC's global front-end, and it is built on Byte Helium, Yum!'s enterprise design system and front-end foundation. Helium gives Atlas the shared UI system; Atlas skins that foundation for the KFC brand and customer journey.
- Byte Commerce — The engine behind every order. Handles cart state, pricing, tax calculation, payment processing, and POS injection. Invisible to customers, critical to everything.
- Byte Portal — The admin control plane paired with Commerce. Market and ops teams use this to configure stores, menus, promotions, taxes, payments, users, and content.
- Byte Connect — The integration middle layer when a market POS is not Byte POS. It bridges Byte Commerce to the market POS environment and matters anywhere non-Byte POS onboarding or order routing is in scope.
These parts also connect to a set of external services: Menu, Identity/SSO, PSP (payments), Loyalty/Promos Engine, Order Tracking, CMS, and Analytics.
Readers often assume Atlas or Byte Commerce can talk directly to any market POS. The intended model is narrower: Atlas -> Byte Commerce -> Byte POS by default, or Atlas -> Byte Commerce -> Byte Connect -> POS when the market is not on Byte POS.
Platform Hierarchy
This explorer combines the hierarchy and architecture views in one place. Use the tabs to switch between a side-by-side comparison, hierarchy-only, or architecture-only mode.
System Architecture Diagram
The architecture view is available in the same explorer above. Open the Architecture only tab if you want to focus just on runtime relationships and box-level explanations.
See Platform Layers for a plain-English breakdown of what each layer does and what markets can configure. Need the POS integration caveat? Read Byte Connect.