Skip to main content

​
Demos

The product lands fastest when you treat demos as progressive proofs, not one giant everything-demo. Recommended order:
  1. Hosted self-demo — proves the trust model
  2. Preview-safe Vercel demo — proves live provider mutation
  3. Vercel + GitHub wedge — proves the strongest current multi-provider story
Do not start with the mixed-provider path unless the audience explicitly wants the deepest live story.

​
Demo A — best first demo: hosted control plane, no external credentials

​
Run

npm install
npm run demo:hosted:self

​
What it proves

  • agents submit intent, not arbitrary shell
  • Keycli returns a structured plan with risk and next action
  • risky apply is blocked until a human approves
  • agents cannot self-approve
  • agents cannot issue stronger tokens for themselves
  • approvals, apply flow, and audit work on the hosted TypeScript path

​
What it does not prove

  • live provider mutation
  • GitHub-native approval capture
That is okay. Demo A is about the trust boundary.

​
Demo B — best live proof: preview-only Vercel mutation

​
Run

Terminal 1: 
npm run api:hosted
Terminal 2: 
export VERCEL_TOKEN=...
export KEYCLI_VERCEL_PROJECT=your-project
npm run demo:vercel:preview

​
What it proves

  • real hosted API
  • real Vercel ProviderConnection creation
  • real connection testing
  • real workspace readiness detection
  • real preview env var mutation via the Vercel API

​
Why this is the right live demo

  • single provider
  • preview target, not prod
  • no deploy step required
  • low-risk and repeatable
  • much easier to explain than the mixed-provider wedge
Full details: Vercel

​
Demo C — strongest current wedge: Vercel + GitHub Actions

Use this after Demo B lands well. This path is real when both providers are connected, but it is higher-friction:
  • usually prod-oriented
  • approval-gated
  • touches multiple systems
  • better as a second or third demo, not the first morning run
Full details: GitHub

​
Which demo should you show first?

​
If you only get one shot

Show Demo A.

​
If you need live proof after the trust story lands

Show Demo B.

​
If the audience asks whether it really works across providers

Show Demo C, but only if the connections and approval path are already prepared.

​
Short truth summary

  • Hosted API / auth / approvals / runs / audit: live
  • Vercel live mutation: live
  • GitHub Actions live secret rotation: live
  • Render live env var mutation: live
  • Best-tested mixed-provider lane: Vercel + GitHub Actions
  • GitHub App approvals: not built yet