Start here
The shortest path from a new account to a proven Viewport workflow run.
Start with one proof, not a platform migration.
The shortest proof is the Quickstart: one governed run and its receipt, in about ten minutes, with no GitOps setup. The fuller event-triggered launch path is:
create org -> connect GitHub/Slack -> install vpd -> pair worker -> commit .viewport -> trigger -> approve -> inspect receiptsThe First Hour
Quickstart
First governed run and its receipt in about ten minutes.
What is Viewport?
Why Viewport is a control plane, not another coding agent.
Launch checklist
The team acceptance bar for the first governed run.
Cold-path acceptance
The pass/fail worksheet for the first operator-run setup.
Self-serve first run
The exact hosted setup path for an early partner workspace.
Mental model
The six questions every workflow answers.
Before You Begin
You need:
- access to the hosted app;
- Node 20+ on the machine that will run
vpd; - a GitHub repository safe for a demo PR;
- a Slack workspace/channel for completion receipts;
- permission to install the Viewport GitHub and Slack apps.
Use a sandbox repo for the first pass. Keep the workflow small enough that a human can inspect every receipt.
What Not To Do First
Do not start by wiring production repositories, broad Slack channels, or complex
context sources. Prove .viewport/ sync, worker claim, approval, PR creation,
Slack completion, and run detail first. Then broaden scope intentionally.