> For the complete documentation index, see [llms.txt](https://zkcross-network-1.gitbook.io/learn.zkcross.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkcross-network-1.gitbook.io/learn.zkcross.network/ecosystem-validation/why-surfliquid-exists-on-zkcross.md).

# Why SurfLiquid Exists on zkCross

[SurfLiquid](https://www.surfliquid.com/) is not separate from zkCross Network. It is a consumer deployment of the zkCross execution stack.

<figure><img src="https://2970403064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwOUbJmiTegGBEv1M988A%2Fuploads%2FtbfgNaAUZcSNuE2brsB6%2FSurf%20built%20on%20zkCross%20stack.png?alt=media&amp;token=ab7ca633-e3e0-4ac2-8ad2-91745cd5f63f" alt=""><figcaption></figcaption></figure>

That distinction matters because it explains why Surf can make strong claims around custody, deterministic control, cross-chain execution and safety.

Surf uses:

* zkCross vault custody
* zkCross Guardian enforcement
* zkCross routing and chain abstraction
* zkCross signing architecture
* zkCross settlement verification and reconciliation

This means Surf does not depend on outsourced control surfaces for core execution. It inherits infrastructure that was already built and tested before the consumer product layer existed.

For zkCross, Surf is important as a proof of infrastructure productisation. For readers of the zkCross docs, Surf should be positioned as the first visible product expression of the rails, not as the entirety of the company.

***