Roadmap
What's planned for PulsVault — the Android and iOS apps now in beta and store review, plus the browser extension, desktop apps, and help-center improvements still in development.
Where PulsVault is heading. Today the web console is the fully supported way to use PulsVault; the items below are in development or planned.
This page reflects current intent, not a commitment. Priorities and timelines can shift; nothing here is a promise of delivery. For what has already shipped, see the changelog.
Apps & platforms#
| Platform | Status |
|---|---|
| Android app | Beta — feature-complete, in store review |
| iOS app | Beta — feature-complete, in store review |
| Browser extension (autofill) | In development |
| Windows desktop app | Planned |
| macOS desktop app | Planned |
| Linux desktop app | Planned |
The command line (pulsvault CLI) has shipped — it reads and writes DevOps secrets and runs
credential validation from a terminal or a CI pipeline. See the
CLI documentation and the changelog.
Everything still marked In development or Planned is shown with a Soon badge on the PulsVault website; the mobile apps are past that stage and now in testing.
Every client follows the same zero-knowledge model: encryption and decryption stay on your device regardless of platform. When they launch, setup instructions will land in Install apps & extension.
Mobile apps — what "beta" means here#
Development of the Android and iOS apps is finished. What is left is release, not build:
- Testing track — the builds are distributed to a limited test group (Google Play closed testing on Android, TestFlight on iOS) so real-device issues surface before a public release.
- Store review — both apps are going through Google Play and App Store review. That step is outside our control and can add days, and a rejection means a resubmission.
- No public download yet — the store listings are not live, so there is still nothing to install from Google Play or the App Store. The moment they are, the links appear under Resources → Downloads and in the changelog.
Beta builds are the same zero-knowledge client as the shipped app will be: keys are generated and used on the device, and nothing about your vault is readable by our servers during testing. What can still change before release is the app's UI and the exact set of features enabled at launch.
Help & support center#
The console does not currently include a Help & Support area; this documentation is the self-serve knowledge base. Wider help content — tutorials, video guides and update feeds (what's new, changelog, roadmap) — is planned for when that area returns. See Support for what's available now.
Documentation#
These docs are actively being written — pages marked as drafts are being replaced with full content on a rolling basis.
Have a request?#
Feature suggestions are welcome through a support ticket — see Support. Requests from team and enterprise customers can also go through your sales or account contact.