We have seen the same with our customers and our own experiences -- most teams "graduate" from a PaaS because you're locked into a set of proprietary technologies and hosting.
When they do get large enough, they leave to build their own infrastructure. Unfortunately, they have to rebuild much of the automation and user experience that a PaaS provided for them.
It's fair to call us a PaaS given our launch, but our vision is to give teams automation and collaboration in their own tooling and workflows.
We have seen the same with our customers and our own experiences -- most teams "graduate" from a PaaS because you're locked into a set of proprietary technologies and hosting.
When they do get large enough, they leave to build their own infrastructure. Unfortunately, they have to rebuild much of the automation and user experience that a PaaS provided for them.
It's fair to call us a PaaS given our launch, but our vision is to give teams automation and collaboration in their own tooling and workflows.