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.

    Technology company with proprietary AI.
    Friedrichshafen on Lake Constance.
    Operated on sovereign infrastructure in Germany.
    Six platformsOne codebaseProprietary AI2–4 weeks per new verticalPenetration tests completed
    01 — The Engine

    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.

    001

    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.

    002

    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.

    003

    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.

    02 — Platforms

    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.

    01
    clubbrain®
    The intelligent platform for team sports and multi-sport clubs. Six areas on one data set — board, administration, club life, sport, finance, tournament. With sport DNA, tactical work and joint play across club borders.
    Pilot phase
    02
    verein.cloud®
    The vertical-neutral entry point. Management, fees, finances, communication for clubs of all kinds.
    In market
    03
    OpenFootball®
    The football edition. District, league and federation logic natively mapped — own brand, own presence, own sales. For clubs expecting more than just fixtures and registrations.
    Launch 2026
    04
    StiftungsOS
    For foundations and non-profit organisations. Projects, annual budgets, board resolutions, donation receipts.
    Pilot phase
    05
    Event-as-a-Service
    The ecosystem for festivals and organisers. Ticketing, artists, catering, sponsors, volunteers, payment — seven interest groups on one database.
    In development
    06
    Niche Editions
    Guilds, music, shooting clubs, hunters, fire brigades. Each vertical with its own roles, its own cycles, its own name.
    From Q4 2026
    03 — OpenClub® AI

    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.

    001

    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.

    002

    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.

    003

    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.

    04 — The architecture in numbers

    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.

    1
    Codebase supports all platforms, verticals and brands
    2–4
    Weeks from configuration to operational platform per vertical
    100 %
    of member data is processed on proprietary infrastructure in Germany
    176.000
    digitally addressable clubs in the German-speaking region
    05 — Collaboration

    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 briefing

    Technology Partners

    White label, interfaces, joint development of vertical-specific business models. For providers wanting to occupy a vertical without building the infrastructure themselves.

    View models

    Capital

    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 touch
    06 — Under Cover

    A 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.

    The Venture Lab is not a product or a program with open registration. Access is granted to partners we already work with and selected investors.
    07 — How we build

    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.

    Seam
    Seams instead of machines. We build the point where configuration will later take place — not the configurable system itself. A default value with a clean seam is enough, as long as a tenant exists. Everything else is speculative inventory.
    Practice
    Ship first, then harden. Functions enter real hands early. Pilot operation is not a preliminary stage of development, but its test bench. If nobody uses it, it isn't finished.
    Tenant
    Multi-tenant by design. Every new table carries a tenant ID and row-level security from the first line. Retrofitting costs many times more than building it in from the start.
    Clarity
    No line without clarity. Technical convention precedes code. If it hasn't been decided, it won't be built — even if it could be done quickly.
    08 — Contact

    If you organise a community, we should talk.

    Inquiries

    Jean-Claude ParentManaging Directorjean-claude.parent@maitrx.ai

    maitrx GmbH

    Seeblick 21
    88045 Friedrichshafen
    Deutschland

    Infrastructure

    OpenClub® AI
    Eigene Kubernetes-Umgebung
    Rechenzentrum Bielefeld

    Write to us
    We use your details exclusively to respond to your enquiry.