Built for the committee that has no administrator, and is not getting one.
Six researchers, a rotating chair, and a congress that has happened every year since 2011. You are the entire operations department, in the evenings.
This is you
A small or mid-sized research group, or a community that convenes itself
An event that recurs, so every configuration you set is an asset next year
An institution behind you that can invoice and receive money, but gives you no staff
Established in a country where Stripe opens merchant accounts — that is the one hard requirement, and it follows your institution, not the venue or your attendees
This is not
A professional conference organiser with a ticketing contract and an events team
A society needing us to invoice attendees in its name and carry the tax exposure
A journal, or anyone needing papers hosted permanently under their own DOI prefix
A congress requiring three independent reviewers and a rebuttal round
Six roles, one account each
Chair
Everything, including the money and the payment account.
Organizing committee
Everything operational. You can keep the finances out of it.
Jury
Only their assigned papers, only blinded.
Moderator
The accepted papers of the session they chair.
Author and participant
Register, submit, follow the state of their own work.
Invited guest
A reduced or waived rate, with nothing required in return.
Anyone can hold several of these at once. They remain one person in the database, switching roles without switching accounts — which is precisely what makes the conflict check possible.
Set it up once, in an evening. Clone it every year after that.
Nothing to install, no contract, and your existing payment account.