It makes sense to keep track of developer accounts alongside the admin accounts you already need to manage, to make sure you can access the services you're relying on if the original developer is on vacation or leaves the company.
And once you start relying on the services that your developers are choosing and buying to run your company, you need to care about service availability and performance (as well as any financial implications if they don't meet their SLAs). You need to do initial due diligence for evaluating service and terms of service, and plan for ongoing monitoring (tools like Apigee, Mashery's API Management or APImetrics' API performance monitoring and analytics will help here, or you can use something like Azure API Management to offer approved APIs ready for developers to use).
But you want your developers involved in the technology decisions. Lawson suggests that developer buying, "can be substantially less risky because the risk is tied to the size and the scope of the project." That doesn't mean unpicking a bad decision will be painless, so whatever tools you pick to manage this trend, the first thing to do is find out what your developers are already buying for you and set policies around how that happens.
Like cloud purchasing by line of business teams, developers buying services that become increasingly strategic is a genie that isn't going back in the bottle.
Sign up for Computerworld eNewsletters.