Jump to content

Draft:Frontend management platform

From Wikipedia, the free encyclopedia
  • Comment: AI submissions can't be accepted. ChrysGalley (talk) 11:33, 4 June 2026 (UTC)

A frontend management platform (FMP) is a category of cloud-based software used to build, manage, and deliver the frontend (user interface) layer of websites and applications that are built on API-first or headless architectures. Frontend management platforms connect multiple backend systems, such as e-commerce platforms, content management systems (CMS), enterprise resource planning (ERP), and customer relationship management (CRM) systems through APIs and provide a unified layer for composing, governing, and deploying user interfaces across channels and devices.[1]

Background

[edit]

In traditional, monolithic web architectures, the presentation layer is part of the same system that manages content and business logic, as in a classic CMS or e-commerce suite.[citation needed] From the 2010s onward, vendors increasingly decoupled the presentation layer from backend systems ("decoupled" or "headless" architectures), exposing content and commerce functions through APIs instead of rendering pages themselves.[citation needed] This approach later became associated with composable commerce, in which commerce capabilities such as product catalog, checkout, search, and payments are selected as independent, API-connected components and assembled into a custom stack.[2]

Because headless backends do not provide a user interface, organizations adopting these architectures must either build and operate a custom frontend in-house or use specialized tooling. Frontend management platforms emerged as one such tooling category, alongside related offerings marketed as "frontend as a service" (FaaS) and "frontend cloud".[1][3]

Characteristics

[edit]

Frontend management platforms typically combine several functions:[1]

  • Backend orchestration - connecting and aggregating multiple data sources (commerce, CMS, ERP, CRM, search, or machine-learning APIs) behind a single frontend layer.
  • Component and design governance - managing reusable UI components, layouts, and design tokens so that interfaces remain consistent across channels.
  • Editorial tooling - visual editors and preview functions that allow non-developers, such as marketing or product teams, to compose and modify pages without code changes.
  • Multi-channel delivery - rendering interfaces for web browsers, mobile devices, point-of-sale displays, and other digital touchpoints, often with automated deployment and edge delivery.

See also

[edit]

References

[edit]
  1. 1 2 3 "Compare Frontend Management Platforms". OMR Reviews. Retrieved 4 June 2026.
  2. ↑ "Composable Commerce in 2026 (Redefine Your Tech Stack)". BigCommerce. Retrieved 4 June 2026.
  3. ↑ "Composable Frontend: Composable Commerce Explained". Netguru. Retrieved 4 June 2026.