In brief: Client Vault’s roadmap is public and community-driven. You can follow each project by status — proposed, under review, planned, delivered — and submit your own ideas directly from the roadmap. I don’t promise to deliver everything: I select and build what is truly useful to the majority.
We don’t develop in isolation. Client Vault’s roadmap is an open workshop — and above all, a shared one: you see the actual progress of each project, and you can submit your ideas. The plugin’s best features come from there. Here’s how to read it, where projects stand today, and how to contribute.
Why a Public and Community-Driven Roadmap
Because transparency is the same requirement as the product: your data hosted by you, your software without a black box. You build your customer relationship on this tool; you deserve to see where it’s going, and to have your say. A closed roadmap requires trust based on words alone. An open roadmap, on the other hand, shows real progress — and a community roadmap hands you the pen.
The details of what has already been released, version by version, are recorded on the public changelog. The roadmap, however, looks ahead: what we are evaluating, what we have decided to keep, what we have just delivered.
How to read the roadmap: four statuses
The roadmap is organized into four columns, from the most uncertain to the most finalized. An important point: a status is neither a date nor a promise. It represents the real state of a project at a given moment. An idea only moves from one column to another if it proves useful to the greatest number of people.
- Proposed — an idea on the table, not yet decided.
- Under review — I am evaluating its feasibility and real interest.
- Planned — the project is accepted and scoped, without a fixed date.
- Delivered — it’s online, you can use it.
What is the status of each project
Delivered — available now.
- Complete documentation — clear and illustrated guides to install, configure, and operate the vault independently. This also supports WordPress agencies that deploy the plugin for multiple clients. Consult it on the online documentation.
Planned — accepted and scoped, my next priorities (without a fixed date).
- Unlock upon payment (Fluent Cart · WooCommerce · SureCart) — the content of a space or a journey would unlock once payment is received, without manual access granted “while awaiting transfer”. In line with automation & API connectors.
- MCP Server — control the vault with an AI assistant in natural language (“create this client’s space and send them the list of documents”), with automation running on your server rather than with a third party who reads your data in passing.
Under consideration — currently being evaluated, not yet decided.
- Global data export — retrieve all your clients’ data in one go. Total portability, in the spirit of a vault you own on your hosting.
- Vault reset — start from a blank slate in one click, cleanly, at the end of a cycle or after a demonstration.
- Anonymous member in a journey — hide a participant’s identity, synchronously wherever they appear.
Proposed — ideas on the table, to be confirmed if they are useful to the majority.
- Automatic vault backup — files and folders continuously backed up, without you having to think about it.
- Chinese language — open the vault to the world’s largest market, in addition to the eleven languages already available.
- Japanese language — a native experience for your clients in Japan.
A roadmap you write with me
The roadmap is not a showcase : it’s a living idea box. From the roadmap page, you can propose a feature, comment on it, and support others’ ideas — in just a few clicks. Several projects on the board were born exactly this way, from a need raised by a user.
I read everything. I don’t retain everything, and that’s intentional: I keep the ideas that are truly useful to the greatest number, those that make the plugin better for all users — not just an adjustment for a single, specific case. This is the filter that moves an idea from ‘proposed’ to ‘delivered’. If the feature you’re missing checks this box, it has every chance: mention it on the roadmap or in the community.
Our direction remains steady
Regardless of what appears in these columns, our principle remains unchanged: Client Vault remains a plugin that you install on your WordPress, with the hosting provider of your choice, holding data that you alone own. No publisher — myself included — has any insight into what is stored there. Every idea on the roadmap is weighed against this principle, never against it.
And an honest clarification, because a roadmap is not a contract : some ideas will remain under consideration, others will progress quickly. I commit not to deliver everything, but to do the maximum of what is useful to the greatest number — and to show it to you transparently rather than promising dates I wouldn’t be able to keep.
Next Step
Whether you are already a client or simply curious : open the roadmap, follow the ongoing projects, and most importantly, submit the idea you’re missing. If it makes the vault better for everyone, it has its place. To discover the product, take a look at the offers and pricing ; and to discuss it in person, let’s book a video demo.
Frequently Asked Questions
Is the Client Vault roadmap public ?
Yes, on clientvault.pro/roadmap. It is organized by status — proposed, under consideration, planned, delivered — and shows the actual progress of each project. Details of what has already been released can be found on the public changelog.
What do the statuses (proposed, under review, planned, delivered) mean?
They describe the status of a project, from a simple idea to an online feature. A status is neither a date nor a guarantee: it’s a snapshot of progress at a given moment. An idea moves from one column to another if it proves useful to the majority.
Can I suggest a feature?
Yes, and that’s the core of how it works. You can suggest your idea directly from the roadmap, or in the Client Vault community. I read everything and keep what is truly useful to the majority.
Are the displayed features guaranteed?
No. A roadmap expresses intentions, not a contract. Some ideas will remain under review, others will progress. I commit to doing the maximum of what is useful to everyone, and to showing it with full transparency rather than promising dates.
What is the MCP server, currently planned?
A project that would allow an AI assistant to interact with your vault in natural language: create a client area, initiate a request for documents, find a document. Automation would run on your server, without entrusting your data to a third-party service.
Do these developments change anything regarding sovereignty?
Nothing. Client Vault remains a plugin installed on your WordPress, hosted by the provider of your choice, with data that you alone own. Every idea on the roadmap is weighed against this principle, never against it.
