[mithunshanbhag]

Thanks.

1. Does your team/org maintain a central diagram repository? Or do team members use their diagram tool of choice and then export diagram into a central doc library (e.g. github markdown)?

2. The short-term plan is to add more diagram templates (e.g. VPCs, K8s clusters) to help folks author complex architectures quickly.

3. There are plans to release a paid enterprise version later in the year with features like SSO, customer-managed-encryption-keys, customer-managed-storage, team collaboration etc.

Overall, CloudSkew will remain focused on cloud diagram only.

[chessmango]

1. Yes/no - my own team is more the latter as I'm more customer-facing and lone-ranger-y, but other teams do a lot more collab and keep things central. As far as I'm aware though, it's a bit of a mixed bag, so getting to the point where we're all on the same page would be fantastic.

2. This sounds great. I like the k8s angle particularly as well - I have yet to find much useful in that area, so having a service that's good at it would be wonderful.

3. This I'd imagine would be end-game at AWS. Specifically ability to handle own storage and keys would be an immediate sell here. We've just taken on Slack Enterprise Grid for basically this (granted this was a 2-way deal: https://www.theverge.com/2020/6/4/21280829/slack-amazon-aws-...) so clearly we're up for it :D

I get the focus though. Seems like a good opportunity to set yourself up as best-in-class for this type of thing. I'll certainly be using CloudSkew for anything I need privately. :)

[mithunshanbhag]

Thank you for the pointers! This is great info.

Also, please feel free to file feature requests or bugs/issues over on github: https://github.com/cloudskew/cloudskew/issues