Skip to content

GhostForge Demo Script ​

Seven demos. Twenty minutes. An enterprise AI app portal with PII scanning and governance.

This script walks through GhostForge — GhostAI's built-in app portal for publishing, discovering, forking, and embedding interactive AI-generated applications. Every app is PII-scanned before publishing, supports org-level governance (approval queues, visibility policies, PII blocking), and includes analytics and audit logging.


Pre-Demo Checklist ​

  • [ ] GhostAI instance is running and reachable
  • [ ] Browser open to GhostAI chat interface
  • [ ] GhostForge is enabled for your organization (Admin Dashboard > GhostForge > "Enable GhostForge" is ON)
  • [ ] Your account has the app_publish billing feature (Team, Business, or Enterprise tier)
  • [ ] Sidebar shows "Browse Gallery" and "My Apps" buttons (if not visible, GhostForge may be disabled for your org)
  • [ ] At least one canvas has been created previously (or create one live in Demo 1)
  • [ ] Admin approval is disabled for the initial demos (enable it for Demo 6)
  • [ ] Screen resolution is large enough for both chat and gallery views

Quick verification ​

  1. Click Browse Gallery in the sidebar — the /apps gallery page should load
  2. Click My Apps in the sidebar — your published apps list should appear (may be empty)

Demo 1: Publish a Canvas App ​

Duration: 3 minutes Story: A team member builds a dashboard in chat, then publishes it as a shareable app in one click.

Step 1 — Create a canvas ​

Type this into the GhostAI chat:

Build a real-time server monitoring dashboard with 4 widgets: CPU usage gauge, memory usage ring chart, network throughput sparkline, and a live request count that ticks up. Use random simulated data that updates every second.

Wait for the canvas to render with all four animated widgets.

Step 2 — Publish to GhostForge ​

  1. Click Publish to GhostForge on the canvas toolbar
  2. The AppPublishModal opens with:
    • Title: pre-filled from the canvas (edit to "Ops Dashboard")
    • Description: add "Real-time server monitoring with animated gauges, ring charts, and sparklines"
    • Category: select "Productivity"
    • Tags: add dashboard, monitoring, real-time
    • Visibility: select "Organization" (all org members can see it)
  3. Notice the PII scan results section — it should show PII-Free (green badge)
  4. Click Publish

Expected Output ​

  • Success notification: "App published to GhostForge"
  • The app is now available at /apps/ops-dashboard (auto-generated slug)
  • The publish modal closes and a link to the app appears in the chat

Talking Points ​

"One click. That dashboard is now a shareable app with a stable URL. No deployment pipeline, no DevOps ticket, no waiting for IT. The analyst who built it in chat just published it for the whole organization."

"Notice the PII scan. GhostForge automatically scanned every line of HTML, CSS, and JavaScript in that canvas for personally identifiable information before allowing the publish. The green badge means it's clean."


Duration: 2 minutes Story: Show the app marketplace experience — discovery, search, categories, featured apps.

Steps ​

  1. Click Browse Gallery in the sidebar (or navigate to /apps)
  2. Point out the gallery layout:
    • Featured carousel at the top (admin-curated apps)
    • Category filters (Productivity, Education, Finance, etc.)
    • Search bar for finding apps by title, description, or tags
    • Sort options: Recent, Popular, Trending
  3. Search for "dashboard" — the app from Demo 1 should appear
  4. Click on the app card to open the App Detail Page
  5. Point out:
    • App preview (live rendered canvas)
    • Author name and organization
    • Privacy badge (PII-Free)
    • View count and fork count
    • Fork, Embed, and Open buttons

Expected Output ​

  • Gallery loads with any existing published apps
  • Search returns the "Ops Dashboard" from Demo 1
  • Detail page shows full app preview with metadata

Talking Points ​

"This is an internal app store for your organization. Every app was built in conversation — no code review, no pull request, no CI/CD. A business analyst builds it, publishes it, and the whole team can discover it here."

"Every app card shows the privacy badge. Your compliance team can scan the gallery and instantly see which apps have been verified PII-free, which had PII tokenized, and which need review."

"The sort options — Recent, Popular, Trending — help teams find the apps that are actually being used. This isn't a graveyard of unused tools; the trending algorithm surfaces apps with recent engagement."


Demo 3: Fork an App ​

Duration: 2 minutes Story: A colleague finds the dashboard useful but wants to customize it for their team.

Steps ​

  1. From the App Detail Page (Demo 2), click Fork
  2. A new chat session opens with the forked canvas loaded
  3. The canvas is a complete copy — all HTML, CSS, JS, and state
  4. Type a modification:
Replace the CPU gauge with a donut chart, change the color scheme to blue/teal, and add a header that says "DevOps Dashboard" with today's date.
  1. The canvas updates in place with the new design
  2. (Optionally) Publish the forked version as a new app

Expected Output ​

  • New chat session with the forked canvas
  • Canvas renders identically to the original, then updates with modifications
  • The fork is independent — changes don't affect the original app

Talking Points ​

"Fork is the collaboration model. Sarah built the original Ops Dashboard. DevOps wants a version with different metrics. They fork it — one click — customize it, and publish their own version. No coordination, no merge conflicts, no shared codebase."

"The fork maintains attribution. On the detail page, you'll see 'Forked from Ops Dashboard by Sarah.' The original author gets credit, and the fork count shows how influential their app is."

"This is how organizational knowledge compounds. One person builds a template, the whole team builds on it."


Demo 4: Embed an App ​

Duration: 2 minutes Story: The dashboard needs to appear on an internal wiki or executive portal.

Steps ​

  1. From the App Detail Page, click Embed
  2. Show the embed code:
html
<iframe
  src="https://your-host/api/apps/ops-dashboard/embed"
  width="100%"
  height="600"
  frameborder="0"
  sandbox="allow-scripts allow-same-origin"
></iframe>
  1. Point out the key features:
    • Sandboxed iframe with CSP protections
    • "Powered by GhostForge" footer in the embed
    • oEmbed endpoint at /api/apps/ops-dashboard/oembed for services that support auto-discovery
    • Open Graph page at /api/apps/ops-dashboard/og for rich social previews (Slack, Teams, etc.)

Expected Output ​

  • Embed code displayed with copy button
  • oEmbed JSON available at the /oembed endpoint
  • OG meta tags generate rich previews when the app URL is shared in Slack/Teams

Talking Points ​

"Embed anywhere. Confluence, Notion, SharePoint, your internal wiki — just paste the iframe. The app runs in a sandbox with strict CSP so it can't access cookies, storage, or the parent page."

"When someone shares the app URL in Slack or Teams, the Open Graph tags generate a rich preview with the app title, description, thumbnail, and a 'Powered by GhostForge' badge. It looks professional, not like a random link."

"For Confluence and tools that support oEmbed, we have that too — automatic embed discovery without pasting iframe code."


Demo 5: Privacy Badges and PII Scanning ​

Duration: 2 minutes Story: Show what happens when an app contains PII — the safety net that enterprise compliance teams need.

Steps ​

  1. Create a new canvas in chat:
Build a simple employee directory page with a table showing 5 employees: John Smith (john.smith@acme.com, 555-123-4567), Jane Doe (jane.doe@acme.com, 555-234-5678), Bob Wilson (bob.wilson@acme.com, 555-345-6789), Alice Brown (alice.brown@acme.com, 555-456-7890), and Charlie Davis (charlie.davis@acme.com, 555-567-8901). Include their department and start date.
  1. Click Publish to GhostForge

  2. In the publish modal, notice:

    • PII scan results: PII detected — emails, phone numbers, names
    • Privacy badge: PII-Warning (red) or PII-Tokenized (amber)
    • Warning message explaining what was found
  3. If org policy has Block PII Publishing enabled, the Publish button is disabled with an explanation

Expected Output ​

  • PII scan identifies email addresses, phone numbers, and person names
  • Privacy badge is amber or red depending on tokenization
  • If PII blocking is enabled, publish is prevented

Talking Points ​

"This is where GhostForge is fundamentally different from any app marketplace. Every publish goes through the full PreDact PII pipeline — the same engine that protects your chat conversations. Emails, phone numbers, names, SSNs — all caught before the app goes live."

"For the CISO: your team builds a hundred internal tools. Without GhostForge, any one of them could accidentally include customer PII in the HTML. With GhostForge, it's impossible to publish without a PII scan, and the org admin can block PII-containing apps entirely."

"The three-tier badge system gives compliance teams instant visibility. Green means safe. Amber means PII was found and tokenized. Red means review is needed."


Demo 6: Org Admin Governance ​

Duration: 3 minutes Story: Show the admin controls that enterprise IT needs — approval workflows, visibility policies, and audit logs.

Steps ​

  1. Navigate to Admin Dashboard > GhostForge tab

  2. Walk through the configuration options:

    • Enable GhostForge: toggle on/off for the entire org
    • Default Visibility: Private / Unlisted / Organization / Public
    • Require Admin Approval: toggle on
    • Block PII Publishing: toggle on/off
    • Max Apps Per User: set a limit (or -1 for unlimited)
    • Allowed Categories: restrict which categories are available
  3. Enable Require Admin Approval and save

  4. Go back to chat, create a simple canvas, and try to publish:

Build a simple calculator with +, -, ×, ÷ buttons and a display.
  1. Publish it — notice the status shows Pending Review instead of immediately going live
  2. Go back to Admin Dashboard > GhostForge > Approval Queue
  3. The calculator app appears with:
    • Title and slug
    • Author name
    • PII detection status
    • Privacy badge
  4. Click Approve — the app goes live
  5. (Show the Reject flow briefly — author gets notified with rejection notes)

Expected Output ​

  • Admin policy saved successfully
  • Published app enters "Pending Review" status
  • Approval queue shows the pending app
  • Approving moves it to "Published" status

Talking Points ​

"This is the governance layer that separates GhostForge from a toy. The org admin controls everything: who can publish, what visibility is allowed, whether PII can be published, and whether every app needs manual approval."

"For regulated industries — healthcare, finance, government — the approval queue is mandatory. No app goes live without an admin reviewing the PII scan results and the content. It's the same model as a code review gate, but for business-built apps."

"Every action is logged in the audit trail. forge.app_submitted_for_review, forge.app_approved, forge.app_rejected, forge.policy_updated — all exportable to your SIEM. Splunk, Sentinel, QRadar — they all get these events."


Demo 7: Analytics ​

Duration: 2 minutes Story: Show the author and executive views of app engagement.

Steps ​

  1. Click My Apps in the sidebar

  2. Find the Ops Dashboard (or any published app with some views)

  3. Click the analytics icon (chart icon) on the app card

  4. Show the analytics panel:

    • View count (total)
    • Fork count (how many times it's been forked)
    • Version history (changelog for each update)
    • Recent forks (who forked and when)
  5. (For executive view) Navigate to Admin Dashboard > executive metrics section

  6. Show the GhostForge org summary — total apps, total views, active authors

Expected Output ​

  • Per-app analytics panel with view count, fork count, version history
  • Org-level summary metrics

Talking Points ​

"The author sees how their app is performing — views, forks, version history. The executive sees the org-wide picture — how many apps are in production, how many people are building, total engagement."

"For the CTO: this is the metric that proves the ROI. Your team built 47 internal tools last quarter without a single engineering ticket. Here's the usage data to prove they're being used."

"The fork count is particularly interesting. A high fork count means the original app has become a template — it's seeding an entire category of internal tools."


Recovery Steps ​

GhostForge not visible in sidebar ​

Symptom: No "Browse Gallery" or "My Apps" buttons in the sidebar.

Fix:

  1. Verify GhostForge is enabled for your org: Admin Dashboard > GhostForge > "Enable GhostForge" should be ON
  2. Verify your account tier includes GhostForge (Team, Business, or Enterprise)
  3. Refresh the page

Publish button disabled ​

Symptom: "Publish to GhostForge" button is grayed out or returns an error.

Fix:

  1. Check if your org blocks PII publishing and the canvas contains PII
  2. Check if you've hit the max apps per user limit
  3. Verify your account has the app_publish billing feature

App stuck in "Pending Review" ​

Symptom: Published app shows "Pending Review" and never appears in the gallery.

Fix: Admin approval is enabled. Navigate to Admin Dashboard > GhostForge > Approval Queue and approve the app.

Symptom: /apps gallery page is empty.

Fix:

  1. Verify at least one app is published with "Organization" or "Public" visibility
  2. Apps with "Private" or "Unlisted" visibility don't appear in the gallery
  3. Check if the search/filter is active

Embed not rendering ​

Symptom: Iframe embed shows blank or error.

Fix:

  1. Verify the app is published (not draft, archived, or pending review)
  2. Verify the app visibility allows access (private apps can't be embedded)
  3. Check browser console for CSP errors — the embedding page may block iframes

Fork creates empty canvas ​

Symptom: Forking opens a new session but the canvas is empty.

Fix: The canvas content may not have been saved. Verify the original app has content by checking the detail page. Refresh and try again.


Demo Flow Cheat Sheet ​

#DemoDurationKey Moment
1Publish a Canvas App3 minOne-click publish with PII scan and privacy badge
2Browse the Gallery2 minApp marketplace with search, categories, featured
3Fork an App2 minOne-click copy into a new editable session
4Embed an App2 minSandboxed iframe, oEmbed, Open Graph previews
5PII Scanning2 minPII detection blocks publishing of sensitive content
6Org Admin Governance3 minApproval queue, visibility policy, PII blocking
7Analytics2 minPer-app and org-wide engagement metrics
Total~16 min

Frequently Asked Questions (From Demos) ​

"How is this different from just sharing a link?"

A link to a canvas in a chat is ephemeral — it's tied to that conversation and that user's session. GhostForge gives the app a stable URL, a version history, a privacy badge, analytics, and discoverability. It's the difference between emailing a file and publishing it to an internal app store.

"Can apps access our company data?"

Published apps run in a sandboxed iframe with strict Content Security Policy. They cannot access cookies, local storage, or the parent page. The only data access path is through the Canvas SDK's ghostai.proxy() endpoint, which the backend controls and audits.

"What about compliance? Can we prevent certain apps from being published?"

Yes. Org admins can: (1) block PII-containing apps from publishing, (2) require admin approval for every app, (3) restrict allowed categories, (4) set default visibility, and (5) limit apps per user. Every governance action is logged to the audit trail and exported to your SIEM.

"Can external users see our apps?"

Only if visibility is set to "Public." Most orgs default to "Organization" (all org members) or "Unlisted" (link-only). The admin can set the org-wide default and block public publishing entirely.

"How does versioning work?"

Every update to a published app creates a new version with a changelog. The version history is visible on the app detail page and in analytics. Users always see the latest version; there's no rollback UI yet, but the version data is stored.

"Can we run this air-gapped?"

Yes. GhostForge is fully self-contained — no external CDN dependencies, no external API calls. In air-gapped deployments, the gallery, embed, and oEmbed endpoints all work within the local network.

"How does this compare to Retool or Appsmith?"

Retool and Appsmith are low-code platforms for professional developers. GhostForge is for anyone — you describe what you want in conversation and publish it. No drag-and-drop builders, no data source configuration, no deployment pipeline. The tradeoff is that GhostForge apps are best suited for internal tools, dashboards, and prototypes rather than production customer-facing applications.


For hands-on setup from scratch, see the GhostForge Full Lab. For canvas creation demos, see the Canvas Demo Script.

SOC 2 Type II Certified | BAA Available | HIPAA-Ready