Add a link to Canvas on the OHE quickstart page

enterprise/quick-start.mdx

@@ -8,21 +8,27 @@
 You'll provision infrastructure (AWS Terraform or a manual VM setup), configure
 GitHub for user authentication, and configure your LLM provider.
 
-## Who This Is For
+## Who is this for
 
-This guide is **not** for single-user local laptop installs. It is for a **30-day trial of OpenHands Enterprise** on a
-**dedicated VM/server** on your own infrastructure. The deployment requires DNS records, network, and compute setup before installation.
+This guide is **not** for single-user local laptop installs. It is for a **30-day trial** of **OpenHands Enterprise** on a **dedicated VM/server on your own infrastructure**. The deployment requires DNS records, network, and compute setup before installation.
 
-If you want to use OpenHands immediately without infrastructure setup:
+Which scenario makes the most sense for you?
 
-- Use OpenHands Cloud (SaaS)
-- Run OpenHands open-source locally using Docker, CLI or SDK
+  ### I am looking to use OpenHands for myself
 
-### Accounts and Credentials
+Consider [OpenHands Agent Canvas](openhands/usage/agent-canvas/overview), which can be downloaded locally on your machine and runs for a single-user environment. 
+
+  <Card title="Download Agent Canvas" href="/openhands/usage/agent-canvas/setup">
+    100% Open Source (MIT license). Single-user. Runs on your local machine.
+  </Card>
+
+  ### I am looking to use OpenHands within my team or organization
+
+If you are looking to use OpenHands across **multiple users in your organization**, then you are at the right place. 
 
 Before you begin, make sure you have the following ready:
 
-<Card title="Register for a Trial Account" icon="user-plus" href="https://install.r9.all-hands.dev/openhands/signup">
+<Card title="Register for an OpenHands Enterprise Trial" icon="user-plus" href="https://install.r9.all-hands.dev/openhands/signup">
   Sign up for a free 30-day OpenHands Enterprise trial account. You'll need this to access the installer dashboard.
 </Card>
 
@@ -36,7 +42,7 @@
 You will need a VM to host OpenHands Enterprise. Choose one of the options below to provision your infrastructure.
 
 <Note>
   The requirements below are the trial baseline, which comfortably supports about 15 concurrent sandboxes. For a larger rollout, pick your VM from the [Sizing Guide](/enterprise/sizing-guide) before provisioning.
 </Note>
 
 <Tabs>
@@ -209,7 +215,7 @@
 done
 ```
 
 Expected: each hostname resolves to your VM's public IP address through the
 wildcard record.
 
 ### Outbound connectivity checks
@@ -239,7 +245,7 @@
 done
 ```
 
 Any HTTP response code other than `000` is acceptable for reachability checks
 (for example `200`, `301`, `302`, `401`, `403`, `405`).
 
 If any check fails, stop and resolve before continuing:
@@ -250,10 +256,10 @@
 
 | Requirement | Why It Exists |
 |------------|----------------|
 | `443/TCP` inbound | Primary HTTPS entrypoint for users and service hostnames |
 | `30000/TCP` inbound | Replicated/KOTS Admin Console for install and configuration |
 | `80/TCP` inbound | HTTP entrypoint used for ingress/redirect behavior |
 | `*.<domain>` DNS + cert SAN | Application services and sandboxes are addressed by hostnames under the base domain |
 | `replicated.app`, `proxy.replicated.com` | Replicated control-plane/license/install paths |
 | `images.r9...`, `charts.r9...`, `updates.r9...`, `install.r9...` | Vendor distribution image/chart/update/install endpoints |
 | `traefik.github.io` | Embedded cluster ingress chart repository |
@@ -306,7 +312,7 @@
 
   For trials and production deployments, use a publicly trusted TLS certificate whenever possible.
   Private CA certificates may work for users after manual trust setup, but external integrations
   such as GitHub, GitLab, Slack, Jira, and Bitbucket must also trust the certificate chain. If they
   do not, webhook or OAuth callbacks can fail TLS verification and repeatedly retry.
 </Warning>
 
@@ -326,7 +332,7 @@
 ### 5. Upload TLS certificate (if not provided with the install command)
 
 If you did not provide certificates with the `install` command, select **"Upload your own"**,
 enter `admin.<your-base-domain>` under **Hostname**, upload your private key and SSL certificate, then click **Continue**.
 
 If you upload a private CA certificate, make sure any external webhook or OAuth provider that
 calls OpenHands also trusts that CA.
@@ -354,7 +360,7 @@
 
 ### Domain Configuration
 
 - Keep the Hostname Configuration Mode set to **"Simple (default)"**
 - Enter your base domain (e.g., `openhands.example.com`)
 
 ### Certificate Configuration
@@ -399,7 +405,7 @@
 
 ### Additional Integrations
 
 If your team uses Jira Data Center or Bitbucket Data Center, follow these guides
 to configure Admin Console values before deployment and complete webhook setup
 inside OpenHands after deployment.
 
@@ -408,7 +414,7 @@
     Configure Bitbucket Data Center login, repository access, bot identity, and pull request webhooks.
   </Card>
   <Card title="Jira Data Center" icon="building" href="/enterprise/integrations/jira-data-center">
     Configure Jira issue triggers, OAuth account linking, service account credentials, and Jira webhooks.
   </Card>
 </CardGroup>