> For the complete documentation index, see [llms.txt](https://terminus-1.gitbook.io/terminus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://terminus-1.gitbook.io/terminus-docs/governance-and-execution/roadmap.md).

# Roadmap

The Terminus roadmap is structured around three phases: validating product-market fit, scaling the ecosystem across Southeast Asia, and evolving into a more open payment network with stronger governance and infrastructure reach.

## 2026: Product Validation and Market Density

The primary objective of 2026 is to deepen proof in live markets and strengthen the repeatability of the payment model.

Key priorities:

* strengthen operations in Thailand and Vietnam,
* increase daily transaction activity and user retention,
* expand merchant-side coverage in high-frequency scenarios,
* improve routing, reconciliation, and risk systems,
* and prepare the launch framework for `TMNS`.

This is the year in which Terminus moves from validation to density.

Expected milestone direction:

* clearer transaction growth benchmarks,
* stronger repeat usage behavior,
* more merchant category depth,
* and a market-ready framework for `TMNS` activation.

## 2027: Regional Expansion and Ecosystem Scaling

The objective of 2027 is to turn validated product logic into regional growth.

Key priorities:

* enter additional Southeast Asian markets,
* add more partner channels and ecosystem integrations,
* activate `TMNS` as a live growth coordination layer,
* expand the role of the Terminus Payment Association,
* and increase network-level distribution through partner ecosystems.

This is the year in which Terminus begins to look less like a country-by-country product and more like an expanding regional network.

Expected milestone direction:

* first wave of multi-market operating confidence,
* stronger partner-led distribution,
* live token-powered incentive programs,
* and a visible ecosystem footprint beyond the initial launch markets.

## 2028: Open Network and Protocol Evolution

The objective of 2028 is to deepen the infrastructure nature of the network and open the path toward broader ecosystem participation.

Key priorities:

* introduce more open infrastructure interfaces,
* expand governance participation,
* increase network composability for external partners,
* strengthen regional treasury and ecosystem programs,
* and explore strategic protocol evolution opportunities, including future `x402`-aligned directions where relevant.

This is the phase in which Terminus begins to resemble a shared payment layer rather than a single product surface.

Expected milestone direction:

* a more open infrastructure posture,
* broader ecosystem participation in governance,
* stronger treasury-backed ecosystem programs,
* and a clearer transition from product network to regional payment layer.

## Milestone Table

| Year | Strategic Theme        | Primary Outcome                                          |
| ---- | ---------------------- | -------------------------------------------------------- |
| 2026 | Validation and density | prove repeatable payment behavior in live markets        |
| 2027 | regional scaling       | expand markets, partners, and tokenized growth loops     |
| 2028 | open network evolution | deepen infrastructure reach and governance participation |

```mermaid
timeline
    title Terminus Roadmap
    2026 : Validate Thailand and Vietnam
         : Increase daily transaction density
         : Improve settlement and risk systems
         : Prepare TMNS launch framework
    2027 : Expand across additional SEA markets
         : Scale ecosystem integrations
         : Activate TMNS incentives
         : Grow the Payment Association
    2028 : Open network interfaces
         : Expand governance participation
         : Strengthen ecosystem treasury programs
         : Explore protocol-layer evolution
```

The roadmap is not merely a set of dates. It is a sequence in which product execution, network growth, token coordination, and governance evolution reinforce one another.


---

# 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://terminus-1.gitbook.io/terminus-docs/governance-and-execution/roadmap.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.