> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shipyard.lol/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome to Shipyard

> Start here to understand the Shipyard suite and where each product fits.

Shipyard brings planning, coding, team coordination, and upcoming delivery workflows into one product suite. Use these docs to choose the right entry point, set up your workspace, and connect your team to the tools they already use.

<Card title="Open Shipyard" icon="rocket" horizontal href="https://shipyard.lol" cta="Go to Shipyard">
  Visit the main Shipyard site to sign in, review plans, and launch the apps available to your workspace.
</Card>

## What Shipyard includes

<Columns cols={2}>
  <Column>
    <Card title="ShipSpace" icon="circle-dot">
      Plan work, track issues, import Linear tasks, collaborate with teammates, and ask Leo for issue context and setup help.
    </Card>
  </Column>

  <Column>
    <Card title="ShipCode" icon="code">
      Move from issue context into local or cloud coding workflows, inspect diffs, run tests, and create pull requests.
    </Card>
  </Column>

  <Column>
    <Card title="ShipOS" icon="panel-top">
      Manage workspace access, MCP connections, Company Knowledge, and the shared context that powers Shipyard apps.
    </Card>
  </Column>

  <Column>
    <Card title="Upcoming apps" icon="radar">
      ShipCloud and ShipRadar are planned for deployment pipelines, monitoring, analytics, and production feedback loops.
    </Card>
  </Column>
</Columns>

## Recommended path

<Steps>
  <Step title="Choose a plan">
    Review [Pricing](/add-ons) to decide whether Pro or Scale fits your team size and collaboration needs.
  </Step>

  <Step title="Set up ShipSpace">
    Create or import your workspace, then connect Linear if your team already tracks issues there.
  </Step>

  <Step title="Invite your team">
    Add teammates to your Shipyard team so they can collaborate in shared workspaces and issues.
  </Step>

  <Step title="Hand work to ShipCode">
    Move planned issues into ShipCode when you are ready to implement, test, and open pull requests.
  </Step>
</Steps>

<Tip>
  If you are just evaluating Shipyard, start with ShipSpace setup and a small issue import. That gives you enough context to test planning, collaboration, and AI handoff without restructuring your whole workflow.
</Tip>