Specify the Axe Developer Hub Server URL
Configure Axe Watcher to connect to a regional, private cloud, or on-premises Axe Developer Hub instance
When your organization was set up with Axe Developer Hub, Deque provisioned you onto a specific server. Most users are on the default US server and do not need to set a server URL in their Watcher configuration. If your organization is on a different server, you will need to supply that server's URL when configuring Axe Watcher.
If you are unsure which server your organization uses, check the project configuration in Axe Developer Hub. You can also check your provisioning email, look at the URL you visit when you log in to Axe Developer Hub, or ask your organization's administrator.
Deque Cloud Servers
Deque operates Axe Developer Hub on the following servers:
| Region | URL |
|---|---|
| United States (default) | https://axe.deque.com |
| Europe | https://axe-eu.deque.com |
| Australia | https://axe-au.deque.com |
| Frankfurt, Germany | https://axe-frankfurt.deque.com |
Private Cloud and On-Premises Servers
Organizations that run Axe Developer Hub in a private cloud or on-premises installation have a custom URL. Use the URL provided by Deque or configured by your administrator.
Where to Configure the Server URL
The server URL is set in different ways depending on how you use Axe Watcher. Refer to the documentation for your setup:
- JavaScript and TypeScript API: Set the
serverURLproperty in your Watcher configuration. - Java API: Call
setServerUrl()on yourAxeWatcherOptionsinstance. - Watcher setup instructions: Set the
SERVER_URLenvironment variable. Every framework setup page includes instructions for this variable in the environment variable configuration step. - CLI: Use the
--axe-devhub-server-urloption or theAXE_DEVHUB_SERVER_URLenvironment variable. See Send Results to Axe Developer Hub Using the CLI. - GitHub Action: Set the
server_urlinput parameter. See Using the Axe Developer Hub GitHub Action.