Tickets, memberships, and gifts on one stack
Almost everything a museum sells or asks for runs through the same few screens: a ticket, a membership, a donation, a class. My team builds and maintains those online flows on ACME for the Barnes and Calder Gardens.
When Calder Gardens opened it needed all of that under its own brand, so one codebase deploys twice, with one ACME tenant and one customer data layer underneath. Two front doors, one back office. That's also what made Plus admission possible: one ticket to both institutions, composed at purchase and put back together at the gate.
We keep our ACME client open source, so any museum on the platform can use it.
Read more: One Codebase, Two Brands