Nemea

Turns bank debt and real-estate portfolios into exploitable investment intelligence.

Vertical: Real estate and banking Solid base

What it is for

Turn real-estate and bank debt portfolios into usable investment intelligence, and market them through a private portal.

What it does

Several coordinated platforms: an engine that automatically interprets the spreadsheets banks send, a non-performing loan module, a bank-owned property module with investment analysis, and a commercial module for investors and lead capture.

Sector

Real estate, banking and asset management (REO / NPL).

What it improves

Analysing a bank portfolio today takes days of manual work across heterogeneous spreadsheets. Here ingestion is automatic and investment analysis is immediate and comparable.

Target client

Investment funds, servicers, banks with their own portfolios and specialised brokers.

Status and maturity

The best-governed asset in the portfolio: continuous integration, a dated in-house code audit as source of truth, and maturity declared module by module.

Differentiator

The semantic spreadsheet ingestion engine is the real moat: it is the work nobody wants to do and what consumes all of an analyst’s time.

Commercial fit

Licence per portfolio or per volume under management plus brokerage commission. The asset with the shortest path to recurring revenue.

Architecture

Layered architecture

A knowledge engine for land and asset, and on top of it a multi-company product with per-client data isolation. Each engine pillar delivers a data product with a stable contract, so the product does not depend on how the pillar is built.

01

Ingestion and normalisation

Spreadsheet-agnostic engine: it interprets the heterogeneous file each bank sends and turns it into a data product with personal information masked.
02

Knowledge pillars

Cartography and reference systems, cadastre and per-floor building, automated valuation with explainability, technical building engine, legal understanding of encumbrances, and image geo-intelligence. Each exposes its own expert and contract.
03

Financial core

Non-performing loan pricing and scenarios, expected credit loss under accounting standard, institutional analysis of repossessed property, stochastic simulation and portfolio/fund view, with the bank view decoupled from the investor view.
04

Multi-company platform

Database per client, role- and attribute-based access control, legal gate, per-operation audit and a hub of pluggable modules.
05

Product and commercialisation

Work desk with territorial and 3D viewer, investor workspace, showcase behind a confidentiality agreement, deal control tower and a sovereign analytical copilot.
06

Embedded cyber defence

Proprietary defence module, isolated behind an activation flag, that does not run unless the deployment explicitly asks for it.

Inventory

Status per component

A real inventory of the asset’s components with their declared status. We publish capability, never code or internal figures.

Built and testedFunctional with declared debtDesigned, not implementedWired; depends on a third party

Semantic ingestion engine
Built and tested

The real moat of the asset and the work that consumes the analyst’s time.
Multi-company platform and access control
Built and tested

Database-level isolation, role and attribute control, per-operation audit.
Debt and property financial core
Built and tested

Scenarios, expected loss, simulation and portfolio, with their own tests.
Automated valuation and technical engine
Built and tested

Valuation with explainability and a building engine with panels embedded in the work desk.
Geo-intelligence and legal understanding
Built and tested

Change detection, 3D and legal querying with document retrieval.
Compliance and anti-money-laundering
Wired; depends on a third party

Built end to end; go-live depends on third-party identity and qualified signature providers.
Governance of its own code
Built and tested

A dated internal audit as source of truth, with the explicit rule of auditing against code, not against a document.
Front-end test coverage
Functional with declared debt

A declared gap being closed: functionality had been built without interface tests.

This profile describes capabilities and status, not implementation. Code, architecture documentation and internal figures are shared under a confidentiality agreement during due diligence.

Platforms