# TMS pricing

TMS fees are charged **onchain** to **end users**, directly in the **chain’s native gas token** (e.g. ETH, BNB, etc.).

When a user:

* **Claims** tokens from your Vesting & Claim Portal, or
* **Interacts with staking** (e.g. stake/unstake, claim rewards),

the transaction includes:

1. The normal **network gas fee** (paid to validators).
2. A small **TMS protocol fee**, also in the native token.

These are bundled into the **same transaction** — users don’t sign multiple popups for separate payments.

From the user’s perspective, they see:

* “You are paying:
  * Gas: X \[native token]
  * Fee: Y \[native token] (protocol / platform fee)”

Exact UI wording depends on your wallet and integration, but economically it’s a **small, fixed-style fee** attached to the onchain interaction.

***

### What projects (founders) pay

Under this model, **founders pay very little by default**.

You **do not** pay:

* A percentage fee on your token flows (no platform 0.1% rake on vesting/claims).
* Large “standard” setup fees for every project.
* Automatic recurring maintenance/hosting fees baked into normal usage.

You **do** pay:

* **Gas fees** from your Admin/Manager wallet when:
  * Deploying and configuring contracts (vesting, staking, locks).
  * Performing admin actions that touch the chain.

Any **optional** commercial arrangements (e.g. enterprise support, custom integrations) are handled on a **case-by-case** basis and are **not** part of standard TMS usage.

***

### What end users pay

When a user interacts with your TMS-powered portal, they pay:

1. **Network gas fee**
   * Standard cost to perform an onchain transaction on the chosen network.
   * Goes to the network, not to TMS or your project.
2. **TMS protocol fee** (included in the transaction)
   * A small fee in the native gas token.
   * Charged on **claim** and relevant **staking** transactions.
   * Collected by Decubate/TMS as revenue to run and improve the infrastructure.

Because this fee is fixed/low compared to token values and claim sizes, it:

* Keeps UX predictable.
* Scales with actual **usage** (more real users → more transactions → more fees).
* Avoids punishing projects that route high-value flows through TMS.

***

### Why we use this model

We call this an **experimental, user-paid infrastructure model**.

It allows us to:

* **Support more founders**
  * You don’t need a big budget just to start using professional token infrastructure.
  * Early-stage projects can launch vesting/staking with minimal upfront cost.
* **Reduce setup & maintenance fees**
  * Instead of invoicing every project for setup and hosting, we fund operations from the small protocol fees built into claim/stake transactions.
* **Align incentives with real usage**
  * If your portal is heavily used, our revenue scales with that usage.
  * If you’re early and usage is low, you’re not stuck with big fixed bills.

It’s closer to how cloud infra works: you pay as the product is actually used, not for the *theoretical* value of your token supply.

***

### How to communicate this to your users

Most of your users are already used to paying **network gas**.\
The only extra concept is the **TMS protocol fee**.

In your own docs / FAQ, we recommend something like:

> “Claims and staking actions on our official portal include a small protocol fee (on top of normal gas), charged in the network’s native token.\
> This fee helps cover the infrastructure that powers our vesting and staking, and is handled automatically in the same transaction.”

Key points:

* The fee is **small and fixed-style**, not a % of their claim.
* It’s **bundled** with their transaction — no second pop-up, no weird extra steps.
* It funds the infra that keeps their claim/stake experience reliable and secure.

***

### FAQ (short)

**Do we as a project pay any platform percentage fee on our token flows?**\
No. The standard TMS model does **not** take a % cut of your vesting/staking flows.

**Do we have to pay large setup or maintenance fees?**\
As of 2026, we're onboarding up to 50 clients without setup fees to experiment with the new business model. Decubate reserves the right to change this at any moment. 

**Who pays the TMS fee?**\
End users pay a small fee in the chain’s native token when they claim/stake. It’s included in their transaction.

**Can we “turn off” the protocol fee?**\
No. The protocol fee is how we make TMS sustainable without charging you large upfront and recurring fees.


---

# 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://tms-finance.gitbook.io/tms.finance/general/tms-pricing.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.