Today is National Pizza Party Day, and we have a couple of improvements to release.
* Cloudflares
header is now getting passed through to backend services. Since we are using Cloudflare as well, some headers usually set by Cloudflare will get overwritten with GraphCDN-specific values. If you run Cloudflare in front of GraphCDN and need access to those headers, let us know and we'll take a look if/how we can pass through the original values.
* GraphCDN joined Stripes Climate program and donates 1% of our revenue to carbon removal. See for more information
* Weekly Digest emails sometimes got stuck/congested. We fixed that bug and those digests are now getting delivered reliably.
The release included further under-the-hood improvements and preparations for soon-to-be-launched features. Stay tuned for those, you are going to 😍 them.
We're excited to announce a new Wordpress plugin that makes using GraphCDN with WPGraphQL a breeze.
The plugin takes care of invalidating the cache for any entities you update in your Wordpress installation, works with custom post types as well as taxonomies and allows you to focus on your content and not worry about your GraphCDN setup.
See for more information, as well as installation instructions. And don't hesitate to reach out via or the in-app messenger if you have any questions at all.
We're happy to release the new
graphcdn check
CLI subcommand.
Based on the analytics data GraphCDN collects for your service, we check that any breaking changes you make to your GraphQL API will not affect your users. See for the announcement blog post and for the documentation.
The next step? Opening a PR on your CI/CD workflow to call
graphcdn check
as part of your pipelines.
The GraphCDN team spent the last week in Lisbon, Portugal at an amazing onsite. (Since we are a distributed company, we're actually "on-site" when we're all together. 😊) Other than getting to know each one of us better, and working hard on the vision and mission for our company, we also shipped some improvements, fixes, and new features.
  • We have a new field called
    on the organization type, which allows you to paginate/filter through all services owned by an organization. This implements the relay-pagination spec.
  • POST
    requests with an empty body are now blocked at the edge.
  • The Forwarded headers are now appended rather than replaced
  • Requests are retried at most once to not overload your backend services.
  • We have fixed the Slack channel selector, which was not working for Slack workspaces with more than 1000 channels. We will now load all non-archived channels when loading the page. Unfortunately Slack does not implement filtering via their API 😅, which makes our UI and background logic a slight bit more complicated.
  • We now make a better attempt at removing the TLS subscription when removing a custom domain from your service.
  • We have fixed an issue where we would cache empty array root-fields
  • Set
    headers via GraphCDN edge workers.
  • The GraphCDN CLI
    command now exposes a Purging API in addition to your cached GraphQL API in version 1.11.0
  • Added a list of 3rd party subprocessors that GraphCDN uses at
  • [Private Beta]
    If GraphCDN encounters an invalid JWT, requests will be passed on to your backend service instead of being treated like an unscoped request.
We are also working on a new version of our dashboard and shipped some internal improvements and prerequisites for that. See for a sneak peek.
If you want to purge specific results based on fields and arguments passed to your queries, you can use the _purgeQueryField(fields: [QueryFieldInput!]!) mutation.
The QueryFieldInput argument will be an enum based on your schema if you pushed your schema to GraphCDN (or have introspection enabled), or a string if GraphCDN doesn't have access to your schema.
As an example, let's say you have the following query as part of your application:
package(name: "@urql/core") {
You can then target the
field and purge the above result with the following mutation.
mutation {
_purgeQueryField(fields: [
name: "package",
args: { name: "@urql/core" }
If you pushed your schema to GraphCDN, you could also use more specific mutations based on your schema definition. For example, you would also be able to use the following mutation.
mutation {
purgeQuery_package(args: [{ name: "@urql/core }])
And you can, of course, pass in those arguments via variables as well.
Up to now, GraphCDN could cache GraphQL responses up to 2MB in size. If the response size was larger than this, the response could not be stored in the cache, and any future requests would be passed on to your backend service.
We are happy to announce that we could bump this limit and can now cache responses up to 10MB in size.
You can now define a set of request headers that will cause GraphCDN to bypass the cache and pass the request on to your origin. Any request you send that includes one of those headers (e.g. a
header with any value) will not be cached.
You will see a new option called
Bypass Headers
in the cache configuration on your service dashboard.
Screen Shot 2022-01-11 at 16
However, you can also specify those headers via the
in a new
name: my-app
schema: https://end.point
originUrl: https://end.point
- name: x-preview-token
- name: some-other-token
Common use cases for this feature are preview modes for e.g. a headless CMS or specific queries where you always want to get the latest data.
See for our documentation of this feature.
Powered by GraphCDN badge
If you have this shiny "Powered by GraphCDN" badge in the footer of your website, we'll double your free monthly requests to 10M!
Copy-and-paste this HTML code into your website's footer, email us a link, and we'll unlock the extended free plan for you:
<a href="">
<img src="" alt="Powered by GraphCDN" />
We now support signing up for GraphCDN, as well as signing in, via We do
currently support self-hosted GitLab instances.
If there are other identity providers you are looking for, please let us know!
Load More