Skip to content

Software & AI Guides

How we research these profiles

Every profile is a research-based assessment built from the vendor's own public pages. None is a hands-on review, and no vendor paid for or reviewed its profile.

Where the facts come from

Primary sources only for anything about access, plans, or capability: product and pricing pages, developer documentation, help centers, release notes, dated announcements, official marketplaces, and security, privacy, and AI documentation. Third-party reviews can suggest questions to ask; they are never the source for API access, plan entitlements, or what a feature does.

Every material claim is stored with an ID, the platform and product it applies to, the source URL, title, and publisher, the date the page shows, the date we checked it, the plan or region it covers, and its two labels. The profile, the library, and the comparison all read the same records, so a fact cannot say one thing on one page and another elsewhere.

We research with AI assistance and read the vendor's pages ourselves. Nothing on these pages is a hands-on review unless a feature says “Independently tested,” and that label requires test evidence on file. As of today, no feature carries it.

Two separate labels

How we know something and whether you can use it are different questions, so they never share a label.

Evidence: how we know

Evidence: Vendor states
Said on the vendor's marketing, pricing, or announcement pages.
Evidence: Documented
Described in the vendor's technical, developer, help, or release documentation.
Evidence: Independently tested
Used and checked by EmpowerFrame, with test evidence on file.
Evidence: Not publicly confirmed
Not found on the public pages checked. This does not mean unsupported.

Availability: can you use it today

Availability: Generally available
The vendor says customers can use it now, without a named plan limit.
Availability: Plan or add-on dependent
Available on some plans, tiers, or as a paid add-on.
Availability: Limited rollout
Released to some accounts, behind a feature flag, or in stages.
Availability: Beta or pilot
Labeled beta, pilot, or early access by the vendor.
Availability: Announced
Said to be coming. An announcement date, not an availability date.
Availability: Retired
Removed or replaced.
Availability: Unknown
The pages checked do not say.

Rules we hold ourselves to

  • “No public documentation found” does not mean “unsupported.” Unknowns render as unknown, never as a red cross.
  • When sources conflict, we show both. Product-specific technical documentation outranks marketing for technical details.
  • We record the announcement date, the release or effective date, and our verification date separately. A newer announcement can set an announcement date without proving every customer has the feature.
  • An old announcement is not “recent” because we found it recently. We search a recent window first, then broaden.
  • We name an authentication method only when the vendor documents it. An API is an interface; OAuth, API keys, and client credentials are ways to authorize it.
  • An AI assistant connector, including an MCP server, does not mean every field or action is reachable. We record who runs it, how it is authorized, what it can do, and whether it asks before changing anything, where documented.
  • We do not infer Zapier, Make, or Power Automate support from the existence of an API, and we never recommend undocumented or private endpoints.
  • Model providers are named only when the vendor documents them.
  • No star ratings, scores, overall winners, customer outcomes, or performance figures of our own. Vendor statistics are not repeated as fact.
  • No vendor paid for, sponsored, or reviewed a profile. EmpowerFrame has no partnership with the vendors covered here, and names a product in text when its logo terms have not been reviewed.

How profiles stay current

Access and AI facts, the ones most likely to change, are rechecked monthly. The whole profile is reviewed quarterly, and sooner after a major release or a change to a vendor's access policy. When a review date passes without a recheck, the profile shows a visible “Needs recheck” label until someone verifies it.

Each profile shows three dates: when it was first published, when its facts or advice last changed in substance, and when it was last verified. A routine rebuild of the site changes none of them. A person reviews and approves every substantive change before it is published.

Found something wrong or out of date? Email hello@empowerframe.com with the page and a source. Vendors may send corrections the same way; they are checked against the vendor's own public documentation like everything else.

A manager reads a prepared document at her desk with a pen in hand, checking it line by line, while a colleague across the desk listens. Apartment buildings are visible through the window behind her.
Illustrative AI concept. The people shown are fictional.

Coverage, and what comes next

The first profiles cover four rental management platforms and four association management platforms. Products are grouped by their documented audience and operating role, so systems built for management companies are kept distinct from tools mainly for boards, self-managed associations, communications, or residents. A product can carry more than one audience.

Queued for research, with no profile yet: Yardi Voyager, Yardi Breeze, RealPage OneSite, Entrata, MRI residential management products, Propertyware, DoorLoop, TownSq, Condo Control, PayHOA, Rentec Direct.

Back to the library

Next step

If your question is about your own setup, that is a conversation, not a profile. Tell us what keeps getting stuck.