HomeNote: Major overhaul underwayOverviewFramework adaptersDeployment adaptersThe FAB format
Knowledge Base

fab logo wide

Join discussion on Discord

See current version of the docs at https://fab-docs--production--next.branch.linc-preview.sh/, or join the discussion on Discord

FAB Specification

💎 FABs are a compile target for frontend applications.

They unify static sites, single page applications (SPAs) as well as server-rendered JavaScript UIs in one bundle format, allowing instant deployment to a wide range of hosting platforms. Its goal is to do for frontend applications what Docker has done for infrastructure—a standard for interoperable tooling.


Note: Major overhaul underway

The FAB tooling is being rebuilt in preparation for a v1 release. See the next branch for latest progress.


FAB Diagram

👉 Read more about the FAB Structure.

Framework adapters

Note: for now, you probably want to get started with @fab/static. It's a zero-config compiler for static sites with hooks to add as much server-side logic as most apps need.

Working with one of these projects? Read the following

Thinking of writing your own adapter? Head to @fab/compile to understand the low-level compilation API. Then get in touch, we're happy to help!

Deployment adapters

💎 FABs are portable. That is, once they're compiled, they can be deployed to any number of

Thinking of writing your own deployment adapter? Read on to understand the runtime requirements of FABs, then check @fab/serve for some sample code.

The FAB format

What is a Frontend Application?

The term Frontend Application encompasses a wide range of modern web projects, from purely static sites with no client-side JS, to entirely client-rendered apps hitting an API, or those with a significant server-side-rendering component. But they are defined in opposition to a more traditional "backend" application, which may emit HTML across the wire as well, but usually has a persistent server, with direct connections to databases and a local filesystem.

This is synonymous with some of the more common web app development methodologies in the React/Angular/Vue/Ember ecosystems—a self-contained single-page-app, potentially pre-rendered or server-rendered, talking to a separate backend app or collection of services via HTTP.

Why a new bundle format?

The Frontend Application Bundle is designed to fill a gap between existing options for frontend application deployment and hosting environments. Usually, you have a choice between a static site host, which prevents you from having any active server-side components, or a more traditional web app host designed for hosting backends.

And while deploying frontend apps to backend-centric hosts works reasonably well, it misses a crucial aspect of frontend web development—iteration speed. UI development benefits greatly from rapid prototyping and feedback, and since frontend apps, having no direct dependencies on databases or filesystems, can be cloned & deployed freely, backend-centric workflows can feel overly constrained.

As such, static site hosting has grown in popularity among the frontend application community, and static site generators along with them. But there are many reasons why it's preferable or even essential to include a server-side component in your application, which these projects can't take advantage of without fundamentally changing how they build & deliver their app.

Frontend Application Bundles are the container format that work equally well for fully-static through to full server-rendered frontend apps, making your choice of technology independent from your choice of hosting.