# Connecting Infrastructure Providers | Cycle.io

Canonical URL: https://cycle.io/docs/portal/connecting-an-infrastructure-provider

## Connecting Infrastructure Providers.

[Infrastructure provider integrations](https://cycle.io/docs/platform/hub-integrations#infrastructure-provider-integrations) are connected through the integrations dashboard.

To get there:

1.  Hub from the main, left-hand navigation.
2.  Integrations from the hub sub-navigation menu.
    
    ![integrations navigation](https://cycle.io/_cdn/docs-7923c125-integrations-aws-full-1333x988-webp.webp)
    

### Currently Supported Providers

Cycle currently supports the following providers:

-   [AWS](https://cycle.io/docs/guides/configure-aws)
-   [Cherry Servers](https://cycle.io/docs/guides/configure-cherry-servers)
-   [GCP](https://cycle.io/docs/guides/configure-gcp)
-   [Vultr](https://cycle.io/docs/guides/configure-vultr)
-   [Virtual Providers](https://cycle.io/docs/portal/virtual-providers)

### Auxillary Native Providers

To set up an Auxillary native provider, or, more simply, to add another account of the types natively supported, users can select the **Abstraction / Custom Integration** provider with the following special **base\_url**.

The supported base URLs are:

-   **aws**
-   **cherry**
-   **gcp**
-   **vultr**

Alongside these base URLs, the user will also need to provide the respective API key, secret, config, or whatever that provider requires.

### Provider Names and Identifiers

The provider configuration forms support both name (optional) and identifier (required). While the native providers will have the identifier filled in with a default value, this value can be changed to the user preference.

Valid identifiers support alphanumeric chars and **\-**'s.

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
