Dependencies
Power and cooling held as a dependency chain on the equipment record. What is not recorded is shown as unknown, never as safe.
Starting point · Run critical property
Run critical property with nothing left to memory.
Dependencies made visible, changes and permits controlled, evidence kept on the record — and AI agents that act only with scoped, expiring authority.
For operators of data centres, infrastructure and buildings where a missed step has real consequences.
What you switch on first.
Controlled change
Permits, lock-out/tag-out, method statements and a change calendar — prepared by the team or by agents, approved by a person.
Governed AI
Each agent has an owner, a purpose, an expiry and a list of exact actions. When risk rises, authority drops back to read-only.
From a planned change to filed evidence.
How one maintenance window runs.
- Planned. The window is placed on the change calendar; clashes with other work on the same dependency chain are shown.
- Prepared. Method statement, permit and lock-out steps are drafted and checked against the equipment and the people involved.
- Approved. A named person approves. Agents can prepare and remind; they cannot approve permits or silence alarms.
- Evidenced. Completion, readings and photos are filed on the equipment record; an incident opens a review with its evidence attached.
Typical first use cases.
Chosen with you in the Scope phase.
- Equipment topology and dependencies for one site
- Permits, lock-out/tag-out and change calendar
- Compliance duties with their evidence
- Agents with scoped authority, starting read-only
Data centre operations · Infrastructure asset operations · Portfolio and asset management
How a first deployment runs.
One portfolio, a few use cases that matter, and the people who own them. Each phase says what we do and what we need from you.
- Scope. Choose one portfolio and the first use cases, and name the person who owns each one. What we need from you: A list of the buildings in scope and a sponsor who can decide.
- Connect. Import buildings, units, assets, leases and documents, and connect the systems you keep. What we need from you: Your current registers and spreadsheets, and access to the systems you want connected.
- Configure. Set up workspaces, roles, approval steps and the country rules that apply to your properties. What we need from you: Who may see, approve and pay what — written down once.
- Go live and review. Your team runs the first workflows. Agents stay off until you turn them on, and every step is logged. What we need from you: Time from the people who will use it, and a review of data quality and the next use case.
Phases, not promises: timing depends on your data, your systems and the scope, and is agreed with you before work starts.
Available today. Configured for you. Connected. Governed.
What Residention does out of the box, what is set up for your portfolio, how it connects to your systems — and what always stays with your people.
Available today
- Property, building, floor, space and asset records
- Work orders, planned maintenance, inspections and compliance evidence
- Service desk with resident and supplier portals
- Lease register, invoices, approvals, journals and VAT per administration
- Maintenance plans, budgets, CapEx and projects
- Document index with versions, review and in-browser viewing
- smartAI assistance that shows its sources
Configured for your portfolio
- Organisations, portfolios and workspaces
- Roles, permissions and approval steps
- Country rules — VvE, HOA, WEG or Comunidad — currencies and dates
- English, Dutch, German and Spanish
- Custom fields, registers and inspection templates
Connected through integrations
- Registers, finance, calendar, mail, directory and meter connections listed on the integrations map
- File exchange for maintenance plans, project schedules and BIM (IFC, COBie)
- Excel, CSV, email intake and webhooks for everything else
- Building systems such as BMS and sensors: a read-only layer in development — Residention never controls plant
Always governed by your people
- Money, contracts, complaints, deletions and outside messages need a person
- Agents act only with an owner, a purpose, an expiry and exact permissions
- Every action logged with who, when, why and the evidence
- Access resolved per workspace; a request without scope returns nothing
Not claimed: universal live BMS or sensor connectivity, full BIM interoperability, real-time simulation, predictive maintenance or autonomous technical control.
See every integration · Security and governance · Trust Centre · Follow one day in one building
See it on your own portfolio.
Book a demo and we will walk through these workflows with your own buildings in mind.