Software development with platform thinking.

Custom development on proven architecture principles

vCongress is not one program. It is a set of capabilities — registration, submission, review, scheduling, payment and invoicing, public presentation, notification — each declared in a registry, switched on per event, and licensed per organisation. Adding one is a catalog entry and its enforcement point, not a branch of the product. That is why a customer-specific requirement becomes part of the standard platform instead of a fork nobody can maintain two years later.

The same parts assemble differently for a different domain. A grant review process, a member directory, a clinical registry and a training programme all need identity, roles, structured submission, review, scheduling, billing and notification — and differ in the model on top, not the machinery underneath.

And if you want to own the product rather than use ours. Some organisations do not want to be a tenant on someone else's platform — they want their own product, for their own market. That is the same construction job with a different model on top. Multi-tenancy, identity, roles, single sign-on, passkeys, per-customer entitlement, media handling and an audit trail are already built and already operated, so the part designed from scratch is the part that is actually yours. We are open about the boundary too: the platform spine carries over, the domain model does not, and where a capability is still tied to congress operations we say so at the start rather than discovering it halfway through.

Where this is heading: assembling a new SaaS product largely from capabilities that already exist and are already operated. We are not claiming a finished product factory — we are saying the parts are built to combine, and one platform in production is the evidence.