Start Here

Choose the path that matches how much you want to inspect.

Audience: First-time evaluators, operators, and contributors deciding whether to click through the shared demo, clone the repo, or deploy the stack.

The Short Version

There are three ways to start:

  1. Use the shared hosted demo
    • fastest first impression
    • no local setup
    • limited scope, shared environment
    • use Public Demo Guide
  2. Clone the repo and run it locally
    • best path if you want to see the full product
    • use Quickstart
  3. Deploy it on a server
    • best path if you want a real self-hosted workspace instead of a shared demo
    • use Deployment

Fastest Shared-Demo Path

If you want the shortest possible first pass, use the hosted demo:

  • URL: https://demo.clawback.team
  • email: evaluator@hartwell.com
  • password: publicdemo1

Then:

  1. open Chat
  2. select Incident Copilot
  3. ask Why did checkout fail last night?

If you want the full step-by-step path, use Public Demo Guide.

Which Path Should You Pick?

Pick the shared demo if:

  • you want a quick look
  • you're okay with the Incident Copilot path
  • you don't need your own data or workspace

You'll see: retrieval-backed answers, action handoff with review, and workspace state. You won't see: your own deployment, your own connectors, or broad workflow coverage.

Next: Public Demo Guide

Pick local clone if:

  • you want to see the full product
  • you want a private local workspace
  • you may want to contribute or debug

Fast path:

git clone https://github.com/clwbk/clawback.git clawback
cd clawback
pnpm install
./scripts/start-local.sh
pnpm db:seed

Then open:

  • http://localhost:3000/setup

Next docs:

Pick server deployment if:

  • you want a real self-hosted environment
  • you need a dedicated workspace rather than a shared public one
  • you want to verify the supported single-node deployment path

Next docs:

With Or Without Cloning The Repo

  • If you want to self-host, the supported path starts from a repo checkout
  • If you only want to try the product, use the shared demo — no clone needed
  • If you're deploying to a remote VM, the remote host doesn't need its own git checkout when you deploy from a local checkout with ./scripts/deploy-remote-stack.sh

The current modes are:

  1. No clone at all
    • use the shared hosted demo
  2. Clone locally
    • use quickstart for local evaluation or contribution
  3. Clone locally, but not on the server
    • use the deployment tooling to sync the current repo snapshot to the host

Example remote deploy flow:

git clone https://github.com/clwbk/clawback.git clawback
cd clawback
cp .env.prod.example .env
./scripts/deploy-remote-stack.sh --host user@host

Recommended Starting Order

If you are unsure, use this order:

  1. Public Demo Guide for the quick shared path
  2. Quickstart for the real local path
  3. Deployment if you want a dedicated server-backed workspace

Related Guides