> For the complete documentation index, see [llms.txt](https://liquid-finance-1.gitbook.io/liquid-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liquid-finance-1.gitbook.io/liquid-finance/for-developers/architecture-summary.md).

# Architecture Summary

In summary, when a developer or an integration partner interacts with **Liquid**, they’re leveraging a **robust microservice-like architecture**:

* **Front-end Interface (Bot or Web):**\
  Collects user inputs.
* **Backend (Node.js + Supabase):**\
  Orchestrates workflows, maintains user and asset states.
* **Third-Party Services:**\
  KYC (Civic/Sumsub) and Documint for specialized verifications and legal document generation.
* **Blockchain (Solana):**\
  Issuance of asset tokens and recording of immutable transaction records.
* **Decentralized Storage (IPFS/Arweave):**\
  Storage of off-chain asset data linked securely to on-chain tokens.

This modular design allows **each component to be improved or scaled independently**.\
For instance, Liquid can **swap or add KYC providers per region**, **upgrade its storage backend**, or even **migrate from Solana to LiquidChain** in the future — all **without overhauling the entire system**, thanks to **consistent interfaces between components**.