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
Section titled “Search this documentation”Press Ctrl and K 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
Section titled “Check the known issues”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
Section titled “Check service status”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.
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
Section titled “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
Section titled “Send a message”The contact form 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.
If the form will not work for you, email [email protected] directly.
Report a security problem
Section titled “Report a security problem”Do not use chat, the form or a public issue for a security problem. See reporting a vulnerability, which tells you where to send it and what happens next.
Improve a page yourself
Section titled “Improve a page yourself”Every page on this site is public and takes corrections. See contribute. A fix from somebody who hit the problem is worth more than a page written by somebody who did not.
Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either licence.