> For the complete documentation index, see [llms.txt](https://docs.neverinstall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neverinstall.com/cloudlink/creating-a-cloudlink-space.md). # Creating a CloudLink space ### Creating an Instance Using Your Preferred Cloud Service Provider Follow the steps below to set up a new instance using Neverinstall: **Step 1: Access Your Neverinstall Account** To start, visit the Neverinstall website and sign in to your account.

**Step 2: Select a Cloud Service Provider** Navigate to the 'Spaces' page within your Neverinstall account. Here, you will see an option to select your cloud service provider, to the top right corner. Please note, as of our latest update, Neverinstall supports the creation of instances on three platforms: Vultr, Azure, and AWS. We are continually working to expand our offerings, and additional cloud service providers will be available soon.

**Step 3: Input Instance Details** Upon selecting your cloud service provider, a pop-up form will appear. This form requires specific details necessary for instance creation. Please note that the information required varies depending on the selected cloud service provider. Fill in the necessary information accurately and proceed. In the case of any difficulties or discrepancies while creating an instance, do not hesitate to reach out to our support team for assistance.

--- # 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.neverinstall.com/cloudlink/creating-a-cloudlink-space.md?ask=&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.