thanks for the feedback. you're not alone with that concern and it's something we thought a lot about in designing our infrastructure. we approached the problem in a few ways. 1) building as much of our technology on top of existing open source software. that way if you choose to move to a new product, your data is compatible and the transition will be much simpler. 2) making much of the infrastructure component based, so that you don't need to use everything all at one. you'll be able to slowly migrate data from existing services into our infrastructure. 3) your data will always be your own and exportable for you if you so choose. Backyard came out of our own experience at different startups. we spent valuable early engineering cycles setting up infrastructure, much of the time just recreating something that many other people had already built. so we understand the concerns about entrusting core pieces of a technology stack to a thrid-party. we plan on working closely with our users to help adress those concerns.