Getting started

Start from a clean workspace, wire read-only connectors, and publish your first documentation bundle in three conversational passes. Each column below mirrors the kanban lane your onboarding lead uses: command, expected console shape, and the note they leave in your shared doc.

01 — Install

npm create claimharbor@latest ops-docs
cd ops-docs && npm install

Creates /.ch config stub with staging endpoints.

02 — Authenticate

npx ch-auth login --profile seoul-staging

Device code flow prints a short URL; no secrets in shell history.

03 — Sync topics

npx ch-sync pull --modules harbor-signal

Downloads topic JSON plus attachment manifests for offline review.

11years shipping ops tooling
38cities with active readers
92%quarterly doc freshness score
6language packs in circulation
54partner organizations in rotation

Zero-to-running

Install, authenticate, sync.

After the third command you should see a calm confirmation block—no stack traces, no marketing banners—just module names and freshness timestamps. That is the signal the workspace is talking to staging correctly.

If the banner line reads modules pending review, open the documentation hub and approve the import list; the CLI will resume automatically.

Browse modules instead →

Field team reviewing camera notes in a Hong Kong workspace 
claimharbor-cli/2.4.1 darwin-arm64
> sync complete — 9 modules, 0 warnings
> next: ch docs preview --port 4173

Trust signals we publish

  • SOC 2 Type II on the controls that matter for documentation and analytics workspaces.
  • GDPR-ready subprocessors list with change notifications to tenant admins.
  • ISO 27001 aligned runbooks for backups, access reviews, and incident response drills.
  • Korean PIPA mapping for Seoul-hosted tenants with data residency options.
  • Customer-managed keys for attachment vaults where policy requires offline root.
  • Transparent uptime targets with public status history you can cite in procurement packets.

Community trajectory

  • Reader accounts crossed eighteen thousand active seats in the APAC corridor last quarter.
  • Workshop attendance held steady even as self-serve onboarding improved—people still want live Q&A.
  • Issue threads tagged documentation resolve a day faster than average engineering tickets.
  • Contributor patches cluster around connector maps and brief templates, not cosmetic CSS.

Status

Subscribe where you already live.

All systems operational

Updated moments ago · Seoul edge

Email

Weekly digest of incidents + retro links.

Slack

#ch-status with threaded summaries only.

PagerDuty

Low-volume route for Sev2+ platform events.

Playground

The embedded editor mirrors the tabs we ship inside the documentation hub. Visitors can rearrange the sample, run a mocked execution path, and read the cautions about secret handling. We keep the default snippet short so screen readers encounter meaningful structure before the textarea. Language toggles on the listing page swap syntax highlighting presets only—they do not change backend behavior. When you promote a snippet to production docs, version tags travel with the block so readers know which CLI generation they are looking at. Finally, the playground refuses outbound network calls, which means output is deterministic for workshops and classroom settings alike. 

OK — modules: 9 active

Runnable preview is sandboxed: edits stay in-browser and never call production networks. The snippet shows the shape of responses your operators should expect when credentials are configured in a staging workspace. Swap tokens through your secret manager rather than pasting live keys here.

Recent releases

  1. Added

    2.4.1 — connector diff exports

    Markdown bundles now include hash pointers for each table mapping, matching the integrity utilities module.

  2. Changed

    2.4.0 — nightly brief defaults

    Paragraph slots reorder to prioritize operational deltas before attachment summaries.

  3. Fixed

    2.3.8 — sidebar focus rings

    Keyboard traversal no longer skips collapsed disclosure groups on Safari.

Book a workshop walkthrough

We will bring a facilitator, a dry-run tenant, and annotated agendas—no participant cap gimmicks.

Schedule a call