> For the complete documentation index, see [llms.txt](https://docs.teraswitch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teraswitch.com/getting-started/getting-started.md).

# Getting Started

Get up and running with TeraSwitch in minutes. Learn the basics of the console and deploy your first server.

Welcome to TeraSwitch! This section will help you get started with our platform and deploy your first infrastructure.

### What is TeraSwitch?

TeraSwitch provides high-performance bare metal servers, cloud compute instances, and GPU resources across 13+ global data centers. Our platform offers:

* **Bare Metal Servers** - Dedicated, single-tenant hardware with cloud-like ease of use
* **Cloud Compute** - Virtual instances with flexible vCPU, RAM, and storage
* **GPU Compute** - High-performance GPU servers for AI/ML workloads
* **Global Reach** - Data centers in North America, Europe, and Asia-Pacific

### Quick Links

* [Console Overview](/getting-started/console-overview.md) - Tour the TeraSwitch console
* [First Deployment](/getting-started/first-deployment.md) - Deploy your first server
* [Projects & Roles](/getting-started/projects-and-roles.md) - Understand organization structure


---

# 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.teraswitch.com/getting-started/getting-started.md?ask=<question>&goal=<user_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.