Technology and security

What Homono is built on, and what protects your data.

The questions an organisation asks before entrusting its tenants' files, and our answers. What is not yet delivered is marked as such.

The foundations

Proven technology, nothing exotic.

The application

Written in TypeScript with Next.js and React, open building blocks in very wide use.

The database

PostgreSQL, queried through Prisma, which describes and types the data model.

Hosting

Railway, in Europe: the application and the production database run in the Netherlands.

Files

Documents and attachments are kept at Cloudflare, outside the database.

Where your data lives

Where it is stored, and who processes it.

The production database

In the Netherlands, at Railway, a US company. It holds the leases, the accounts, the exchanges.

Files

At Cloudflare, a US company.

What is processed in the United States

The assistant and document reading — identity papers, bank documents, meter photos — go through Anthropic. Other services also process some data in the United States: sending e-mail and, depending on each organisation's configuration, WhatsApp, Gmail, address suggestions. Each transfer and its safeguard are listed on the subprocessors page.

Every subprocessor, its role and its location

What protects it

Each organisation's files are separated by the database itself.

One organisation, one compartment

Leases, accounts, documents, repairs: an organisation's files are filtered by PostgreSQL itself, and a query only sees those of the active organisation. Person records, which the same person may have in several organisations, are separated by the application. On every code change, a check flags any organisation table lacking that filter.

Encrypted secrets

Credentials for connected services — bank, messaging, AI — are encrypted; the key is kept outside the database.

Passwords never stored

Only their fingerprint is kept. Repeated sign-in attempts are limited.

Encrypted connections

HTTPS enforced everywhere, and a security policy that forbids the browser from loading resources from elsewhere.

A backup every day

The database is backed up daily, outside its hosting; the restore procedure is written down.

Sessions that expire

A session closes after twelve hours of inactivity, or thirty days if you choose to stay signed in.

Who can access it

Everyone sees what concerns them, and nothing else.

A scope per role

Property manager, owner, tenant, contractor, supplier, organisation administrator: each role has its scope. A tenant only sees their own lease; an owner, their own properties.

The Homono team

For support, the Homono team can access a user's account. That right is reserved for platform administration.

Every access recorded

Viewing and changing tenant files — record, lease, account, documents — is recorded: by whom, and when. When the Homono team steps in, the record keeps both the person acting and the person on whose behalf they act.

In preparation
  • Two-factor authentication — A second factor at sign-in, through an authenticator app with recovery codes, which each organisation will be able to require from its whole team.
  • Reviewing these records — A screen where the organisation finds who viewed or changed which file, and when.
Artificial intelligence

AI within limits: it prepares, a person confirms.

A named provider

The assistance features run on Claude, Anthropic's model.

Validated sources

For a legal question, the tenant assistant only relies on validated passages, specific to the region and the language.

A human in the loop

The AI prepares — a meter reading, a repair request, a letter — and a person confirms.

In preparation
  • Choosing the model — Each organisation will be able to choose the AI model that handles its requests.
If Homono stops

Your data stays yours.

Your organisation decides

For its tenants' data, your organisation is the controller; Homono is only the processor.

Exports today

Accounting entries export to CSV.

The code

Depositing the code with a third party, guaranteeing access to it if Homono disappears, can be provided for in your contract, on request.

In preparation
  • The complete archive — The whole organisation — buildings, leases, accounts, documents, history — in an archive the organisation downloads itself, in a format designed to be re-imported.
  • At the end of the contract — An archive generated automatically, regenerable for thirty days, then a certificate of deletion.