Update blog post on state of GraphQL gateways with the new bench website (#6943)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: kamilkisiela

packages/web/docs/src/app/blog/(posts)/state-of-graphql-gateways-in-2023/page.mdx

@@ -13,6 +13,17 @@ import { Callout } from '@theguild/components'
 The GraphQL ecosystem is growing rapidly, and solutions to complex problems are more accessible than
 ever before.
 
+<Callout type="info" emoji="🚀">
+  Since publishing this research, we released [**Hive
+  Router**](https://the-guild.dev/graphql/hive/blog/welcome-hive-router) - a high-performance,
+  open-source GraphQL federation gateway.
+
+Hive Router outperforms other leading gateways across RPS, latency, and resource usage.
+
+👉 See the [benchmark results](https://the-guild.dev/graphql/hive/federation-gateway-performance).
+
+</Callout>
+
 One of the most common questions about GraphQL is how to extend or enrich it. This can be achieved
 by adding custom flows, securing your `/graphql` endpoint, improving performance through caching,
 orchestrating upstream calls for distributed GraphQL, or monitoring and tracing it.
@@ -24,6 +35,11 @@ the following problems.
 exploring, and creating a report on the state of GraphQL gateways in 2023. We compared, tested, and
 benchmark various open-source solutions, and we'd like to share our process thus far.**
 
+<Callout type="info" emoji="📊">
+  Prefer numbers? See the live, reproducible benchmark (RPS, p95/p99, CPU, memory): [GraphQL Gateway
+  Performance Benchmarks](https://the-guild.dev/graphql/hive/federation-gateway-performance).
+</Callout>
+
 <Callout type="info" emoji="❣️">
   We would like to thank our partners and customers who took part in that journey!
 </Callout>
@@ -93,8 +109,9 @@ between GraphQL gateways:
 4. We tracked all available vitals and metrics, such as network traffic, CPU, and RAM.
 5. We tested different use cases to simulate real-life scenarios with different flows, such as peak
    times or upstream server delays.
-6. We are running all scenarios for every change, and have a complete overview of the results and
-   the stats of every gateway.
+6. We are running all scenarios for every change, and maintain a **complete, live overview of
+   results** at <a href="https://the-guild.dev/graphql/hive/federation-gateway-performance">the
+   benchmark dashboard</a>.
 7. We are running Rust-based servers for the subgraphs implementation, to ensure it's never becoming
    a bottleneck.
 
@@ -129,6 +146,9 @@ encourage developers to help us with the following:
 
 ## The Numbers
 
+For up-to-date results across scenarios, use the
+[live benchmark website](https://the-guild.dev/graphql/hive/federation-gateway-performance).
+
 ### `constant-vus-over-time`
 
 > [You can find here the latest results, report and statistics](https://github.com/the-guild-org/gateways-benchmark/blob/main/federation-v1/scenarios/constant-vus-over-time/README.md#overview-for-constant-vus-over-time)