whats-best.ai

Property & WEG Management · head-to-head

DOMUS vs Karthago

DOMUS

EU-Made

Panel rating

Sovereignty: 1 of 4 dimensions proven

Full evaluation →

Karthago

EU-Made

Panel rating

Sovereignty: 1 of 4 dimensions proven

Full evaluation →

The written short answer is being updated after a re-evaluation. The scores below are current.

Read this comparison as one judge. Each weighs the same scores by what they care about.

The Portfolio Manager

Runs a firm managing several thousand units and lives on throughput. Wants statutory inspections scheduled with proof stored, defects that route to the right trade, multi-community reporting, and onboarding a new WEG that takes days rather than a quarter.

DOMUS

This judge's pick

Karthago

Criterion by criterion

Wirtschaftsplan, Jahresabrechnung & Rücklage

DOMUS

There are dedicated product pages for booking the Wirtschaftsplan and for producing the Hausgeld settlement under WEG 2.0, which puts the statutory cycle inside the product rather than in Excel. Beyond those page topics we found no public information on configurable distribution keys, separate trust handling of the reserve, or a separately shown Abrechnungsspitze — the details that decide whether a settlement survives a contested owners' meeting.

Karthago

The module list names Doppelte Buchhaltung and 'WEG- & Nebenkostenabrechnung', so a settlement capability exists, but the evidence is silent on Wirtschaftsplan, distribution keys, Rücklage separation, BGH form or dunning. With several thousand units I cannot confirm the reserve is even booked apart from operating funds — rubric level 3 is the most I can honestly give a nameplate module.

Eigentümerversammlung & Beschluss-Sammlung

DOMUS

Homecase carries an Abstimmungsmodul for online owners' meetings plus newly published WEG meeting functions, so meetings are genuinely conducted in the system rather than on paper. We found no public information on quorum and majority computation, proxy handling, or a continuously maintained Beschluss-Sammlung with amendment and invalidation notes — the register is the first thing an owner's lawyer asks me for.

Karthago

Zero evidence: the module list and the product scope statement cover master data, billing and owner communication, and not a word about Versammlung, invitations, minutes or a Beschluss-Sammlung. Meetings and the statutory resolution register evidently stay entirely outside the system, which is an anchor-0.

Owner & tenant self-service

DOMUS

Documents are placed online for owners in Homecase and a service-case portal exists, but we found no public information on per-owner scoping, personal statements, or defect status visible to the reporter. Without confirmed scoping I cannot put one owner's arrears or settlement in front of another owner's eyes.

Karthago

All I have is the marketing line 'Kommunikation mit Eigentümern und Mietern – alles in einer Lösung' — no per-owner login, no statements, no meeting papers, no defect form, no tenant/owner separation evidenced. Requests presumably still land on my staff, so this sits just above nothing.

Maintenance, defects & contractors

DOMUS

A ServiceCase maintenance portal combined with a communication platform that connects our craftsmen and service providers directly is real routing infrastructure, not a phone notebook. We found no public information on recurring maintenance calendars, warranty periods tracked against the responsible trade, or statutory lift, heating, fire-safety and drinking-water inspections with proof of completion stored — exactly the operating record I need when something fails.

Karthago

'Digitales Facility Management' as a module name is the entire evidence — nothing on defect routing to the responsible trade, statutory inspection calendars (lift, heating, fire safety, drinking water) or stored proof of completion. The exact machinery I run my portfolio on is unevidenced, so this is barely off the floor.

Documents, retention & handover

DOMUS

A reports and data-export function and online document placement exist, but we found no public information on version history, retention periods for community records, or a structured handover package a successor administrator could actually load. When I onboard a new WEG in days, the incumbent's exit story matters as much as my entry.

Karthago

'Integriertes Dokumentenmanagement' is named and the on-premise option puts data 'in Ihrer Hand', but there is nothing on versioning, statutory retention periods or a structured handover export a successor could load. Handover of a WEG is a statutory event for me, and the evidence treats it as a non-topic.

European sovereignty

DOMUS

The contracting entity is a German AG registered in Munich, web analytics run self-hosted, and third-country transfers are framed under EU adequacy decisions or standard contractual clauses. Hosting location for the actual management data is unstated and we found no public information on subprocessors — silence I cannot underwrite for thousands of owners' records.

Karthago

German servers with 'zertifiziertem Datenschutz' are claimed and a real on-premise option exists, which I value, but the contracting entity's jurisdiction is unconfirmed (an Aareon entity surfaces only in the contact trail) and there is no subprocessor list at all. EU hosting with an absent subprocessor list is precisely the anchor-3 state.

Pricing transparency

DOMUS

Every route to a number runs through a quote request inside a Beratungsgespräch or the online shop of the sales partner TSA Solution GmbH, and we found no public prices, per-unit or per-community. I cannot compute the annual cost for my portfolio from what is published, which for a multi-thousand-unit book is disqualifying.

Karthago

The only route to a number is a Beratungs­gespräch form demanding my managed units and workstation count — no public prices of any kind. I cannot compute an annual cost per unit across my portfolio without a sales call, which is the definition of rubric level 0.

Sovereignty, side by side

Dimension DOMUS Karthago
Legal entity Incorporated in DE Not determined
Ownership Not determined Not determined
Data residency Not determined EU only
Subprocessors Not determined Not determined