---
title: Frequently Asked Questions
description: "Common questions about Jamdesk: pricing, build times, custom domains, team collaboration, AI chat, GitHub integration, and documentation site features."
---

Common questions about pricing, builds, domains, and features.

## Getting Started

<AccordionGroup>
  <Accordion title="What is Jamdesk?">
    Jamdesk is a documentation platform that builds docs sites from your Markdown files. Write in MDX, push to GitHub, and your site deploys automatically with search, analytics, and AI-ready `llms.txt`.
  </Accordion>

  <Accordion title="Do I need to know how to code?">
    No coding required. Writing in MDX is like using a text editor: you write plain text with simple formatting. Components are available if you want them, but they're entirely optional.
  </Accordion>

  <Accordion title="Can I try Jamdesk for free?">
    Yes! We offer a 14-day free trial with full access to all features.  
  </Accordion>

  <Accordion title="What's the difference between Jamdesk and other docs platforms?">
    Jamdesk is built around MDX and GitHub: your docs are plain text files in a repo, not locked in a proprietary editor. Push to GitHub and your site deploys in under 60 seconds with no build configuration or CI/CD pipeline. Every site gets `llms.txt` and an MCP server automatically, so AI tools like Claude and ChatGPT can access your current docs directly. Visitors get a built-in [AI chat assistant](/ai/chat) that answers questions from your docs, too.
  </Accordion>
</AccordionGroup>

## Builds & Deployment

<AccordionGroup>
  <Accordion title="How long do builds take?">
    Most documentation sites build in 30-60 seconds. Larger sites with many pages may take longer.
  </Accordion>

  <Accordion title="Can I preview changes before publishing?">
    Yes! Use the Jamdesk CLI (`jamdesk dev`) to preview locally with hot reload. Changes only go live when you push to GitHub or run `jamdesk deploy`.
  </Accordion>

  <Accordion title="Can I deploy without GitHub?">
    Yes. Run `jamdesk deploy` from your project directory. The CLI packages your files, uploads them, and triggers a build directly. No Git repo required. See the [CLI Deploy guide](/cli/deploy) for details.
  </Accordion>

  <Accordion title="What triggers a build?">
    Builds trigger automatically when you push to your connected GitHub branch. You can also trigger builds manually from the dashboard or with `jamdesk deploy` from the CLI.
  </Accordion>

  <Accordion title="Can I roll back to a previous version?">
    Yes. Go to **Deployments** in your project, find the previous build, and click **Rollback**.
  </Accordion>
</AccordionGroup>

## Billing & Pricing

<AccordionGroup>
  <Accordion title="How much does Jamdesk cost?">
    The Pro plan is $29/month per project. Additional projects are $15/month each. See [Plans & Pricing](/help/billing/plans) for details.
  </Accordion>

  <Accordion title="Is there a free plan?">
    We offer a 14-day free trial. After that, you'll need a Pro subscription to continue.
  </Accordion>

  <Accordion title="What payment methods do you accept?">
    We accept Visa, Mastercard, American Express, and Discover credit cards.
  </Accordion>

  <Accordion title="Can I get a refund?">
    We offer refunds within 30 days of your first payment. Contact support for assistance.
  </Accordion>
</AccordionGroup>

## Custom Domains

<AccordionGroup>
  <Accordion title="Can I use my own domain?">
    Yes! Add a custom domain in **Settings** → **Domains**. SSL certificates are provisioned automatically.
  </Accordion>

  <Accordion title="How long does DNS propagation take?">
    DNS changes typically propagate within a few hours, but can take up to 48 hours.
  </Accordion>

  <Accordion title="Can I host docs at a subpath like /docs?">
    Yes. Use a reverse proxy (Cloudflare, AWS, nginx) to serve Jamdesk at a subpath. See [Subpath Hosting](/deploy/subpath-hosting).
  </Accordion>
</AccordionGroup>

## Teams & Collaboration

<AccordionGroup>
  <Accordion title="How many team members can I have?">
    Pro plans include 10 team members per project.
  </Accordion>

  <Accordion title="Can team members edit documentation?">
    Team members can view builds and trigger rebuilds, but editing happens in your GitHub repository. Anyone with repository access can edit the docs.
  </Accordion>

  <Accordion title="How do I transfer project ownership?">
    Go to **Settings** → **Team** → **Transfer Ownership**. The new owner must be an existing team member.
  </Accordion>
</AccordionGroup>

## CLI

<AccordionGroup>
  <Accordion title="Where are my CLI credentials stored?">
    In `~/.jamdeskrc`, a JSON file with `0600` permissions (only your user can read it). It stores your refresh token, email, and user ID. Run `jamdesk logout` to clear it.
  </Accordion>

  <Accordion title='Why does the CLI say "session expired"?'>
    Your refresh token is no longer valid. This happens after password changes, account deletions, or extended inactivity. Run `jamdesk login` to get a fresh session.
  </Accordion>

  <Accordion title="Can I use the CLI in CI/CD pipelines?">
    Yes, but the browser-based login won't work in headless environments. Log in on your local machine, then copy `~/.jamdeskrc` to your CI runner. The refresh token handles authentication from there.
  </Accordion>
</AccordionGroup>

## Content & Features

<AccordionGroup>
  <Accordion title="What file formats are supported?">
    Jamdesk supports MDX (Markdown + JSX) and standard Markdown files.
  </Accordion>

  <Accordion title="Can I use custom React components?">
    Yes. Define inline components directly in MDX with `export const`, or create reusable components in the `/snippets` directory. For interactive components with hooks, use `.tsx` files with `'use client'`. See [Custom React Components](/content/react-components) and [Snippets](/content/snippets).
  </Accordion>

  <Accordion title="Is there a page limit?">
    No hard limit on pages. Most documentation sites work well with hundreds of pages.
  </Accordion>

  <Accordion title="Does Jamdesk support multiple languages?">
    Yes. Use the `languages` property in your navigation config to create a language switcher. Each language gets its own navigation structure and content. See [Multi-Language Support](/setup/languages).
  </Accordion>

  <Accordion title="Does Jamdesk translate my content automatically?">
    No. Jamdesk does not translate content for you. You provide the translated MDX files and Jamdesk handles routing, navigation, the language switcher, and RTL styling. Bring translations from your own workflow (human translators, machine translation, or an LLM) and place them in language-prefixed directories (`es/`, `fr/`, etc.). See [Multi-Language Support](/setup/languages) for the directory layout and config.
  </Accordion>
</AccordionGroup>

## AI Chat

<AccordionGroup>
  <Accordion title="Does my docs site have AI chat?">
    Yes. Every Jamdesk site includes a built-in chat assistant that answers visitor questions from your documentation. It's enabled by default, no setup required. See [AI Chat](/ai/chat) for details.
  </Accordion>

  <Accordion title="Does AI chat cost extra?">
    No. AI chat is included on all plans at no additional cost.
  </Accordion>

  <Accordion title="Can I turn off the AI chat?">
    Yes. Set `chat.enabled` to `false` in your `docs.json`:

    ```json
    { "chat": { "enabled": false } }
    ```

    The chat panel and keyboard shortcut will be removed after your next build.
  </Accordion>

  <Accordion title="What data does the chat use to answer questions?">
    The chat only uses your published documentation pages. During each build, Jamdesk indexes your content into a vector database. When a visitor asks a question, relevant sections are retrieved and sent to Claude as context. The AI cannot access data outside your docs.
  </Accordion>
</AccordionGroup>

## Related Articles

<Columns cols={2}>
  <Card title="Contact Support" icon="headset" href="/help/support/contact">
    Get help from the Jamdesk team
  </Card>
  <Card title="Build Failures" icon="triangle-exclamation" href="/help/troubleshooting/build-failures">
    Diagnose common errors
  </Card>
</Columns>