API Orchestration
Success Stories

Now teams can start with a VIN, decode it to get the vehicle ID, connect to valuations, and get everything they need in one query. We can compose these proven services in ways we never could before. And considering the process would have typically required months or even a year of work from multiple engineers, Apollo Connectors saved us millions. This was monumental.

Mark Meiller

Principal Engineer of Data Services at Cox Automotive

With Apollo GraphOS and federated subscriptions, JUCR delivers seamless live updates to thousands of EV charging sessions across Europe, keeping our customers up-to-date in real time during their charging experience

If you’re a company that’s expecting to build more and scale more, but you still want the confidence that what you’re building is standardized and not slowing you down, then I would recommend you consider an Apollo GraphQL approach.

In all our previous stacks, each individual UI built their own APIs. iOS had one API, Android had another API, TV has a different API, etc. we just couldn’t scale with the business anymore. Unifying those in a single federated GraphQL API was super valuable, and something we couldn't do before.

Bruce Wang

Director of Product Platform Systems team, Netflix

Apollo GraphOS is a key platform for the development team to work softly with GraphQL. It provides a bunch of tools and APIs that allow us to establish a secure development pipeline to compose and deliver new pieces to our supergraph.

Without the supergraph, we’d still be trying to figure out how to build a user journey for the fleet business.

Stephan Lonntorp

Senior Engineering Manager at Volvo Cars

With a supergraph, we could create a single source of truth for definitions of every entity in our data model . . . eliminating a huge amount of maintenance work associated with these disparate graphs. For us, it was worth it.

Mike Byrnes

Principal Software Engineer at Priceline.com