DoJiggy vs Houdini

DoJiggy is a web-based fundraising platform for nonprofits, schools, and other charitable organizations. Campaign options include peer-to-peer crowdfunding, donations, ticketing, golf tournaments, online stores, raffles, and charity auctions. Participants and teams can customize fundraising pages with thermometers, social sharing, and gamification. Event registration supports live, virtual, and hybrid events, with ticket tiers, group registration, custom fields, capacity limits, and QR code check-in. Organizations connect Stripe or PayPal to process payments; DoJiggy says it does not hold campaign funds and does not store payment information on its servers. Apple Pay and Google Pay are also supported. Listed integrations include Google Analytics, Meta Pixel, and Zapier, which connects to more than 5,000 apps. The service offers training and support by ticket, live chat, and email, plus 24/7 emergency support for a fee. Campaigns can run without subscription fees, but payment processing fees are paid directly to Stripe or PayPal. DoJiggy says it does not support individual fundraising for personal accounts. The company began developing fundraising software in Boulder, Colorado, in 2003.

Houdini is free, open-source fundraising infrastructure for nonprofits and NGOs. It provides crowdfunding campaigns, fundraising events, donation forms, a donate-widget page and generator, plus simple donor management. Nonprofit dashboards cover payment history, payouts, recurring donations, metrics, supporter relationships through a CRM and organizational user accounts. Campaign reporting is listed as advanced. Payment processing is separate and requires Stripe API keys during setup. Houdini runs as a self-hosted Rails application, with production instructions for Linux using SystemD and Nginx. Supported systems include Ubuntu 18.04, 20.04, 22.04 or an equivalent. Prerequisites include Node.js 16, Yarn, PostgreSQL 12 (PostgreSQL 10 may work) and Ruby 2.7. The project describes its latest version as pre-2.0 and in heavy development, recommending v1 instead. Building JavaScript assets needs about 3 GB free RAM, while the deployment guide suggests at least 4 GB for the server. Security reports go by email; GitHub Discussions hosts project chat.