> 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/help/zkcross-faqs.md).

# zkCross FAQs

### Is zkCross a bridge?

No. zkCross is broader than a bridge. It is an execution infrastructure layer that includes routing, signing, deterministic enforcement, settlement verification and monitoring across multiple blockchain environments.

### Is zkCross custodial?

No. zkCross is built around a vault-based custody model where the vault remains the execution boundary. The infrastructure is designed to preserve non-custodial operation.

### Does zkCross rely on third-party bridges and routers as core infrastructure?

The goal of zkCross is to control the critical execution path internally rather than depend on third-party vendors as the primary infrastructure layer.

### What makes zkCross suitable for AI-driven applications?

AI systems can propose actions, but zkCross provides the control, signing, routing and verification framework that keeps those actions bounded and enforceable.

### Has zkCross been used in production?

Yes. zkCross has operated across multiple ecosystems and has already processed substantial on-chain volume and transaction count in live market conditions.

### What is Surf’s relationship to zkCross?

Surf is a consumer-facing product built on top of zkCross infrastructure. It uses the same vault, control, routing, signing and settlement foundation.