<!-- Canonical: https://docs.linea.build/stack/how-it-works -->

> For the complete Linea documentation index, see [llms.txt](/llms.txt).
> Agents can fetch this page as Markdown at [https://docs.linea.build/stack/how-it-works.md](https://docs.linea.build/stack/how-it-works.md).

# How it works

This section introduces how Lineth (formerly the Linea Stack) works from an operator's perspective. It surfaces the architecture, deployment models, and component boundaries you need to understand to run a network effectively.

## Architecture

As an Ethereum-equivalent network, Lineth uses a dual-layer architecture separating consensus from execution. This design enables modular deployment, client diversity, and operational flexibility.

-   Understand the core [components](/stack/how-it-works/core-components) that make up the stack
-   Learn more about the [protocol architecture](/protocol/architecture)

## Deployment models

Lineth allows operators to tweak the deployment model according to their business case, for example, a network built on Lineth can be operated as:

-   Private Validium: Offchain data availability, ideal for regulated financial applications
-   Public: Fully public network with onchain data availability

See more on the [deployment options](/stack/how-it-works/deployment-models).

## Data availability and finalization

For details on L2/L3 relationships, smart contract requirements, and how data availability differs by deployment model, see [data availability and finalization](/stack/how-it-works/data-availability-finalization).

important

Understanding data availability and finalization is key to good deployment decisions.
