# Portal vs VaultPortal

## Overview

The `Portal` is the entry point of the Flap bonding curve protocol. It launches standard tokens and tax tokens and wires them to the bonding curve lifecycle. For each tax token launched, if the "funds recipient wallet" percentage is set to non-zero, a portion or all tax revenue is sent to that wallet. And when that wallet is a smart contract and implements Vault interface, it is called a `Vault`.

The `VaultPortal` builds on top of the `Portal` to add Vault functionality for tax tokens. It launches a tax token and sets up a Vault in one flow.

For Vault concepts and behavior, see [developers/vault-developers/flap-tax-vault.md](/flap/developers/vault-developers/flap-tax-vault.md).

## When to use which

* Use `Portal` when you only need to launch a standard token or a tax token without Vault features or your custom Vault implementation.
* Use `VaultPortal` when you want Vault-backed tax tokens and using a vault factory. (You can use any Vault Factory, this is permissionless.)

## Relationship diagram

![Vault vs VaultPortal relationship](/files/Votv94P9JAYdTWniksf2)


---

# 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://docs.flap.sh/flap/developers/basic-and-mechanism/portal-vs-vaultportal.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.