> For the complete documentation index, see [llms.txt](https://docs.blocksquare.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocksquare.io/certified-partners/pricing.md).

# Pricing

Use of the infrastructure is subject to a software license, while “pay per use” and/or “recurring fee” charges are complementary and applicable based on actual software usage. All quoted prices exclude VAT.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>1 - Software license</strong></td><td>A software license grants partners lifetime access to the tokenization system. <br><br>✅ Monthly plans available.</td><td><a href="/certified-partners/pricing/software-license.md">Software license</a></td></tr><tr><td></td><td><strong>2 - Pay per use</strong></td><td>After that we charge for each tokenization and primary offering.<br><br>✅ No hidden fees.</td><td><a href="/certified-partners/pricing/pay-as-you-grow.md">Pay as you grow</a></td></tr><tr><td></td><td><strong>3 - Post-offering</strong></td><td>Charged per property and only for properties where tokens have been issued.<br><br>✅ Fixed maintenance.</td><td><a href="https://docs.blocksquare.io/certified-partners/pricing/pay-as-you-grow#2.-post-offering-management">https://docs.blocksquare.io/certified-partners/pricing/pay-as-you-grow#2.-post-offering-management</a></td></tr></tbody></table>

### **Example:**

1. Partner/client selects [a monthly plan](/certified-partners/pricing/software-license.md#option-2-monthly-plans) OR the [one-time license fee](/certified-partners/pricing/software-license.md#option-1-one-time-payment)
2. After that [each tokenization](https://docs.blocksquare.io/certified-partners/pages/IPUdgNu5M9IKdSIROeKX#1.-asset-tokenization) and primary offering cost 5,990 USD
3. For each tokenized asset, 69 USD / month is charged for [maintenance](https://docs.blocksquare.io/certified-partners/pages/IPUdgNu5M9IKdSIROeKX#2.-post-offering-management)

{% hint style="success" %}
Please see below subpages to learn more about our pricing model.
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>Transaction fees</strong></td><td>See system integrated fees based on transaction types.</td><td><a href="/certified-partners/pricing/transaction-fees.md">Transaction fees</a></td></tr><tr><td></td><td><strong>Partner program &#x26; discounts</strong></td><td>Discounts for partners who purchase and stake BST.</td><td><a href="/certified-partners/pricing/discounts.md">Discounts</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blocksquare.io/certified-partners/pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.