CUSTOMER CONTROL / SOFTWARE ACCESS
Take your software back.
Can you get your data, connect the tools you choose, and act from outside the system? We examine the access routes, costs and restrictions behind those questions.
0-10 · Higher is better
* Scores with unresolved inputs show the midpoint of their possible scores (document-based assessment). Scoring method ↗
Vendor explorer
Download data ↓Compare overall grades and six dimension scores for property-management software. Grades combine concrete answers from public documentation (including commercial and legal restrictions). Open any score to inspect its inputs and scope.
| Select | Category | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| AppFolio Property Manager ↗ | PROPERTY MANAGEMENT | ||||||||
| Entrata ↗ | PROPERTY MANAGEMENT | ||||||||
| MRI Software ↗ | PROPERTY MANAGEMENT | ||||||||
| Yardi Voyager ↗ | PROPERTY MANAGEMENT |
* Scores with unresolved inputs show the midpoint of their possible scores (document-based assessment). Scoring method ↗
A hyphen means no eligible assessment. Grades describe the licensed products and routes reviewed, not every plan or measured performance.
Your comparison
Compare documented conditions across six dimensions. The route beneath each answer matters (partner access and customer APIs can have different terms).
Select at least two vendors in the explorer to compare them here.
Access route evidence
Supporting observations about the connection methods listed so far. These route counts describe the research scope, not customer-control ratings.
Routes using credentials held by the customer
Listed route counts · Vendors with linked documentation
Routes listed without a provider review requirement
Listed route counts · Vendors with linked documentation
Routes requiring provider review
Listed route counts · Vendors with linked documentation
Connection requirements
4 vendors with linked documentationYes No- Unknown
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
Customer-held credentials can still need provider approval. Select a point to inspect the vendors at that intersection.
Routes with customer credentials →
Numbers on points show how many vendors share the same counts.
Counts apply to the listed methods. Neither axis measures record coverage or the quality of a vendor.
START WITH AN INDUSTRY
Customer credentials, partner programs and report exports can carry different conditions (even when they reach the same vendor’s data). These profiles keep the routes separate.
Yes No- Unknown
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
Yardi Voyager↗
Direct interfaces, customer-owned warehouse products and report exports are separate access paths. Their licensing and data coverage need separate checks.
Read the access reviewAppFolio Property Manager↗
API availability depends on the product plan. Customer API access and the Stack partner program have different prerequisites and costs.
Read the access reviewMRI Software↗
MRI Information eXchange supports custom APIs. Customer MIX, Partner Connect and report files are distinct routes with separate entitlements.
Read the access reviewEntrata↗
Entrata describes a partner API path and reporting products. Agreement, customer permissions and intended downstream use need to be checked together.
Read the access reviewAPI LIMITS & DATA ACCESS
How much can you extract?
Request limits and monthly allowances affect how fast you can export data or keep an integration current. Explore the published limits and how a usage-based allowance changes with your business.
Original time windows and account scope (including shared limits) are shown for each route. Values are converted to a minute equivalent; they aren’t measured throughput. Checked 2026-10-09.
Stripe allocates 500 read requests per transaction over a rolling 30-day period, with a minimum of 10,000 per month. Write requests have no allocation limit.
Standard-account allowance under the published policy. Connect platforms have separate allowances (based on connected-account transactions), and request-rate limits apply separately. Stripe documentation ↗ · Checked 2026-10-09.