> For the complete documentation index, see [llms.txt](https://hub.moonexe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.moonexe.com/roadmap.md).

# Roadmap

What we built in 2026 and where we are heading in 2027.

![](https://1494590963-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fum22DENTNDd9fygCCV9w%2Fuploads%2F09j2FpzBMpEq9JsY1sn8%2Fmoonexe-roadmap.png?alt=media)

## 2026: Build the engine

**2026 built the engine. Q4 turns it on.** The foundation is in place, partnerships have moved forward, and launch preparations are under way.

| Quarter | Stage     | Status         | Milestones                                                                                                    |
| ------- | --------- | -------------- | ------------------------------------------------------------------------------------------------------------- |
| Q1      | Ignition  | ✅ Delivered    | Set up the TRX lounge and management structure; connected to liquidity providers.                             |
| Q2      | Alliance  | ✅ Advanced     | Moved the Huobi Labuan partnership forward; aligned plans for shared resources, data and a payment gateway.   |
| Q3      | Elevation | 🔄 In progress | Upgrade the member portal; expand in TRX and Vietnam; build media; activate Malaysia Blockchain Week.         |
| Q4      | Liftoff   | ⏭ Next         | Deliver the December launch; get eligible members using the card; pilot compliant USDT–fiat counter services. |

**2026 outcome:** a complete operating platform that is connected, visible and ready to grow.

{% hint style="warning" %}
Card and counter milestones depend on readiness of the partner programme and regulatory approval.
{% endhint %}

## 2027: Go borderless

**Infrastructure becomes reach. Reach becomes a movement.** The app, the card and the partner network start working together as one ecosystem.

| Quarter | Milestones                                                                                   |
| ------- | -------------------------------------------------------------------------------------------- |
| Q1      | Onboard SERA; introduce cardholder benefits; launch the MoonExe iOS app.                     |
| Q2      | Enter priority markets in the Middle East and Europe through licensed local partners.        |
| Q3      | Pilot virtual-account and digital-banking services with Huobi Labuan before a wider rollout. |
| Q4      | Celebrate year one; grow towards 1M registered users; deepen strategic alliances.            |

**One app. One card. One global network.**

*The moon was never the destination. It was the launchpad.*

{% hint style="warning" %}
Targets for expansion and regulated products depend on approvals from partners, commercial terms and regulators.
{% endhint %}

## Events 2026

* Malaysia Blockchain Week
* Global Dinner
* Vietnam Business Forum
* Malaysia Business Forum


---

# 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://hub.moonexe.com/roadmap.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.