> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/install/lunar-hub/dedicated.md).

# Lunar Dedicated

Lunar Dedicated is a fully managed, single-tenant Lunar install. Earthly provisions it in an AWS account dedicated to you and owns the whole lifecycle: upgrades, patching, monitoring, backup and restore. If you would rather run the Hub on your own Kubernetes, see [Self hosted](/install/lunar-hub/self-hosted.md) instead.

{% hint style="info" %}
Earthly runs the infrastructure; you keep custody of your data and your credentials. The CLI and CI tracer are installed and configured exactly as they are on a self-hosted Hub.
{% endhint %}

## In order

1. [**Overview**](/install/lunar-hub/dedicated/overview.md) — how a Dedicated install is put together, the ways you can reach it, what Earthly needs from you, and how it handles your data and secrets. Read this first, and hand it to your security reviewer.
2. [**Setup**](/install/lunar-hub/dedicated/setup.md) — everything your side does, in order: the questionnaire, your depositor account, your Git platform credential, and the secret deposit. This is the page to work from.
3. [**PrivateLink to Your Hub**](/install/lunar-hub/dedicated/privatelink-inbound.md) — the recommended way for your CI runners, CLI users, and browsers to reach the install, and skippable only if your CI runs on shared hosted runners. Your side creates one interface endpoint and two DNS records. Settle how your Git platform will deliver webhooks early on, because that part can carry a lead time you don't control.
4. [**PrivateLink to Your Internal Systems**](/install/lunar-hub/dedicated/privatelink-outbound.md) — only if something your install must reach isn't on the public internet: a self-managed Git platform, or a collector target such as an internal registry, ticketing system, or API. It comes last in this list, but start it first. It needs a DNS change and an AWS domain-ownership check on your side, which makes it the longest-lead-time item in onboarding. You can forward the page to your networking team on its own.

## Before you start

Two neighboring sections apply to Dedicated installs as well, so they sit outside this one:

* [**Git Platforms**](/install/git-platforms.md) covers creating the credential Lunar authenticates with, on GitHub or GitLab. You create it and you [deposit it yourself](/install/lunar-hub/dedicated/setup.md#step-4-deposit-your-secrets), so it never passes through Earthly. The Hub-configuration sections of those pages are for self-hosted installs only.
* [**Lunar CI Tracer**](/install/ci-tracer.md) covers build-time data, if you want it. The tracer installs on your CI runners rather than in your install, so it is independent of onboarding and can be added at any point afterwards.

Still deciding whether Dedicated is the right fit? The [Overview](/install/lunar-hub/dedicated/overview.md) covers the trade-offs, or [book a demo](https://earthly.dev/book-demo/) and Earthly will walk your team through the model.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-lunar.earthly.dev/install/lunar-hub/dedicated.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.