About
I Built RigVault Because I Needed It Myself.
I'm Christian, a musician, producer, and developer based in the Des Moines area. I built RigVault because the tool I needed to keep my own gear, cases, and gig loadouts straight didn't exist, so I wrote it.
Gear management shouldn't run on memory and spreadsheets.
Between studio sessions, tour dates, and the shows I've booked and promoted, I kept losing track of the same things: what gear I actually owned, which case it lived in, what needed to go to which gig, and what was actually covered if something got damaged or stolen. A spreadsheet works right up until it doesn't.
What I wanted was one place that connected the equipment to the case it travels in, the rig it belongs to, the loadout that takes it to a show, and the paperwork that protects it, instead of four disconnected systems, one of them being my own memory. That's RigVault. I eventually formalized the structure behind it into a framework I call MAIS.
The Person Behind It
A musician who also happens to write software.
I'm a multi-instrumentalist, composer, and studio producer, and I've spent years booking and promoting concerts. I also run a software practice building custom web applications and platforms. RigVault sits at the intersection of both: gear management built by someone who actually loads a van and packs a stage, not a generic inventory tool retrofitted for music.
Built for the way musicians actually work.
RigVault has to hold up for a solo act playing a bar with a guitar and a pedalboard, and for a full production ensemble loading into a concert hall, on the same product, without turning into two different apps. If you want to see how that plays out for your situation specifically, start with Musicians, Bands, or Touring Musicians.
FAQ
About RigVault, answered.
Who built RigVault?
I did. RigVault is built and actively maintained directly by me, Christian. It's not a feature inside a larger platform or a project handed off to a team.
Is RigVault run by a large team?
No. It's built and run by one person, which means changes ship fast and any support request reaches the person who actually wrote the code, not a queue.
Where is RigVault based?
The Des Moines, Iowa area.
See what I built.
Explore the features RigVault connects.
See RigVault Features