We were on Hasura Cloud and really did not have a problem with it. But we moved away to self-hosted Hasura for more control over deployment and cost as we have 10s of same-schema MSSQL databases that we were orchestrating and the management and synchronization of metadata was becoming a bit of a pain.<p>They just announced dynamic connection routing[1] which is a feature we have sorely needed as it would allow us to run a single instance. Fantastic stuff.<p>It is marked as "cloud / enterprise" only feature. Fine. Just yesterday we began to explore moving back to the hosted cloud service to prepare ourselves for availability of the feature.<p>And then today they announce this pricing change that 10x's the amount we would pay! On top of that the max for dynamic connection routing for the Pro plan is listed at 1! What's even the point???<p>Our opinion of Hasura has always been high and we've been quick to recommend it. But with the strategy and pricing in flux it's hard to justify picking it for future API needs. They seem to pushing aggressively towards Enterprise or bust deals which is a shame because the features they are gating off behind the Enterprise wall are fundamental to many application architectures.<p>[1] <a href="https://github.com/rakeshkky/graphql-engine/blob/dynamic-connection-routing-rfc/rfcs/database-connection-routing.md">https://github.com/rakeshkky/graphql-engine/blob/dynamic-con...</a>