Chapter software built for Panhellenic Council chapters.

Yes. The rush board stages are yours to define, so a chapter running four rounds and a chapter running two both see their own process rather than a fixed template.

Yes. Identity and ballot are stored separately with no link between them, and each ballot carries a SHA-256 receipt so a member can verify their vote counted without revealing how they voted.

Both. Members pay dues by card into your chapter’s own Stripe account, and alumnae give through Stripe flows tagged by campaign. On dues-sharing sites, the platform takes 5% of collections through the service (dues, event bookings, giving, and brother web-app tickets), and 10% of external public event ticket sales, even if the chapter does not collect dues. The 5% comes out of the amount paid, Stripe's processing comes out of the 5%, and choosing dues sharing waives the flat plans. Flat plans ($25/week or $1,000/year) do not include dues collection through GreekStack. Every payment that does run through GreekStack on a flat plan (giving, tickets, vendor bookings and rentals) carries the 5% platform fee, or 10% on public ticket sales, with card processing inside it. Event ticket sales carry a platform fee on every plan: 5% of member orders and 10% of public website sales, with Stripe processing included in that fee. Buyers pay the listed ticket price and nothing is added on top. Vendor bookings and rentals carry a 5% fee taken from the vendor's payout, on every plan, with card processing included.

Yes. Every chapter gets its own isolated database schema, so your roster, recruitment records and dues history are walled off from every other chapter on the platform. Officer access is further scoped by role.