What belongs in the frontend now

Most architectural discussions fixate on the backend, and for good reason: it is complex, business-critical, and hard to change. But the frontend has grown into a substantial engineering surface of its own, and when it is treated as an afterthought, the supporting infrastructure tends to sprawl into unmanageable technical debt.

As decoupled architecture becomes the norm, teams are shifting that overhead to what is known as the Frontend Cloud. The idea is to stop provisioning and operating infrastructure separately from development. Instead, the platform reads your application code and, from that, provides the global infrastructure the app needs. In practical terms, this looks like deploying a dynamic site without manually standing up servers, tuning CDNs, or wiring observability.

That automation is what separates the Frontend Cloud from a conventional hosting setup. The backend cloud typically resembles a cost center: raw compute, storage, and networking that must be assembled and paid for regardless of usage patterns. The Frontend Cloud behaves more like a profit center, since it directly serves the customer-facing experiences that drive revenue and engagement.

This is the first installment in a series on why moving to the Frontend Cloud can be the final infrastructure transformation an organization needs. Later pieces will cover edge-delivered performance and personalization, developer experience and iteration speed, then reliability and security at scale.

Defining the modern frontend

In the Frontend Cloud model, frontend means far more than pixels in a browser. It refers to every component that communicates directly with external clients, whether those clients are humans or other machines. That definition stretches well beyond the UI layer to include:

  • End-user and internal application interfaces
  • Code executing on a user's device
  • APIs that respond to external clients
  • Reverse proxies facing users, such as CDNs and ingress firewalls
  • Servers handling user requests for server-side rendering or asset delivery
  • Supporting services like image optimization, which sit behind those layers but exist entirely for frontend concerns

Under that lens, the frontend encompasses a far larger slice of infrastructure than most teams assume. The boundaries between a UI and a backend service blur in practice, but the operational consequences are clear: frontend infrastructure is no longer a thin layer bolted onto a backend architecture. It is a distributed system in its own right, with its own requirements for scale, performance, and security.

That growing scope is precisely what the Frontend Cloud is meant to absorb. The platform handles the global distribution, caching, rendering, and serving logic that used to demand dedicated infrastructure teams, letting application code itself define the infrastructure through framework-defined principles and serverless execution.