If I understand this correctly it's mainly a UI to create new instances of postgresql on existing platforms that offer it as a service or create clusters/databases (in the postgresql jargon) on those. Seems like the SDK is a wrapper for existing libraries to provide connection string for connecting and not much else. Is that correct?
Thanks for the question! In addition to helping with DevOps tasks, we built the infrastructure to help you securely manage your tenants in shared and dedicated instances. The shared instances have logical data separation, so there can be no data leakage. Our goal was it make it so developers did not have to worry about that infrastructure or security. - John
I'm still not sure what fortress actually does that is new.
What I'm guessing is that if you have a isolation=shared tenant you add a database to an existing postgresql cluster and if it is set to isolation=dedicated you setup a separate cluster? The clusters are setup with normal postgresql hosted solutions like AWS aurora and billed in the same way, right?
If so I don't understand why I'd use your product over any traditional IaC like CDK or terraform where I have done similar stuff (spin up multiple instances/clusters/databases based on tenants) and seems to integrate better with existing devops tooling or a workflow on top of CDK/terraform scripts that creates databases/schemas.
