Monkey Box allows teams to securely store, organize, and selectively share secret information. It’s a SaaS product aimed at service providers, IT managers, and small business owners who need to properly document their IT-related assets, passwords, files, and notes.
Built for developers, too
So how does it work? Well, if you’re a developer like us, you’ve probably run into problems like these:
- I need to share the production server credentials with other people on my team. Hmm, probably shouldn’t send that via plaintext email…
- Sensitive API keys and Rails secret token definitely shouldn’t go into source control. Where’s a good place for safekeeping? What if my teammates need to access them while I’m on vacation?
- Where do we store those expensive SSL certificates in case we need to rebuild the VPS?
We built Monkey Box to handle these scenarios, plus a lot more.
Monkey Box has been a fun and challenging project for our team, especially considering the strict security goals we have for the product. We used some neat Ruby meta-programming to ensure that all important data is encrypted when it needs to be, and backed that up with an incredibly thorough test suite using RSpec and capybara.
It goes without saying that Monkey Box is built with Rails (3.2), and we’re seeing some impressive front-end performance thanks to the turbolinks gem. Many of the Rails-related posts on the 55 Minutes blog recently (and to come) are the result of lessons learned and best practices used on this project.