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

# Roadmap

What is planned for the Bloxchain Platform next. Planned items are not documented in detail until they ship, and this page does not give dates. What the Platform can do today is documented in the [Platform guide](/platform-guide/platform.md).

**Alpha · Local-first.** Official deployments are live on the 15 supported networks. Your inventory is stored on your device unless you join an organization.

## Coming later

| Item                                       | What to expect                                                                                                                                                                        |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Applying capabilities from Marketplace** | The **Apply** buttons on the Bloxchain Account product page become active, so a Vault can pick up the Personal security, Treasury or Asset issuance capability from the product page. |
| **Preset wiring**                          | A preset chosen on Discover configures the matching roles and actions at deploy, instead of landing as a plain Vault.                                                                 |
| **Payments preset**                        | Listed on Discover as "Coming later".                                                                                                                                                 |
| **Open sign-in**                           | Signing in without early access, so the waitlist is no longer the way in. Sign-in itself works today for early-access accounts.                                                       |
| **Organizations self-serve**               | Smoother creation, checkout and member management for Pro and Team.                                                                                                                   |
| **Broader relay**                          | Wider availability of the optional Bloxchain broadcaster for submitting signed transactions. Today it is offered per environment.                                                     |
| **Platform API and other services**        | Programmatic access to Platform features and additional hosted services. Not yet specified publicly.                                                                                  |

{% hint style="info" %}
Plans change. Nothing here is a commitment, and features may appear behind the alpha badge before they are documented.
{% endhint %}

## Open source

The Protocol and SDK ship independently of the Platform. Track them on [GitHub releases](https://github.com/PracticalParticle/Bloxchain-Protocol/releases) and see [Releases and compatibility](/resources/releases.md) for the versions this documentation describes.

## Related

* [Releases and changelog](/resources/releases.md#changelog)
* [Limits and defaults](/resources/limits-and-defaults.md)
* [Known limitations](/security/audit-status/known-limitations.md)
* [FAQ](/resources/faq.md)


---

# 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.bloxchain.app/resources/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.