01

SCO AI Workshop

How to Prototype

A hands-on session for SCOs — from an idea to a working, shareable AI prototype, and how to host it.

02

Today's Session

Three parts — intro, hands-on, and where to go next.

Part 1
Intro to Hosting
What hosting means for a prototype, and the landscape of options. Presented by Bijan.
Part 2
Hands-On Exercises
Get a prototype live yourself. Deploy, share, iterate.
Part 3
Outlook: Robust Hosting
From a working prototype toward something production-ready.
03
Part 1 — Intro to Hosting

Intro to Hosting
Presented by Bijan

This part is about one thing: being able to serve a page, an app, a UI — fast and simply. Not production-grade, but fast and reasonably secure. Good enough to share, good enough to get a reaction.

04
Part 1 — Intro to Hosting

Why Hosting Matters

  1. Shareability
    A link beats a screen-share. Share it async — the client opens it when they have time, on their own device.
  2. Feedback loops
    Clients react to what they can touch — and fast hosting means fast iterations.
  3. Credibility
    A live prototype signals we ship.
  4. Interactivity
    Better than slides. Let people click, filter, explore — a hosted prototype is a conversation starter.
05
Part 1 — Intro to Hosting

Hosting Under the Hood

Whiteboard breakout — the building blocks behind every hosted prototype.

Networking
DNS & IP Addresses
How myapp.gemmaanalytics.com turns into an IP address a browser can connect to. A-records, name resolution, TTL.
Transport
HTTP(S), Ports & SSL
What happens when your browser opens port 443. The role of TLS certificates, why HTTPS matters, what a port actually is.
Infrastructure
Servers & (Reverse) Proxies
A server listens on a port. A reverse proxy sits in front of it — routing, SSL termination, multiple apps on one machine.
Format
Short whiteboard session. We’ll draw the path from browser to server and back — DNS, TCP, TLS handshake, HTTP request, reverse proxy, app process.
06
Part 1 — Intro to Hosting

Hosting Prototypes at Gemma

Three options — from zero-effort to fully automated.

Option 1
Gemmbot
Ask Gemmbot in Slack to host something for you. Live in seconds, stays up for a few days. Zero setup.
Available now
Option 2
Proper Hosting
Sub-DNS A-record on mynewapp.gemmaanalytics.com. May include CI/CD pipelines, Docker, etc.
Available now — requires know-how
Option 3
WebGemms (coming)
Infrastructure as Code + agentic skills. Option 2 made accessible to everyone via Claude — proper DNS, CI/CD, no DevOps knowledge needed.
Not yet implemented — TBD
07
Part 1 — Intro to Hosting

Gemmbot Hosting

The fastest path from file to URL.

How it works
Ask Gemmbot in Slack
Send Gemmbot a file, point it to a GitHub repo, or just describe what you need. It spins up a dev server, provisions HTTPS automatically, and posts the live URL back in the thread.
Scope
Temporary — a few days
Great for demos, quick shares, and getting feedback. Not meant for long-lived apps — the session ends when the thread goes idle.
When to use
Quick, low-stakes scenarios
• View a dev version of something already in prod to check something
• Ask Gemmbot for a fix, then validate it before merging the PR
• Share a small thing with someone internally or externally
• Create and iterate on a simple HTML file (like this deck)
• Quickly demo an idea in a client call or standup
08
Part 1 — Intro to Hosting

Proper Hosting

A persistent subdomain under gemmaanalytics.com.

What you get
Your own subdomain
e.g. mynewapp.gemmaanalytics.com — a real DNS A-record, HTTPS, and a server that stays up. Can include CI/CD pipelines, Docker, reverse proxy, etc.
When to use
Longer-lived prototypes
• You need it running for weeks or months, not just a few days
• A prototype that should work in pseudo-production (e.g. the HelloMed prototype)
• You want a proper-looking URL to share with a client
Prerequisite
You need to know what you’re doing
DNS, Docker, server config, maybe CI/CD. Available today but not self-service — coordinate with whoever manages the infra.
Option 3 WebGemms will enable exactly this — but with Claude Code knowing what to do out of the box. No DevOps knowledge needed. Until then, Option 2 requires manual setup.
09
Part 2 — Hands-On Exercises

Hands-On Exercises

Your turn. We'll get a prototype live together, step by step.

TODO
Confirm exercise setup, prerequisites, and accounts needed.
10
Part 2 — Hands-On Exercises

Deploy Your First Prototype

Step 1
Get the code / template
Placeholder — TODO: link to the starter repo or template.
Step 2
Push to the host
Placeholder — TODO: exact deploy steps for the chosen platform.
Step 3
Open your live link
Placeholder — TODO: confirm expected build/boot time.
Step 4
Share it
Placeholder — TODO: where to post the link (e.g. workshop Slack channel).
Note TODO — confirm exact steps and screenshots for the host chosen for this workshop.
11
Part 2 — Hands-On Exercises

Make It Yours — TODO Title

A second, slightly harder round — details TBD.

TODO
Define this exercise — e.g. swap the prompt/model, add a field, restyle the UI. Keep it small enough to finish live.
12
Part 2 — Hands-On Exercises

You Should Now Have…

  1. A live URL
    Placeholder — TODO.
  2. A prototype you can share
    Placeholder — TODO.
  3. A sense of the deploy loop
    Placeholder — TODO.
Note TODO — confirm this checklist matches what the exercises actually produce.
13
Part 3 — Outlook

Prototype Hosting vs. Production-Grade

A quick host is perfect for a prototype. When a client depends on it, the bar moves.

Dimension Fast Prototype Hosting Production-Grade
Access control Public link, maybe security by obscurity Proper reverse proxy, authentication, IP whitelisting, additional hardening
Deployment Manual push or Gemmbot CI/CD pipelines with automated checks and tests
Data Mock / synthetic data only Real client data — likely needs to live in client infrastructure
Reliability Best-effort, may go down Monitoring, logging, backups, recovery plan
Secrets Env vars, maybe hardcoded Proper credential management (1Password, vault, etc.)
Lifespan Days to weeks Months to years
Rule of thumb
Once a client depends on it, or real/sensitive data flows through it — move off the quick host. From there, Tech takes over for the production build.
14

Prototype fast. Host simply. Harden when it matters.

Intro to hosting — what it is, and the landscape of options.
Hands-On — deploy your first live prototype.
Outlook — from prototype toward production.

Next
TODO — follow-up resources, who to ask, and where prototypes go after this workshop.
1 / 14