Condominium management software built for the German WEG.

Why generic property software doesn't fit a German WEG

A German WEG is not the same as a US HOA, a UK leasehold or a French syndicat de copropriétaires. The German Wohnungseigentumsgesetz (WEG-Gesetz) imposes specific operational requirements that generic property management software typically does not model:

• An economic plan (Wirtschaftsplan) per § 28 WEG must be presented and approved at the annual general meeting before each business year.
• An annual statement (Jahresabrechnung) per § 28 (2) WEG with per-owner allocation by the configured distribution key.
• A resolution archive (Beschlusssammlung) per § 24 (7) WEG, kept since 2007, with sequential numbering and full text of every resolution.
• The distribution key (Verteilungsschlüssel) — typically by ownership share (Miteigentumsanteil) but configurable per cost type.
• A separation between common costs and individual costs per § 16 WEG, distributed differently.
• The reserve allocation (Erhaltungsrücklage) modelled correctly across years.

dooyah house models all of these natively. Generic property tools either bolt them on as report templates or leave them as manual spreadsheet work.

Built for self-administration, not for large management firms

Most existing German WEG software targets professional property managers (Hausverwalter) with portfolios of 50, 200 or 500 units. The pricing, the onboarding effort and the complexity reflect that.

dooyah house is built for WEGs in self-administration of any size — from two-unit buildings through classic 8-12-unit communities to mid-sized WEGs — that administer themselves rather than hire a professional. The Pro standard tariff covers up to 30 units per WEG as a flat fee per WEG; larger WEGs (more than 30 units) in self-administration are handled individually on request. The free plan covers the operational basics for one WEG up to 10 units. The Pro plan adds the parts that genuinely save hours (bank import, AI matching, OCR, annual statement automation).

What dooyah house does

• Master data: WEGs, units, owners, ownership shares, distribution keys, voting weights.
• Bank import: CSV, MT940, CAMT.052/053 — every German bank.
• AI auto-matching: proposed booking entries from new bank transactions.
• Booking journal: WEG-compliant accounting structure (common cost, individual cost, reserve).
• Economic plan & annual statement: automated drafts per § 28 WEG.
• Resolution archive: sequential numbering, full text, exportable per § 24 (7) WEG.
• Owner portal: read-only access to statements, documents, resolutions.
• Document storage: invoices, contracts, minutes — with OCR.
• Passkey login: WebAuthn / FIDO2 by default.

Who this is for

• WEGs of any size in self-administration — two-unit buildings, classic 8-12-unit WEGs, mid-sized communities, and larger WEGs (more than 30 units) on request.
• WEG board members (Verwaltungsbeirat) who want to retire Excel.
• Owners who want a real audit log and a real resolution archive — not a folder full of email attachments.
• International owners or co-administrators who want a clean, GDPR-compliant tool with servers in Germany.

Who this is NOT for

• Professional property managers with multi-WEG portfolios — better served by Etg24, Casavi or similar.
• Pure rental property management (Mietverwaltung) with no WEG context — not our target.
• Industrial-scale ticket/issue management for hundreds of rental units in parallel — not part of the product.
• Anyone needing a fully English-localised application UI today — the application is German-first; this marketing site is English.

(Larger WEGs in self-administration are not excluded — the Pro standard tariff covers up to 30 units per WEG; larger setups are handled via an individual offer. More details on the larger-WEG answer page.)

Privacy, security and infrastructure

• WEG main data hosted on Microsoft Azure servers in Germany (primary region Bavaria). Operated by FloriCore Software UG (haftungsbeschränkt) in Eggolsheim, Germany.
• TLS 1.3 in transit, AES-256-CBC for sensitive fields, multi-WEG isolation on the database level with foreign-key constraints.
• Append-only audit log for bookings and security-relevant actions.
• Login by passkey (FIDO2/WebAuthn) or optional TOTP-2FA.
• GDPR-compliant data processing agreement (AVV) per Art. 28 GDPR available on request.
• Sub-processor list public (sub-processors: Microsoft Azure, Cloudflare, Brevo). Mollie acts as independent controller for payment processing.