ShipAI Docs

ShipAI Documentation

Implementation-focused docs for building, extending, and operating the ship-ai monorepo.

Scope

These docs describe the ship-ai monorepo. This website repository hosts the docs and marketing experience, while implementation details come from the main ship-ai codebase.

ship-ai is a Bun + Turborepo monorepo for an AI chat/research product with billing, admin operations, background jobs, and optional integrations (search, memory, Telegram).

This documentation is reference-first: it maps source files, runtime boundaries, and operational workflows directly to implementation.

Documentation Map

Repository Snapshot

app/
admin/
web/
auth/
billing/
db/
features/
jobs/
memory/
storage/
stripe/
tracing/
ui/
OPTIONAL_SERVICES.md
TELEGRAM_BOT.md
TROUBLESHOOTING.md
package.json
turbo.json
docker-compose.yml
docker-stack.yml

Start Quickly

bun install
bun run setup
bun dev

Use this for fastest reliable first boot on a new machine.

bun install
cp .env.example apps/app/.env
cp .env.example apps/admin/.env
cp .env.example apps/web/.env
docker compose up -d
bun db:migrate
bun db:seed
bun dev

Use this when you want explicit control over each startup stage.

Start by Goal

  1. Go to Getting Started
  2. Follow Setup
  3. Validate env in Configuration
  4. Use Troubleshooting if boot fails
  1. Start with Codebase
  2. Read Monorepo Structure
  3. Continue with Apps and Packages
  4. Finish with Data Flow
  1. Review Features
  2. Review Operations
  3. Apply Deployment guidance
  4. Use Recipes for common implementation tasks

Command Reference

bun dev
bun dev:app
bun dev:admin
bun dev:web
bun dev:worker
bun db:migrate
bun db:generate
bun db:seed
bun db:seed:plans
bun db:studio
bun health
bun health:wait
docker compose ps
docker compose logs -f
bun lint
bun typecheck
bun test
bun build

API Surface (App)

Major route groups in apps/app/src/app/api/*:

  • auth: Better Auth entrypoint (/api/auth/[...all])
  • chat: message streaming (/api/chat, /api/chat/[id]/stream)
  • billing: plans/usage/subscription/checkout/portal/webhook
  • files: upload URL, upload, file by id
  • instruments: transcription and compare endpoints
  • artifact: create, patch, export
  • webhooks: Telegram webhook endpoint

Use the Features and Data Flow sections for request-level behavior and dependencies.

Reference Baseline

  • Feature flags (FEATURE_*): control user-visible capabilities like search, memory, and billing enforcement.
  • Service availability (SERVICE_*): represent whether backing services are deployed/reachable.
  • Development mode (DEVELOPMENT_MODE): relaxes selected production constraints for local iteration.
  • Workspace boundaries: apps/* own route/UI orchestration, packages/* own reusable domain/platform logic.
  • Ground truth docs: authoritative docs in ship-ai that this site should mirror.

Learn Next

On this page