I'm not sure I can give away the sauce yet for the actual ibrary, but the stack it creates is multiple React frontends with a Django API only backend that are a

I'm not sure I can give away the sauce yet for the actual ibrary, but the stack it creates is multiple React frontends with a Django API only backend that are all deployed to AWS. The AWS stack consists of RDS, Lambda functions for backend, S3 for media and React applications. The deployments are automated at literally every step; from AWS creation, GitHub configs to repo creation, TravisCI deployments. And yes! It is intended for dogfooding. The problem came about when I kept having to write very similar infrastructure over and over for new start ups