Open your GraphCDN dashboard and you will see something new: organizations. They allow you to group multiple services under one umbrella with consistent access control, billing and management.

We have automatically created organizations for all of your services, but you can of course also create a new one for your company specifically:

Instead of the old, tedious way to configure caching per GraphQL type or field, we now have cache rules!

Head over to the "Rules" tab in your service's dashboard and you will see your first rules already:

To upgrade your graphcdn.yml, simply run graphcdn pull and we will automagically rewrite your cache configuration into the new rules!

Some GraphQL APIs rename the root type names from the standard "Query", "Mutation" and "Subscription" to something else like:

schema MySchema {
  query: RootQuery
  mutation: RootMutation
  subscription: RootSubscription
}

We now handle this case well in the UI, showing you "RootQuery" instead of relying on the standard root type names!

Rather than linking out to Notion, our docs are now on the website at https://graphcdn.io/docs! 🎉

You can now create services from the CLI by running a single command and answering a handful of questions:

$ npm init graphcdn
# or if you're using yarn
$ yarn create graphcdn

This will do everything you need to do to get started with GraphCDN: 

1. Install the graphcdn CLI
2. Create a graphcdn.yml file
3. Push it to GraphCDN.

One of our most highly requested features just landed: custom domain support! You can now assign a custom domain to your service, which can be used instead of your <name>.graphcdn.app URL. This is particularly useful if your users authenticate with cookies.

Head to your service's settings, enter your preferred custom domain and follow the instructions to set the correct DNS records: 

The Admin API, which you use to purge data, has moved to a new location in order for us to make it even faster. Moving to the new location should take a handful of minutes at most: The only thing you have to do is change the URL you send requests to: instead of https://graphcdn.io/api/management/[name], send them to https://admin.graphcdn.io/[name]. That's it!

We'll keep the old path around for two months and will notify any customers still using it in a month directly.

We had a bug where any query that had a scope set would not be cached at all for public users.

While the cache for public users should not be shared with authenticated users in that case, the query should still be cached for them. We've now resolved those issues and the caching works as it should again!

We've been dreaming of this feature ever since we first started building GraphCDN so we're very excited it's finally here!

How it works

{
  "user": {
    "id": 5,
    "name": "Peter Pan"
  }
}

mutation {
  editUser(id: 5, name: "Saint Peter") {
    id
    name
  }
}