VipeOS connects re-letting, resident communication, operations and portfolio reporting on one Property Graph — alongside Aareon, DOMUS or immoware24, with a transition you can stage.
6 apps · Edition Portfolio
Today
Vacancy, service and reporting keep moving while teams bridge systems by hand.
Re-letting loses its rhythm
A vacant unit moves through pricing, exposé, portals, inquiries, viewings and selection. When each step lives in another inbox or system, days disappear between handoffs and the next lease starts later than it should.
The ERP cannot carry every experience
Your ERP carries contracts, accounting and years of history. Replacing it just to improve leasing or resident service creates risk; adding another disconnected tool only gives teams one more place to reconcile.
Portfolio answers arrive too late
Owners, management and investors ask for occupancy, pipeline, service and portfolio views. The data exists, but it arrives from different systems, at different times and in formats that are hard to compare.
With VipeOS
Every unit moves through one operating layer, while the systems of record remain connected.
Re-letting moves in one flow
Reach publishes the unit and synchronises listings; Close carries inquiries, viewings and fair selection. Teams see the next action and the full path back to the asset.
Your ERP stays part of the stack
Core and Operate connect asset, service and finance context with systems such as Aareon, DOMUS, immoware24 and DATEV. You can improve the front line without forcing a big-bang replacement.
Residents get one clear door
Vipe Home gives residents and owners a focused portal for messages, documents and service access. Requests reach the right context instead of becoming another unassigned email.
Reporting starts from the same graph
Grow brings portfolio data into Portfolio Analytics, Vipe Index, ESG Reports and the Exit Room, so operating teams, management and investors can work from a clearer shared view.
The path
The apps keep the unit, the resident and the portfolio connected.
Portfolio setup
Connect the living record
Core maps assets, units, contacts and documents while Operate links the established systems around them.
Re-letting
Bring the unit back to market
Reach prepares the exposé, distributes the listing and returns every inquiry to the right unit.
Selection
Move from inquiry to decision
Close organises viewings, comparable applicant information and a fair, documented selection path.
Living & service
Keep communication in context
Home gives residents one door; Operate routes service, vendors, building records and finance context.
Portfolio
Turn operations into a portfolio view
Grow carries occupancy, performance, ESG and exit context into reporting built on the same Property Graph.
The apps
Start with re-letting or reporting, then connect the operating loop around the same assets.
- Vipe CoreOne Property Graph for assets, units, contacts, documents and the systems that already carry them.7 of 10 modules liveOpen the app →
- Vipe ReachExposés, listing sync and inquiries connected to the unit from the first publication.8 of 9 modules liveOpen the app →
- Vipe CloseViewings, applicant information and fair selection in one visible path.8 of 11 modules liveOpen the app →
- Vipe HomeA focused Resident and Owner Hub for communication, documents and service access.5 of 8 modules liveOpen the app →
- Vipe OperateService, vendors, finance context and building records alongside the existing ERP.7 of 7 modules liveOpen the app →
- Vipe GrowPortfolio Analytics, Vipe Index, ESG Reports and exit readiness from shared operating data.8 of 8 modules liveOpen the app →
Fit
Family offices & private portfolio owners
Fast decisions, direct ownership and a sharp re-letting problem. Start where vacancy hurts, then add the reporting view needed across assets and partners.
Private housing companies
Several systems and teams already carry the portfolio. VipeOS adds a connected operating layer with ERP coexistence, staged transition and portfolio-wide visibility.
Municipal companies & cooperatives
Large portfolios, longer procurement and demanding occupancy, funding and ESG requirements. The fit starts with clearly scoped processes and existing-system integration.
Funds & institutional holders
Data quality, investor reporting and exit readiness matter across mandates. Grow turns operating context into a portfolio view, often together with the appointed asset manager.
The edition
Edition Portfolio.
Portfolio is the edition for portfolio holders: re-letting in rhythm with AI price suggestion, exposé, viewing and digital selection — plus re-letting automation in the Owner Hub.
Integrations
VipeOS connects to the systems this work already runs on — each connector has its own page.
Common questions
Does VipeOS replace our ERP?
It does not have to. Aareon, DOMUS, immoware24, DATEV and other systems can remain systems of record while VipeOS connects re-letting, resident service, operations and reporting around the same assets. We define ownership of each data flow before rollout.
How do we move away from older systems?
In stages. Start with one bounded flow, portfolio or region, connect the required source data and keep the old system running where it is still needed. The Property Graph gives the new layer a stable asset model without requiring a big-bang migration.
What does re-letting in rhythm include?
Pricing context, exposé, portal distribution, inquiries, viewings and fair digital selection stay connected to the vacant unit. Reach and Close make handoffs visible; the Owner Hub can carry the recurring re-letting path around the same portfolio.
How is Portfolio priced?
The model is the Core platform at a fixed monthly price plus the apps you use, billed per unit with volume tiers. We scope the starting portfolio and integrations in an intro call, so the proposal reflects the operating flow you actually need.
Can different roles see different views?
Yes. Workspaces and role-based access can give operating teams, owners and partners a focused view of the same Property Graph. The exact reporting and data boundaries are agreed during setup, especially where several legal entities or mandates share systems.
Does this fit municipal or institutional portfolios?
The product direction fits occupancy, ESG, reporting and exit-quality needs, but rollout follows the organisation. For municipal, cooperative or regulated portfolios, we scope procurement, permissions, integrations and governance before making a delivery promise.
Next step
Put your re-letting flow on the table.
We map one vacancy cycle, your ERP landscape and the portfolio view you need — then recommend a practical starting stack.