> For the complete documentation index, see [llms.txt](https://pool-party-xyz.gitbook.io/pool-party-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/get-started/what-is-pool-party.md).

# What is Pool Party

Pool Party is an on-chain platform for collective asset management. A manager designs a multi-asset allocation strategy and deploys it as a pool. Anyone can co-invest in that pool while keeping full self-custody of their assets, and every holding and allocation is verifiable on-chain.

## What makes it different

* **Self-custody.** You keep control of your assets at all times. You are never handing them to a manager or to Pool Party.
* **On-chain transparency.** A pool's holdings, allocations, and fees are recorded on-chain and can be verified by anyone.
* **Open and multi-asset.** Pools reach many asset types (tokens, fixed income, real-world assets, and more) through a standardized adapter layer.

## The idea

The structure of a family office, professional, multi-asset, actively managed allocation, should not be reserved for a few. Pool Party makes that structure open, transparent, and self-custodial.

{% hint style="info" %}
**What Pool Party is not.** Pool Party is non-custodial software for collective asset management. It is not a fund, and it is not an intermediary that holds your assets.
{% endhint %}

Participating in a pool carries risk, including the potential loss of your entire deposit. The historical performance of a pool or a manager does not indicate future results. Nothing in this documentation is financial, legal, or tax advice.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><h4><i class="fa-rocket-launch" style="color:$primary;">:rocket-launch:</i></h4></td><td><strong>Quickstart</strong></td><td>Go from sign-up to your first deploy in under five minutes.</td></tr><tr><td><h4><i class="fa-compass" style="color:$primary;">:compass:</i></h4></td><td><strong>Your first project</strong></td><td>A guided walkthrough that takes you from an empty workspace to a configured, deployed project.</td></tr></tbody></table>

***

***

***

## What you'll need

Before you start, make sure you have:

* [x] An account on the platform (free plans work fine)
* [x] A repository or local project you'd like to deploy
* [x] A few minutes of uninterrupted time

{% hint style="info" %}
If you're evaluating the platform for your team rather than yourself, jump to [Core concepts](/pool-party-docs/pool-party-v2-docs/core-concepts/allocation-pools.md) first — it'll save time when you set things up properly.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/get-started/what-is-pool-party.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.