Because Foundry is a cloud Formation Template that is installed within each customers AWS Instance, it is inherently "back up" because of the fact that a FULL copy (all code and configuration) co exists within the Customer Instance and the Foundry root instance. What's more, a FULL copy exists in every customers Account so in a very real the number of installed Foundry instances represent the number of "hot" backups.
That being said, we encourage our customer to implement the AWS Back ups Services (https://aws.amazon.com/backup/) so that their specific data is backed up across regions.
The Source code for Foundry exists in two different repositories. 1) within the bitBucket Git repository and 2) compiled code within the S3 bucket that is accessed by the Cloud Formation Template.
While the predominate amount of customer data is housed within the Customers Account, and thus falls to them to implement best practices around data backups, ThingLogix does maintain a centralized database of Customer Accounts and usage. These RDS and and Dynamodb tables are backup on a daily basis using the AWS Back up service (https://aws.amazon.com/backup/)