Hyperiux Vault makes it much easier to create a website that feels custom and memorable without building every interaction from scratch.
What stands out most is the source-first approach. The effects are installed directly into your project as editable code, so you are not locked into a black-box component package. You can change the layout, styling, timing, easing, breakpoints, mobile behavior, and animation logic to suit your product.
The collection also goes beyond basic UI components. It includes scroll effects, cursor interactions, text animations, page transitions, loaders, backgrounds, navigation patterns, carousels, and WebGL experiences.
The CLI makes installation straightforward, while the live previews help you understand an effect before adding it to your project. I also appreciate that the documentation discusses practical considerations such as dependencies, accessibility, reduced motion, mobile fallbacks, and performance.
the source-owned angle (copy it, edit it, it's yours) is the right call given the shadcn precedent. but that model has a natural tension with maintenance - once I've copied an effect into my project and customized it, if you later ship a bug fix or perf improvement to that same effect upstream, is there any path for me to pull that in, or am I just permanently forked from that point on and on my own for updates?
Great question, @galdayan! This is a real trade-off with source-owned code. Right now, once you customize an effect, it's basically your own fork. We'll never touch it silently, but that also means upstream fixes need to be applied manually. We don't think "you own it" should mean "you're on your own," though. Fixing that is high on our roadmap.
The plan is to turn the CLI into a lightweight sync layer. Each effect carries version metadata, so something like `npx hyperiux check` can flag when there's an upstream bug fix or perf improvement waiting. Then an interactive diff (think Git) shows exactly what changed, so you can cherry-pick what you want instead of your customization getting overwritten.
So the honest answer is - yes, updates are manual today. The direction we’re building toward is opt-in, reviewable synchronization and not silent auto-updates, and not permanent abandonment after copy-paste. Hope this helps!
@bhaskarvarshney that's a much better answer than I expected honestly, most tools in this space just wave their hands at the fork problem. one thing I'm curious about - the interactive diff works fine when the upstream fix touches lines you never touched. what happens when the upstream fix is literally on the exact line you customized, like they changed the same easing curve you tweaked? does it fall back to something like git conflict markers, or does it just skip that hunk and tell you to eyeball it yourself?
@galdayan Our intended direction is a three-way comparison between the original version you installed, your current customized version, and the latest upstream version. If your local copy and the upstream update changed the same section, the upgrade flow would flag it as a conflict and show all three versions side by side: the original, your edit, and the upstream fix. You could then keep your version, accept the upstream version, or manually combine them.
Implementation wise - Git style conflict markers could exist as a fallback, but ideally the interactive flow would surface and resolve the conflict before writing anything back to the file. The exact UX is still being worked through, but silent overwrites are firmly off the table. :)
@bhaskarvarshney "silent overwrites are firmly off the table" is the part that matters most, even if the exact UX isn't nailed down yet, that's a commitment you can hold the team to later. three-way diff before any write is the right default position to be building toward. curious to see what the conflict UI actually looks like once it ships.
Very excited to see Hyperiux Vault officially launch today! 🚀
Working on this product has been an incredible learning experience. Throughout the journey, I had the opportunity to explore new ideas, craft intuitive and interactive experiences, and collaborate closely with an amazing team to bring those ideas to life.
A huge thank you to everyone involved-from design and development to integration and testing-for the collaboration, support, and dedication that made this launch possible. It's rewarding to see months of hard work finally go live and be featured on Product Hunt.
Proud to have been a part of this journey, and excited to see what comes next. 🎉
Super excited to see Hyperiux Vault officially launch! 🚀
Being part of this journey has been an incredible experience. From exploring new interaction ideas to designing intuitive user experiences, every step challenged me to grow as a designer.
A huge thank you to the entire team for the collaboration, feedback, and dedication that made this possible. It's amazing to see months of hard work finally go live and launch on Product Hunt.
Proud to have contributed to this milestone, and excited for everything that's ahead. Congratulations to everyone involved! 🎉
Every pixel. Every interaction. Every tiny detail.
Watching it all come together today is such a rewarding feeling. So excited! ✨
Excited to finally share this!!
I spent the last few months designing and building Hyperiux Vault, a collection of interaction effects we've been refining through real client work, now packaged so anyone can copy, customise, or install them.
Seeing Hyperiux Vault finally launch felt surreal. 🎉
What started as a simple idea has grown into something we're incredibly proud of. Building Hyperiux Vault has been a journey of countless iterations, late nights, and a shared vision to make high-quality UI components more accessible for developers and designers. Huge thanks to everyone on the team who made this possible. 💙
We're just getting started, and we can't wait to see what you build with Hyperiux Vault. Every piece of feedback, upvote, and share means the world to us. Let's build something amazing together! ✨