2026 Product Roadmap

[luongnh261]

As we say goodbye to 2025, we’re proud of everything the Locker team has delivered based on the goals outlined on this page.

We’re excited to begin shaping our 2026 Product Roadmap 🎯

If you have ideas, feature requests, or challenges you’d like us to prioritize in 2026, we’d love to hear from you. Your feedback plays a direct role in shaping what we build next.

👉 Share your thoughts by commenting below - our team will review every submission and reflect updates on the roadmap shown on this page.

Thank you for being part of our journey and helping us shape the future of the product.

[vhbui02]

How about starts with implementing the regex/prefix-based searching on Web UI and add something like locker secret list --environment=all --environment=Production, where env vars from both envs are returned, and env vars from the latter --environment=all option value would override the env vars from prior --environment=Production option?

I fed up with locker secret list --output-format json | jq pipelining trick to filter and aggregate. I had to maintain two seperate versions: one for Linux and one for Windows because of this.

[luongnh261]

@vhbui02 Thanks for your feedback. I will send this request to our team for further discussion.

[vhbui02]

Why does today, Python SDK API locker.list() only returns 1 or 2 secrets?

[luongnh261]

Hi @vhbui02, we've checked and it worked normally - please check if you chose the right project. If the issue persists, please report more details in a ticket, or email us via support@locker.io.

[vhbui02]

Hi @vhbui02, we've checked and it worked normally - please check if you chose the right project. If the issue persists, please report more details in a ticket, or email us via support@locker.io.

Huh, this is odd. I change the access key ID & secret access key pair (their differences are that I'm switching from read-only one to read-write counterpart) and it worked again.