> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thepublive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> Connect AXP Edge to your CDN and go live.

## Prerequisites

* Admin access to your domain's DNS / nameserver records.
* Access to your CDN or edge network configuration.
* A Publive AXP account with AXP Edge enabled for your domain. [Get AXP Edge](https://axp.thepublive.com/contact).

## Supported CDNs and platforms

AXP Edge integrates at the CDN layer, so it works with any site already served through one. All major CDNs and edge networks are supported:

| CDN / platform            | Integration guide                                             |
| ------------------------- | ------------------------------------------------------------- |
| Cloudflare                | [Deploy on Cloudflare](/axp/axp-edge/integrations/cloudflare) |
| Vercel                    | [Deploy on Vercel](/axp/axp-edge/integrations/vercel)         |
| Amazon CloudFront         | [Deploy on CloudFront](/axp/axp-edge/integrations/cloudfront) |
| Fastly                    | [Deploy on Fastly](/axp/axp-edge/integrations/fastly)         |
| Akamai                    | [Deploy on Akamai](/axp/axp-edge/integrations/akamai)         |
| F5 Distributed Cloud (XC) | [Deploy on F5 XC](/axp/axp-edge/integrations/f5-xc)           |

If your site sits behind a different CDN or edge network, AXP Edge can almost certainly still integrate. [Get AXP Edge integrated here](https://axp.thepublive.com/contact).

### Don't have a CDN yet?

[Don't have a CDN?](/axp/axp-edge/integrations/dont-have-a-cdn) We recommend Cloudflare and can help you get set up.

<Note>
  Rollback is one click: disabling AXP Edge immediately returns all traffic (including AI agent traffic) to your normal origin.
</Note>

## Go live in three steps

A high-level path from zero to live. Each step links to the detail below. Most teams are live in under two hours.

<Steps>
  <Step title="Get set up">
    Publive provides **AXP Edge enabled for your domain**, your **Edge CDS API key**, and your **backend URL** ([Contact us](mailto:support@thepublive.com), if you don't have these). You provide admin access to your CDN. Make sure `PubliveBot/1.0` and LLM user-agents (GPTBot, ClaudeBot, Google-Extended, and similar) are unblocked across your CDN, `robots.txt`, and WAF.
  </Step>

  <Step title="Deploy your integration">
    Pick the [integration guide](#integration-guides) for your CDN, add the Worker/Middleware, set the environment variables (store the API key as an encrypted secret), and attach the route. No CDN yet? [Start here](/axp/axp-edge/integrations/dont-have-a-cdn).
  </Step>

  <Step title="Verify and monitor">
    Confirm bot traffic is served by CDS and human traffic is unchanged, then use the [AXP Edge dashboard](/axp/axp-edge/dashboard) to set rules and watch agent traffic grow. Rollback is one click: disabling AXP Edge returns all traffic to your origin.
  </Step>
</Steps>

## How AXP Edge decides who gets the agent view

AXP Edge detects AI crawlers and agents using user-agent and network signals. Humans, and any traditional search bots you want preserved, are passed through to your normal site untouched.

## Bypass rules

You can exclude specific pages or sections of your site from AXP Edge optimization, so AI bots hit your unoptimized origin pages for those paths instead. This is useful for comparing optimized vs. unoptimized performance on your own domain, or for excluding pages that shouldn't be exposed to AI agents at all. Configure bypass rules from the **Content & Global Rules** section of your AXP dashboard. See [AXP Edge dashboard](/axp/axp-edge/dashboard).

<Frame>
  <img src="https://mintcdn.com/publive/KQKQ_P3CeRtmYtsj/images/axp/axp-edge-global-rules.png?fit=max&auto=format&n=KQKQ_P3CeRtmYtsj&q=85&s=2521529e139eaaffb9336401532134ef" alt="AXP Edge Global Rules tab showing default serving behaviour and URL/bot override tables" style={{ borderRadius: '0.5rem' }} width="1637" height="907" data-path="images/axp/axp-edge-global-rules.png" />
</Frame>

## Integration guides

Setting up AXP Edge yourself instead of pointing DNS at it? Use the guide for your CDN:

<CardGroup cols={2}>
  <Card title="Deploy on Cloudflare" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/cloudflare.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=cc4eadae1cfe9a4a1f4b15c42536fc21" href="/axp/axp-edge/integrations/cloudflare" width="24" height="24" data-path="images/axp/logos/cloudflare.svg">
    Worker-based routing on Cloudflare, with automatic origin failover.
  </Card>

  <Card title="Deploy on Vercel" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/vercel.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=c26be5d5ae1fc30938abda6ed8ee7d2e" href="/axp/axp-edge/integrations/vercel" width="24" height="24" data-path="images/axp/logos/vercel.svg">
    Next.js Middleware-based routing for apps hosted on Vercel.
  </Card>

  <Card title="Deploy on CloudFront" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/aws.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=635d67cccffdbbe8f0441ac38a278721" href="/axp/axp-edge/integrations/cloudfront" width="128" height="128" data-path="images/axp/logos/aws.svg">
    Lambda\@Edge routing for an Amazon CloudFront distribution.
  </Card>

  <Card title="Deploy on Fastly" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/fastly.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=8d33dbf836c835f6bff2fee63e649912" href="/axp/axp-edge/integrations/fastly" width="24" height="24" data-path="images/axp/logos/fastly.svg">
    Compute\@Edge routing for a Fastly service.
  </Card>

  <Card title="Deploy on Akamai" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/akamai.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=44990515928808e237cdc39cd82d5967" href="/axp/axp-edge/integrations/akamai" width="24" height="24" data-path="images/axp/logos/akamai.svg">
    Property Manager rules for routing on Akamai.
  </Card>

  <Card title="Deploy on F5 XC" icon="https://mintcdn.com/publive/0Cl5y4El9teWDKwm/images/axp/logos/f5.svg?fit=max&auto=format&n=0Cl5y4El9teWDKwm&q=85&s=28a284cc54e61c150f00bdc6acc68949" href="/axp/axp-edge/integrations/f5-xc" width="24" height="24" data-path="images/axp/logos/f5.svg">
    Service Policy and Load Balancer routing on F5 Distributed Cloud.
  </Card>

  <Card title="Don't have a CDN?" icon="circle-question" href="/axp/axp-edge/integrations/dont-have-a-cdn">
    Get a CDN in front of your domain, then connect AXP Edge.
  </Card>
</CardGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="AXP Edge dashboard" icon="gauge" href="/axp/axp-edge/dashboard">
    Monitor agent traffic and manage optimization rules.
  </Card>

  <Card title="Contact Support" icon="envelope" href="mailto:support@thepublive.com">
    Need help getting AXP Edge set up? Reach out to support.
  </Card>
</CardGroup>

We can also provide live assistance for setup: [contact us](https://axp.thepublive.com/contact).