> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/concepts/flagship-edge-worker-integration.md).

# Flagship Edge Worker Integration

Welcome to the Flagship Edge worker Integration Hub! This guide provides a high-level overview of how to integrate **Flagship feature flagging and experimentation** into your edge computing stack using:

* [Cloudflare Workers](/server-side/concepts/flagship-edge-worker-integration/flagship-cloudflare-worker-integration.md)
* [Fastly Compute@Edge](/server-side/concepts/flagship-edge-worker-integration/flagship-fastly-computeedge-integration.md)
* [Vercel Edge Functions](/server-side/concepts/flagship-edge-worker-integration/flagship-vercel-edge-function-integration.md)

Whether you're optimizing performance, personalizing user experiences, or running A/B tests at the edge, Flagship enables you to make real-time decisions closer to your users.

***

## Why Edge + Flagship?

* **Ultra-low latency**: Serve personalized content instantly from the edge.
* **Resilient architecture**: Avoid centralized bottlenecks by caching bucketing data locally.
* **Scalable experimentation**: Run feature flags and A/B tests without sacrificing performance.

***

## Integration Highlights

| Platform                  | SDK Mode         | Bucketing cache           | Analytics Support |
| ------------------------- | ---------------- | ------------------------- | ----------------- |
| **Cloudflare Workers**    | `BUCKETING_EDGE` | KV Storage or Local JSON  | ✅ Yes             |
| **Fastly Compute\@Edge**  | `BUCKETING_EDGE` | KV storage or Local JSON  | ✅ Yes             |
| **Vercel Edge Functions** | `BUCKETING_EDGE` | Edge Config or Local JSON | ✅ Yes             |

***

## Prerequisites

* A Flagship account with API credentials
* Node.js (v18+) and Yarn (v4+)
* Platform-specific CLI tools (e.g., `wrangler`, `fastly`, `vercel`)
* Bucketing data from [Flagship CDN](https://cdn.flagship.io)

***

## Next Steps

Choose your platform to dive into the full integration guide:

* [Cloudflare Worker Integration](/server-side/concepts/flagship-edge-worker-integration/flagship-cloudflare-worker-integration.md)
* [Fastly Compute@Edge Integration](/server-side/concepts/flagship-edge-worker-integration/flagship-fastly-computeedge-integration.md)
* [Vercel Edge Function Integration](/server-side/concepts/flagship-edge-worker-integration/flagship-vercel-edge-function-integration.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/server-side/concepts/flagship-edge-worker-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
