---
title: "Get help"
description: "Search first, check the known issues, then chat or send a message. Every way to reach a person about Outpost."
url: "https://support.outpostplatform.com/support/"
product: "platform"
type: "landing"
status: "draft"
ai_summary: "The Outpost support page. Lists the help channels in order: search the documentation, check known issues, check service status, start a live chat, send a message through the contact form, email support, and report a security problem privately."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/support/index.mdx"
license: "CC BY 4.0"
---

# Get help

Start at the top of this page and work down. The first two options answer most
questions in less time than it takes to write a message, and everything below
them reaches a person.

## Search this documentation

Press <kbd>Ctrl</kbd> and <kbd>K</kbd> anywhere on this site, or use the search
box in the header. Search covers every page, matches whole words and phrases,
and takes you to the section that matched rather than to the top of the page.

If you searched and found a page that did not answer the question, say so with
the feedback control at the bottom of that page. That is the fastest way to get
a page fixed, and it takes one click.

## Check the known issues

[Known issues](/support/known-issues/) lists everything we know is broken right
now, with the versions affected and the workaround where there is one. Each row
has an identifier such as `KI-0001`, so you can name an issue in a conversation
instead of describing it.

Check this before reporting a bug. If your problem is on the list, the page
tells you whether a fix is coming and what to do meanwhile.

## Check service status

{/*TODO: no public status page is published yet. When one is, set
PUBLIC_STATUS_URL in the build environment and the link renders.*/}

{
    statusUrl ? (
        <p>
            The <a href={statusUrl}>Outpost status page</a> reports the health of the
            services Outpost runs. It is hosted separately from this site, so it stays
            up when this one does not.
        </p>
    ) : (
        <p>
            No public status page is published yet. If the Outpost service looks
            unreachable from your Depot, the channels below reach a person who can
            check.
        </p>
    )
}

Your own Depot is not on that page. It runs on your infrastructure, and its
health is in your own console.

## Chat with a technician

Live chat reaches somebody who can look at your deployment with you. It is the
right channel for something that is broken now.

Chat is available during business hours. Outside them, use the contact form
below. Nothing you type is lost if nobody answers immediately.

## Send a message {#contact}

The [contact form](/support/contact/) reaches the same queue as chat and is the
right channel for anything that is not urgent, anything that needs detail, and
anything about billing or your account.

Include the component and version, what you expected, what happened, and the
exact message you saw. A message with those four things in it usually gets an
answer rather than a question back.

## Email

If the form will not work for you, email
[support@outpostplatform.com](mailto:support@outpostplatform.com) directly.

{/*TODO: confirm the support mailbox above is monitored and lands in the same
queue as the form before this site goes public.*/}

## Report a security problem

Do not use chat, the form or a public issue for a security problem. See
[reporting a vulnerability](/security/reporting-a-vulnerability/), which tells
you where to send it and what happens next.

## Improve a page yourself

Every page on this site is public and takes corrections. See
[contribute](/contribute/). A fix from somebody who hit the problem is worth
more than a page written by somebody who did not.