Skip to content

Verified routes

Every destination is named, placed and opened before launch.

The public site carries three journeys out to the software you already run. Each route is checked against your live account, not assumed from a vendor name.

Figure 01Routes out of the site

A practical model

Three honest levels of connection.

The right answer is the simplest level that gives you the experience you need and is genuinely supported by your account.

  1. 01

    Verified links

    Resident portal, owner portal, vacancies and applications. Checked on real devices while signed out, and rechecked after any platform change.

  2. 02

    Hosted components

    A supported listing or application component from your platform, placed inside your design and styled to it as far as the vendor allows.

  3. 03

    Custom connection

    A scoped data connection for accounts that permit one. Separate discovery, separate agreement, no promise made before the account is checked.

The limit of a name

Named systems, checked against your own account.

No vendor partnership is implied. Software names appear as text because that is what they are to this website: destinations we verify, not partners we represent.

Systems clients name most often

Buildium, AppFolio, DoorLoop and others

Product names describe systems a client may already use. Access and implementation options vary by vendor, product and account.

Before anything is promised

What we check.

Checked before launchFour checks
  • Devices

    Every route is opened on a real phone and a real desktop browser, in the state a resident or an owner will meet it.

  • Account

    Capability is confirmed against your own account. A product name on a vendor page is not evidence that your plan supports it.

  • Current

    Links are checked again after launch, so a portal that moves does not quietly become a dead page.

  • Labelled

    Anything shown as a demonstration is labelled as a demonstration, on the page where it appears.

Bring the software you already run.

We map the portal, listing and application journey before recommending how each connection should work.