Queue-it in Akamai Property Manager: Simpler deployment, less maintenance

Queue-it has long integrated with Akamai through the EdgeWorkers Connector, giving customers a fast and secure way to orchestrate traffic at the edge. But keeping that integration up-to-date meant provisioning your own EdgeWorker and upgrading with each new connector version, an ongoing job that fell on your team.

With the release of Akamai Visitor Prioritization Powered by Queue-it, that setup and maintenance work is gone.

Queue-it is now available through a native behavior in Akamai Property Manager, automatically maintained and updated by Queue-it. It's built to be just as simple and low-maintenance as Akamai's Visitor Prioritization Cloudlet (VPC), but designed for organizations who need more advanced traffic control, fairer waiting rooms, and richer traffic insights.

Akamai Visitor Prioritization Powered by Queue-it is a new, dedicated behavior in Akamai Property Manager that lets you integrate Queue-it without creating or managing your own EdgeWorker. 

Instead, the behavior invokes an EdgeWorker that Queue-it builds, deploys, and maintains on your behalf. The behavior sets the necessary Property Manager variables and executes the Queue-it EdgeWorker automatically. 

Because Queue-it hosts and controls the EdgeWorker bundle, every customer using the behavior automatically benefits from new capabilities and fixes as we ship them. Queue-it rolls out changes gradually through a staged canary-to-stable deployment process, validating each release on a small slice of traffic before it reaches everyone. That means updates reach you continuously and safely, without any action needed from your team.

• Easier deployment: Add Queue-it in minutes using a pre-built Property Manager behavior, with no EdgeWorker to deploy or maintain.
  
  
• Reduced operational overhead: Queue-it manages the underlying integration, including updates and maintenance, so your team spends less time supporting it.
  
  
• Lower integration costs: No customer-owned EdgeWorker is required to run the integration.
  
  
• Native BYO CDN support: Keep the waiting room on your own domain by default, without a separate integration effort to route traffic through your existing CDN setup.
  
  
• Built-in observability: The behavior exposes status and result variables, so you can monitor integration health, surface errors in response headers, or feed them into your own DataStream 2-based logging.

Setting up Akamai Visitor Prioritization Powered by Queue-it feels less like integrating a third-party tool and more like switching on a native Akamai capability. 

There's no code to write and no EdgeWorker for your team to build or maintain: Queue-it handles that layer entirely, so your involvement is limited to a few configuration inputs inside Akamai Property Manager.

• Enable the behavior: Queue-it appears as a native behavior in Property Manager, added the same way you'd add any other Akamai behavior.
  
  
• Provide your credentials: Your Queue-it Customer ID, API key, and the Proxy key are all that's needed, with the key stored securely via Akamai's Cloud Access Manager rather than embedded in code.
  
  
• Queue-it runs the EdgeWorker for you: There's no bundle to build, deploy, or maintain on your side.

The result is clear visibility into integration health from day one, with fast integration and minimal ongoing maintenance work.

Akamai Visitor Prioritization Powered by Queue-it is suitable for most Akamai customers out of the box. The behavior is designed to cover the most common Queue-it deployment patterns with minimal setup. However, organizations with highly customized requirements may be better served by the existing self-managed Edge Connector.

A couple of things to note before you enable the behavior:

• It's not compatible with a separate EdgeWorkers behavior on the same match condition, as only one EdgeWorker can execute per match condition and one Queue-it behavior instance can run per property for a given request.
  
  
• If your setup requires onOrigin execution of the Queue-it connector, this behavior isn't the right fit yet. That use case remains supported through the existing self-managed connector.

If either applies to you, the self-managed EdgeWorkers Connector remains the optimal setup for your use of Queue-it with Akamai.

The behavior must be purchased through Akamai and enabled on the customer’s Akamai account. But if you’d like to learn more about whether it’s the right fit for your organization, you can contact your Queue-it Customer Success Manager or reach out to support@queue-it.com.

Implementing Queue-it as a native Property Behavior in Akamai is the latest step in a strong partnership between the two organizations. 

Over five years ago, Queue-it was the first partner to go to market on EdgeWorkers together with Akamai. Since then, Akamai and Queue-it have:

• Served over 100 joint customers
• Processed over 40 billion sessions through the Edge Connector
• Launched a powerful joint bot mitigation solution, Hype Event Protection
• Added Queue-it to Akamai’s Qualified Compute Partner Program

Akamai Visitor Prioritization Powered by Queue-it extends that collaboration further, making Queue-it's online traffic orchestration just as easy to access on Akamai as native tools.