Product · Property technology
Domicium keeps the whole rental relationship in one place — not five inboxes.
Renting a property generates a long chain of decisions, documents and payments across landlords, agents, tenants and contractors. Most of it lives in email, spreadsheets and messaging apps, so nobody has the full picture and disputes come down to who kept better records. Domicium models the relationship itself.
Tenancy record
Payments ledger
Maintenance
Compliance dates
This description is provisional and is awaiting confirmation from the Domicium product owner before any of it is published as a factual description of the product.
The problem
A tenancy is a multi-year relationship handled as a series of disconnected transactions. Applications arrive by email with documents attached, references are chased by phone, agreements are signed as PDFs and stored locally, payments are reconciled by hand, and maintenance is reported by text message. When something is disputed — a deposit, a repair delay, a rent arrears schedule — reconstructing what happened means searching several inboxes belonging to several people.
The product insight
The tenancy, not the property and not the transaction, is the right central object. Once applications, verification, agreements, payments, maintenance and communications all attach to a tenancy record, the account of what happened is a byproduct of doing the work rather than something anyone has to assemble afterwards.
Who it is for
- Landlords
- From single-property owners to portfolio landlords who need oversight of occupancy, income, compliance dates and maintenance.
- Letting agents
- Agencies managing properties on behalf of landlords, who need auditable process and clear separation between client portfolios.
- Tenants
- Renters who want a clear application process, one place for their agreement and payments, and maintenance requests that do not vanish.
- Contractors
- Maintenance providers who need scheduled jobs, access details and a clean route to getting paid.
Value
What it gives you
- Applications and referencing handled in a structured flow, with identity verification integrated.
- Agreements generated from the tenancy record, signed electronically and stored with the record.
- Rent, deposits and contractor payments tracked against the tenancy with automatic reconciliation.
- Maintenance requests with photographs, contractor assignment, scheduling and a resolution record.
- Compliance dates — safety certificates, licences, inspections — tracked with reminders before expiry.
- One communication history per tenancy, so a dispute is settled by the record rather than by recollection.
Capabilities
What exists today, and what does not
Split by status deliberately. A roadmap item presented as a shipped feature is the most common way software companies lose trust.
In beta · 8
Property and portfolio management
Property records with compliance documents, certificate expiry tracking, occupancy history and portfolio-level views for landlords and agents.
Listing and discovery
Structured listings with media, availability and viewing scheduling, published to the agent’s own presence and to portal feeds.
Applications and referencing
Structured applications with document upload, affordability information, employment and previous-landlord references chased by the system rather than by a person.
Identity and right-to-rent verification
Identity verification integrated through a provider interface, with the evidence retained against the application and the check recorded.
Agreements and e-signature
Tenancy agreements generated from the record, sent for electronic signature, and stored with a full signature audit trail.
Payments and reconciliation
Rent collection, deposit handling with scheme registration tracking, contractor payments, and reconciliation against the tenancy ledger.
Maintenance and works
Tenant-raised requests with photographs, triage and priority, contractor assignment and scheduling, and a resolution record with cost.
Communications
Tenancy-scoped messaging with a retained history, and notification preferences that respect quiet hours and consent.
Planned · 2
Compliance calendar
Tracking for safety certificates, licences, inspections and statutory dates, with escalating reminders ahead of expiry.
Portfolio reporting
Occupancy, arrears, yield, maintenance spend and compliance position across a portfolio.
Journeys
How people actually move through it
From viewing to keys
- 01Find a property and book a viewing from real availability.
- 02Apply through a structured form that states exactly what is needed and why.
- 03Complete identity verification and upload supporting documents once.
- 04Track the application status without having to chase anyone.
- 05Review and sign the agreement electronically.
- 06Pay the deposit and first rent, and receive confirmation of deposit-scheme registration.
Managing a let end to end
- 01List the property with compliance documents attached to the record.
- 02Manage viewings and receive structured applications.
- 03Review referencing and verification outcomes in one place.
- 04Generate and issue the agreement from the tenancy record.
- 05Track rent, arrears and deposit handling against the ledger.
- 06Handle maintenance and report to the landlord from the same record.
Overseeing a portfolio without chasing
- 01See occupancy, income and arrears across the portfolio.
- 02Review upcoming compliance dates before they become a problem.
- 03Approve maintenance above an agreed threshold.
- 04Review statements and reconciled payments.
- 05Decide on renewals ahead of the term ending.
Trust, privacy and security
The model underneath
These are architectural commitments rather than policy statements — each corresponds to something enforced in the system.
- Strict tenancy scoping
- Access is granted per tenancy and per role. A tenant sees their own tenancy; a contractor sees the job and the access details, not the tenant’s financial record. Isolation is enforced in the database, not only in the interface.
- Financial data separation
- Bank details, affordability information and arrears history sit behind permissions beyond ordinary tenancy membership, because most people who legitimately touch a tenancy have no need to see them.
- Evidence-grade records
- Agreements, signatures, payments, maintenance and communications are recorded immutably with timestamps and attribution, so a dispute is resolved from the record.
- Document retention and deletion
- Identity documents and application evidence are retained for a defined period tied to the lawful basis for holding them, then deleted — not kept indefinitely because deletion was never implemented.
Architecture and scale
How it is built
- Domain
- The tenancy is the central aggregate. Properties, people, agreements, payments and works all attach to it, which is what makes a continuous history possible.
- Access control
- Role- and membership-based access enforced with row-level security in Postgres, with financial and identity data behind additional permissions.
- Documents
- Private storage with short-lived signed access, server-side validation of uploads, download auditing and retention policy per document class.
- Payments
- Provider abstraction covering card and bank payments with reconciliation against the tenancy ledger, and deposit-scheme registration tracking.
- Integrations
- Identity verification, e-signature, portal feeds and accounting export, each behind an interface with connection status and admin diagnostics.
- Scale
- Load is dominated by document handling and month-end payment processing rather than by concurrent browsing, so the architecture prioritises asynchronous processing and storage throughput.
Availability
Where you can use it
- Stage
- in development
- Markets
- United Kingdom, Ghana
- Web
- Not published
- Mobile
- No store listing published
Product scope, availability stage and market coverage are provisional and awaiting confirmation from the product owner.
Related
Product Design
Pick the right aggregate root and half the product designs itself
In property software, teams model the property. The property is not the thing that persists — the tenancy is. The same mistake recurs across sectors.
Identity and Trust
Identity verification is an orchestration problem, not an integration problem
Teams integrate a verification vendor per country and end up with several incompatible processes and no single audit trail. The fix is to make the sequence itself the thing you build.
Industry
Property and real estate
Long relationships, heavy documents and disputes settled by records.
Industry
Financial services and fintech
Onboarding, money movement and controls that survive an audit.
Next step
Talk to us about Domicium
Demonstrations, partnership conversations and pilot enquiries all go to a person, not an automated sequence.