How Vuetify Serves Millions of Developers on a Lean Team Using Cosmic

The team behind four million monthly downloads

Vuetify has grown, since its founding in 2016, into one of the leading component libraries for building Vue applications. The package recorded 4,114,254 npm downloads in the 30 days ending August 3, 2026. It is led by founder and CEO John Leider, and the team's focus has always been on building systems that are intuitive and easy to use.

When Vuetify went looking for a content API, they held their own tooling to that same standard.

The problem: a slow Shopify back end and content living in the codebase

In early 2020, Vuetify was dealing with two things at once.

The first was the online store. It was completely integrated into Shopify's back-end platform, and getting that API to communicate with the front end of the website was far too slow. Rendering a page required too many queries.

The second was the cost of growth. Vuetify's rapid expansion left the team managing all different kinds of documents, affiliate links, and sponsors inside their original code base. Every content update was a code change, reviewed and deployed like a feature. For a team whose actual product is a component library, that was quickly becoming sub-optimal.

Vuetify needed an API that matched their appreciation for intuitive design and included the flexible features they required. After evaluating their options, nothing seemed like the right combination of those values, except for Cosmic.

The result: 300-400 ms down to about 50 ms

It was literally 10 to 15 minutes from taking the SDK, to getting the data I needed, to consuming it. We cut our server response time down from 300-400 ms to about 50 ms. Instead of needing to query the Shopify API, now we only need to query Cosmic. The baseline just works out-of-the-box, and there's considerable more information and documentation if you need it.

John Leider, Chief Executive Officer, Vuetify

Three concrete outcomes sit in that quote:

• Server response time dropped from 300-400 ms to about 50 ms. Measured against the top of the original range, that is roughly an 85% reduction.
• Integration took 10 to 15 minutes, from installing the SDK to consuming live data on the front end.
• One API replaced two. Product content that previously required Shopify API calls now comes back from a single Cosmic query.

The full story is on the Vuetify customer page.

Why Cosmic fit

The API surface matched the existing stack. Cosmic exposes a REST API and a JavaScript SDK, both of which drop into Vue and plain JavaScript projects without ceremony. There is no proprietary runtime to adopt, no separate deployment layer, and no framework requirement.

The team models its own content. Object types and metafields are defined in the Cosmic dashboard, so adding a field to a sponsor record or restructuring a document type does not require a developer or a release.

Fewer round trips per page. Consolidating content behind a single API removed the multi-query pattern that made the original integration slow. That consolidation is where the 50 ms figure comes from.

What Vuetify keeps in Cosmic

Cosmic holds the content that used to be split between Shopify's back end and Vuetify's repository: store and product content, sponsor placements, affiliate links, and the assorted documents a fast-growing open-source project accumulates.

Moving that material into a content API changes the unit of work. Adding a sponsor or correcting an affiliate link becomes a dashboard edit that is live immediately, with no pull request, review cycle, or deploy attached to it.

What the integration looks like

Reading content from Cosmic in a Vue or Nuxt project takes a few lines:

That is the entire integration surface. The SDK handles authentication, query construction, and typing of the response. There is no CMS runtime to host and no custom content server to keep alive.

Why this pattern holds for developer-facing teams

Vuetify's setup generalizes well to any project where the content and the code evolve at different speeds. Documentation, changelogs, sponsor pages, and marketing copy all change more often than the library itself, and each of those changes carries no engineering risk. Routing them through a content API keeps them out of the release process, which frees maintainer time for the library.

Open source has a particular version of this constraint. As John Leider put it in his developer spotlight interview way back in 2019, the hard part of OSS is that "the supply does not always meet the demand," which forces teams to be efficient about where their hours go. Content operations are a good place to reclaim some.

Start building

Cosmic is free to start: 1 Bucket, 2 team members, and 1,000 Objects on the Free plan, with no credit card required.

• Start building free
• Read the Vuetify customer story
• Browse the JavaScript SDK docs
• Book 20 minutes with our CEO