# The LI.FI Product Stack: Seven Layers, One Integration *LI.FI is not a bridge aggregator. It is a full infrastructure stack. I was writing about Layer 5 when they shipped it live. Here is every layer and what just changed.* By [Abu Olumi](https://paragraph.com/@olumi) · 2026-05-28 --- **Just Shipped  ·  May 26, 2026** [LI.FI](http://LI.FI) launched [**LI.FI**](http://LI.FI) **Intents** two days ago — a modular full-stack execution engine built on the Open Intents Framework (OIF), led by the Ethereum Foundation. This post has been updated to reflect it. When most people encounter [LI.FI](http://LI.FI), they see a swap interface or a bridge aggregator. That is the top of the stack. What sits underneath is a seven-layer architecture, each layer doing a distinct job, and together making it possible to move, swap, stake, and deploy assets across any chain in a single step. Understanding each layer is how you understand why [LI.FI](http://LI.FI) is structurally difficult to compete with. You cannot replicate one layer and call it done. ### **Layer 1: The Embeddable Widget** The Widget is the surface layer — a plug-and-play swap and bridge interface any application can embed. Works with React, Next.js, Vue, and Svelte. Fully customisable: layout, branding, wallet handling, and feature flags. Most users who interact with [LI.FI](http://LI.FI)\-powered infrastructure are using the Widget without knowing it. The infrastructure is invisible. That is by design. ### **Layer 2: The Orchestration Layer** The Orchestration Layer is the brain. It knows where assets are across every supported chain, what they cost, and what yields are available. When a request comes in, it finds the optimal route and combines multiple steps into a single transaction where possible. This is what makes one-click cross-chain actions work at scale. ### **Layer 3:** [**LI.FI**](http://LI.FI) **Composer** **Composer** goes beyond bridging and swapping. It enables programmable multi-step flows: bridge into a yield vault, stake into a protocol, chain multiple cross-chain actions — all in one transaction. Bridge → swap → stake → deposit. One confirm. Cross-chain composability at the infrastructure level, not the application level. _The_ [_LI.FI_](http://LI.FI) _Composer turns multi-step DeFi workflows into single transactions. The complexity lives at the infrastructure layer. The user sees one confirm._ ### **Layer 4: The Aggregation Layer** The most comprehensive meta-level aggregation in the market. Connects to 29+ bridges and 33+ DEXs across 60+ networks. Users get the best price without knowing which protocol executes. Wrapped token variants, non-EVM differences, canonical token mapping — handled automatically in the background. ### **Layer 5:** [**LI.FI**](http://LI.FI) **Intents  LIVE MAY 26** This is the layer that just shipped. [**LI.FI**](http://LI.FI) **Intents** is a modular, full-stack execution engine that fulfills orders through a network of professional solvers competing to provide the best execution. It is built on the reference contracts of the **Open Intents Framework (OIF)** — a public-good initiative led by the Ethereum Foundation, with contributors including [LI.FI](http://LI.FI), OpenZeppelin, Uniswap Labs, Hyperlane, and 30+ other teams. The core problem it solves: intent stacks have historically been too rigid, forcing every application into a single shared execution model. Real-world assets are a clear example — RWA flows need permissioned solvers who can market-make those tokens directly. Generic solver sets cannot fill them. [LI.FI](http://LI.FI) Intents fixes this by making the stack modular and configurable at every layer. [_LI.FI_](http://LI.FI) _Intents is the OIF in production, at scale. Over $80B in volume, 100M+ transfers, and 1000+ integrations available to OIF-compatible solvers from day one._ What makes this significant beyond the technology: it is the orderflow. A solver who integrates the OIF integrates one of the largest orderflow sources in crypto immediately. The flywheel — orderflow attracts solvers, solver competition tightens prices, better prices attract more orderflow — now starts spinning at scale for an open standard. ### **Layers 6 and 7:** [**LI.FI**](http://LI.FI)**'s Own Products** [**LI.FI**](http://LI.FI) **Pioneer** is [LI.FI](http://LI.FI)'s own solver. It guarantees execution even when third-party solvers cannot fill, and helps institutions launch and distribute tokenised assets — RWAs and stablecoins — across [LI.FI](http://LI.FI)'s network. With [LI.FI](http://LI.FI) Intents now live, Pioneer is one of the first production solvers operating on the OIF stack. [**LI.FI**](http://LI.FI) **Fly** is a DEX aggregator built specifically for new and emerging chains. Day-one best-price swaps, instant access to competitive liquidity including private market makers. ### **Why the Architecture Matters** The layered design means each component is independently useful. Together they create a full infrastructure stack from UI to execution that no single protocol can replicate by adding one feature. And with [LI.FI](http://LI.FI) Intents now live on an open standard, the stack is no longer just [LI.FI](http://LI.FI)'s to build on — it is the industry's. ![](https://storage.googleapis.com/papyrus_images/6e2edd47e19ef91134efc67504eaea4350c9160aeaa980069a8a6c48d6a6b7bc.png) Next week: Jumper's routing engine — how the consumer-facing product uses this stack to route your trades from the moment you hit swap. --- *Originally published on [Abu Olumi](https://paragraph.com/@olumi/the-lifi-product-stack-seven-layers-one-integration)*