One architecture.
Every community.
maitrx develops the platform engine on which clubs, federations, foundations and event organisers operate their own digital infrastructure. Under their name. On our technology. With AI that never leaves Germany.
We don't build many products. We build one, very often.
Every platform leaving our house rests on the same architecture. What changes is the configuration — roles, cycles, modules, design. What remains constant is everything beneath: multi-tenancy, accounting, payment processing, governance, security.
Platform Core
Member management, subscriptions, SEPA, double-entry bookkeeping according to SKR 49, multi-tenancy, rights and roles. The part that is needed everywhere and tolerates no differences.
Community DNA
The configuration layer. It describes how a vertical actually works: which offices exist, which cycles, which events. A carnival guild is not a handball club — the code knows the difference.
White-Label
The federation appears under its own name, with its own design and domain. The technology stays with us, the brand stays with them. Weeks pass from order to operational readiness, not years.
Six proofs for the same thesis.
Each of these platforms is a configuration of the same engine. Technology and brand rights remain with us, operations and sales with exclusive partners. This ensures the architecture remains in one hand and customer contact stays where the vertical is at home.
We work with children's data. So it stays here.
Club data is the most sensitive category there is — youth, health details, finances, volunteering. That is why we build our own AI: operated on our own infrastructure, processed exclusively in Europe, without access from third countries. It is not a bought-in tool, but the asset around which everything else is created.
Proprietary Operation
Freely available top-tier models, operated on our Kubernetes environment in Germany. No language model built from scratch — but proven technology in our own hands.
Expertise instead of platitudes
Association law, SKR 49, SEPA, funding logic, charter audits, federation workflows. Domain knowledge that an off-the-shelf American provider does not and will not have.
Enforced by technology
A central control point checks every query. Member data cannot leave the house — not as a paper guideline, but as a property of the system.
The question is not if AI arrives in club work. But who owns the data when it does.
We don't count customers. We count capabilities.
These four figures describe why every subsequent vertical is created faster than the last — and why the model becomes cheaper with every vertical instead of more expensive.
Three ways to work with us.
We do not sell licences to end customers. We work with those who bring reach, mandate or capital.
Federations
You have the member clubs, we have the platform. Own branding, own domain, own vertical logic — under your name, operational in a few weeks. Revenue sharing instead of licence costs.
Request a briefingTechnology Partners
White label, interfaces, joint development of vertical-specific business models. For providers wanting to occupy a vertical without building the infrastructure themselves.
View modelsCapital
A model that scales per vertical instead of per product: The marginal costs of each additional vertical decrease with every one already built. Documentation on request and upon review.
Get in touchA business model is born here every week.
Fully conceived. Technically viable. Market-ready. We don't talk about it publicly — but we do talk about it.
Architecture arises from what you don't build.
Four rules apply to every project, regardless of vertical, customer or deadline pressure. They are the reason why the sixth platform costs less effort than the first.
If you organise a community, we should talk.
Jean-Claude ParentManaging Directorjean-claude.parent@maitrx.ai
Seeblick 21
88045 Friedrichshafen
Deutschland
OpenClub® AI
Eigene Kubernetes-Umgebung
Rechenzentrum Bielefeld