Opurix

Opurix

Autonomous Property Operating System

The operating layer for accommodation.

System representation: property operations connect through the Opurix operating layer to residents.

The Shift

Property operations are fragmented.

Operational areas
  • Property
  • Rooms
  • Residents
  • Payments
  • Maintenance
  • Communication
  • Staff
  • Documents
  • Occupancy
The shift
  1. disconnected workflows
  2. manual coordination
  3. Opurix
  4. one operating layer

The Opurix System

One system. Every property operation.

OpurixThe Operating System

  • Property

    Properties · Rooms · Beds · Availability · Occupancy

  • Residents

    Residents · Profiles · Admissions · Stay · Communication

  • Finance

    Payments · Collections · Ledger · Adjustments · Reversals

  • Operations

    Requests · Maintenance · Transfers · Checkout · Calendar

  • Resources

    Staff · Inventory · Documents · Notifications

  • Autonomy

    Workflows · Automations · Exceptions · Approvals · Activity

  • Intelligence

    AI · Insights · Reports · Analytics

  • Governance

    Roles · Permissions · Audit · Settings

How Opurix Operates

Operations that move themselves forward.

Core operating cycle
  1. 01

    Observe

    Understand what is happening.

  2. 02

    Understand

    Interpret the operational situation.

  3. 03

    Predict

    Identify what may need to happen next.

  4. 04

    Act

    Coordinate the appropriate operational action.

  5. 05

    Verify

    Confirm the outcome.

  6. 06

    Optimize

    Use the result to improve the next operation.

Workflow examples

Vacancy

  1. acquisition workflow
  2. follow-up
  3. occupancy update

Maintenance issue

  1. understand
  2. coordinate
  3. track
  4. update

Payment workflow

  1. detect
  2. communicate
  3. follow up
  4. record outcome
The autonomous principle

Opurix is built to take care of routine property operations automatically, while keeping the owner in control of important decisions.

Opurix handles authorized routine work and brings decision points to the owner when required.

  1. Something happens
  2. Opurix understands it
  3. Checks the configured rules
  4. Takes the permitted action
  5. Verifies the result
  6. Records what happened
  7. Informs the owner when required

The owner remains in control of decisions that affect money, resident status, exceptions, or other sensitive property operations.

The autonomy boundary
  • Automate routine work.
  • Ask the owner for important decisions.
  • Stop when the system cannot safely proceed.
Routine operations

Opurix can autonomously coordinate routine workflows such as:

  • Routine resident communication
  • Admission information collection
  • Payment reminders
  • Request acknowledgement
  • Request categorization
  • Request routing
  • Routine status updates
  • Operational record keeping
  • Activity recording
Where autonomy applies

  • Admissions

    Processes admissions within configured rules and requests approval where required.

  • Payments

    Tracks due and overdue schedules, runs configured reminders and escalation, records activity, updates status on confirmation, and escalates when intervention is needed.

  • Room / occupancy

    Updates occupancy state only from valid workflow events; it does not arbitrarily change resident status or room allocation.

  • Move-out / settlement

    Can intake requests, verify resident and payment context, prepare settlement by configured rules, and complete approved workflows. It does not independently decide exceptional compensation, losses, or discretionary deductions.

Where approval may be required
  • Admission approval
  • Room transfer approval
  • Move-out / final settlement approval where configured
  • Exceptional financial decisions
  • Exceptional compensation or deductions
  • Sensitive operational decisions
Exception handling

When something falls outside configured rules, or safe completion is uncertain, Opurix does not guess.

  1. Stops
  2. Explains the issue
  3. Requests human intervention
The core promise
  • The owner remains in control of operational boundaries and sensitive decisions.
  • Opurix handles authorized routine operations end to end.
  • Opurix asks when a human decision is required.
  • Opurix stops at boundaries and records what happened.

That is Autonomous Property Operations.

Human + Opurix

Autonomous does not mean uncontrolled.

Core operating relationship

  1. Owner decides

  2. Opurix operates

  3. People / systems execute

  4. Opurix verifies

  5. Owner sees the result

Humans handle decisions and exceptions; Opurix handles repetitive operational coordination.

The owner controls the boundaries

The owner controls the boundaries of autonomy.

Depending on the property's configuration, an operation may:

  • Run automatically
  • Require approval
  • Notify the owner
  • Escalate to staff
  • Stop and request intervention

Different properties may therefore configure different autonomy boundaries.

The owner's new role

The owner should not have to manually perform every operational task. Instead, the owner primarily sees:

  • What is happening
  • What Opurix has already handled
  • What needs my approval
  • What needs my attention
  • What failed or could not be completed
  • What has been recorded

“Oversee the property and make the decisions that matter.”

The Two Interaction Layers

One operating system. Multiple ways to interact.

Core structure

Owner / operator / staff

Dashboard + WhatsApp

Opurix

Resident

WhatsApp-first experience

  • Admissions
  • Requests
  • Maintenance
  • Payment communication
  • Notifications
  • Status updates
01The interface
Opurix WhatsApp

The autonomous property communication & operations interface.

A natural-language operational interface connected directly to the Opurix property operating system.

02The two sides
Resident WhatsApp

Residents and applicants interact with the property naturally through WhatsApp, without a separate app.

Owner / operator / staff WhatsApp

Owners and operators use WhatsApp to read operational context and initiate authorized actions without workflow friction.

Natural-language requests do not bypass permissions; Opurix evaluates role, context, and operational state before any action.

Same system, different authority
  • Residents cannot gain owner-level access by phrasing.
  • Cross-property access requires explicit authorization.
  • The WhatsApp layer enforces the same boundaries as Opurix.
03Control & boundaries
Autonomous does not mean uncontrolled

Can be autonomous

  • Routine communication
  • Payment reminders
  • Request categorization
  • Admission information collection

May require owner approval

  • Room transfer
  • Move-out
  • Policy exceptions

Human review

  • Exceptional financial settlement
  • Unusual or conflicting information
  • Risk-sensitive operational decisions

Behavior follows configured policy, permissions, and safe-stop rules.

Opurix WhatsApp turns everyday property communication into controlled operations at system level.

Occupancy Intelligence

From occupancy numbers to occupancy intelligence.

Capacity, availability, upcoming vacancies, demand, resident movement, utilization, renewal opportunities, and vacancy risk connect into one occupancy intelligence.

Occupancy signals
  • Capacity
  • Availability
  • Upcoming vacancies
  • Demand
  • Resident movement
  • Utilization
  • Renewal opportunities
  • Vacancy risk

Occupancy intelligence

Opurix Intelligence

  • Insights
  • Summaries
  • Predictions
  • Suggested actions
  • Operational understanding

Autonomous Activity

UnderstandActVerify

  1. Payment reminder sent
  2. Admission follow-up initiated
  3. Maintenance workflow coordinated
  4. Approval requested
  5. Result verified

Autonomous Activity represents actions Opurix is authorized to perform within configured rules. Intelligence itself does not grant authority, and a prediction does not automatically become an action.

Verify + record

Autonomous action is not complete simply because Opurix initiated something.

  1. Act
  2. Verify
  3. Record
  4. Inform when required

Opurix maintains operational history and makes completed activity visible to the owner.

  • Reminder sent
  • Admission information received
  • Payment confirmed
  • Request created
  • Request assigned
  • Request resolved
  • Approved room transfer processed
  • Move-out processed
  • Receipt generated
  • Autonomous action completed

The Ecosystem

Connecting property supply with resident demand.

Property owners / operators

property supply

Opurix

acquisition · operations · occupancy intelligence

Residents

demand · discovery · stay

Built for the Property Business

Designed for managed accommodation.

Hostels, PGs, and Co-living are the core domain today.

Managed accommodation
  • Hostels
  • PGs
  • Co-living
Core todayFuture expansion

The Evolution — Vision

From operating properties to powering modern living.

  1. V1Autonomous Operations

    Run the property.

    Opurix connects autonomous property operations, property intelligence, network coordination and property ecosystem capabilities into one connected operating system that helps owners manage operations and grow their business.

  2. V2Property Intelligence

    Connect properties with resident demand.

    Opurix extends property intelligence to resident browsing and discovery, allowing residents to explore available accommodation details such as building, floor, room, bed and food menu where available. This helps owners improve property visibility, resident reach and occupancy opportunities.

Connect

The operating layer for accommodation.

Opurix is building a more autonomous way to operate property.

Explore the System