Infrastructure

Many businesses trust PropertySync to provide a reliable, secure and performant service to store and retrieve title plant information and imagery across multiple locations between thousands of concurrent users. Our service infrastructure has been designed for high availability, redundancy and security.

Architecture

PropertySync is designed with multiple layers of functionality, covering data transfer, encryption, network configuration, and application-level controls, all distributed across a scalable, secure infrastructure.

Our architecture is comprised of the following services which are deployed in geographically redundant data centers within the Amazon Web Services infrastructure.

Portal - Web Application UI

The PropertySync Portal application is the primary interface for end-users accessing the system to perform plant searches. This application is deployed to multiple geographically diverse endpoints and served via HTTPS at https://portal.propertysync.comopen in new window.

Application API

The API application layer includes all business logic and related functionality for authenticating users, performing the various searches against plant data, tracking orders and activity of individual and groups of users and retrieving index and imagery information about given documents and other plant resources. The application API is deployed as a service layer exposing several RESTful endpoints for the various functionality required. These endpoints are consumed by the Web appllication UI, as well as various other helper services for importing and exporting data, searching data, compiling and delivering analytics analytics and a host of other services. Many of these API endpoints are also provided to customers and partners for integration into their own systems and services via our public Developer Api.

Data Storage

The data storage layer for PropertySync houses all of the plant document indexes. This is a hybrid mix of traditional RDBMS data stores, NoSQL style JSON document storage as well as proprietary indexes and storage and retrieval functions. We use binary logging against multiple geographically diverse data storage layers to support point-in-time recovery of all datasets. Additionally full data storage snapshots are retained and rotated to remote locations to ensure full recoverability during a disaster recovery incident.

Image Storage

The image storage layer houses all raw plant imagery in a hierarchical indexed structure related to entries within the data storage layer. Images are delivered from an AWS s3 CDN via the application API layer on an as-needed basis. Additional cached copies of images may be stored temporarily by the system during search transactions to support various export formats, backups, reports and image manipulation.

Reliability

We want to ensure that our services are highly available and performant during all hours of business usage by our customers. All of our services are deployed using Amazon Web Services tools and technologies to provide the highest level of security, performance and redundancy. We strive to provide 99.999% of availability during US business hours and 99.9% of 24/7 availability overall including scheduled service outages within a given month.

Service Monitoring

We currently use 3rd party service monitors to track accessibility and latency for our services. We are working to provide public access to these status pages to our customers.

Security

PropertySync is committed to providing a secure environment for our customers to store and retrieve their title plant information and imagery. We have implemented a number of security measures to protect our infrastructure and data. These measures include:

  • Data Encryption: All data stored in PropertySync is encrypted at rest and in transit using industry-standard encryption algorithms.
  • Access Controls: Access to PropertySync is restricted to authorized users only. We use multi-factor authentication to verify the identity of users and limit access to sensitive data.
  • Network Security: We use firewalls, intrusion detection systems, and other security measures to protect our network from unauthorized access.
  • Monitoring: We monitor our systems for security incidents and respond to any threats or vulnerabilities that are detected.
  • Compliance: PropertySync complies with industry standards and regulations to ensure the security and privacy of our customers' data.

Incident Response

We have incident response tasks outlined to address service availability, security and privacy issues. As part of these procedures our staff is instructed to:

  • Respond to alerts of potential issues with availability, security or privacy.
  • Determine the importance and severity of the current issue.
  • Communicate all findings regarding the current incident and consult with the development and network teams to determine which customers or services might be effected and to determine necessary action items to resolve or address.
  • Deliver notifications to any affected customers including any possible pre-determined timeline for resolution and any business related impact which may exist along with possible workaround options.
  • Plan and execute resolution options within the required timeline determined by severity of the incident.
  • Discuss and document any required prevention measures for future related incidents.

Disaster Recovery

To address information security requirements during a major crisis or disaster impacting PropertySync operations, we maintain a disaster recovery plan. The PropertySync team reviews this plan quarterly and tests selected elements at least annually. Relevant findings are documented and tracked until resolution.

Our Disaster Recovery Plan (DRP) addresses both data loss and availability disasters, which are defined as follows.

  • A data loss disaster consists of one or more of the following:
  • A complete or permanent loss of a primary data center that stores active searchable plant information including document indexes and/or images.
  • Lost ability to communicate or serve data from a data center that stores searchable plant information or document images.
  • An availability disaster consists of one or more of the following:
  • An outage greater than 10 days
  • Lost ability to communicate or serve data from a data center that stores searchable plant information or document images.

We define a Recovery Time Objective (RTO), which is the duration of time and a service level in which business process or service must be restored after a disaster, and a Recovery Point Objective (RPO), which is the maximum tolerable period in which data might be lost from a service disruption. We also measure the Recovery Time Actual (RTA) during Disaster Recovery testing, performed at least annually.

PropertySync incident response, business continuity, and disaster recovery plans are subject to being tested at planned intervals and upon significant organizational or environmental changes. The PropertySync team reviews the results of these tests and exercises and updates the plans as needed.

Last Updated: