# About Planck

**About Planck**

Planck is a decentralized infrastructure network purpose-built for the future of AI, compute, and decentralized physical infrastructure (DePIN). At its core, Planck enables developers and enterprises to launch their own AI-native chains, deploy GPU-powered workloads, and build applications that require trustless, composable, and sovereign infrastructure.

Planck’s architecture is designed around two core layers:

* **Planck₀** is a modular Layer-0 protocol that provides shared security, interoperability, and tooling for launching scalable, sovereign Layer-1s and DePIN protocols.
* **Planck₁** is a compute-centric Layer-1 blockchain that integrates bare-metal GPU compute and smart contract primitives designed for AI, enabling on-chain scheduling, compute payments, and real-world model deployment.

This dual-layer approach allows Planck to operate as both the coordination layer and the execution layer of a decentralized AI economy. Combined with GPU Console and AI Studio, Planck serves as a unified stack where AI research, development, and deployment converge on-chain.

Planck is built by a world-class team with deep experience in cloud, AI, and blockchain, and is backed by leading investors and ecosystem partners. It is already live with over $60 million in GPU hardware deployed across high-performance data centers, offering a cost-effective, enterprise-grade alternative to centralized cloud infrastructure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.plancknetwork.com/learn-more/white-paper/about-planck.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
