What to do about it
Three things worth doing now, none of them involve panicking.
Stay model-agnostic on infrastructure. If your architecture can swap the underlying model without a rewrite, you are insulated from a lot of vendor risk. This is good engineering anyway. Abstract your integrations. Do not build your differentiation into a wrapper around one provider's API.
Go deeper on domain. The labs will go wide. They will offer services across every vertical because they have to justify the team size. A boutique studio can go narrow, which means going deep. Depth in one sector, one type of problem, or one stage of the product lifecycle is defensible. Width is not.
Make the relationship the product. This sounds soft, but it is not. The highest-value thing a studio can do is become the organisation that a founder or CPO calls before they write a brief. That positioning is not built with a capability deck. It is built over years of honest conversations. No lab is going to out-relationship you if you have been in the trenches with a client through three product cycles.
The labs moving into services is real. It will reshape the market. Some studios will not survive the adjustment. But the ones that treat this as a forcing function to get sharper, not broader, will come out with stronger positions than they had before.