Calgary Innovation Week 2026 — HQ Submission
Platform Calgary’s call for facilitators. Theme: “Build It.” Our play — a live build lab that showcases Code to Cloud engineering, then has every attendee ship a real AI app and learn to secure it.
Ship It Safely — build a real AI app live, then learn why “it works” isn’t “it’s safe”
A hands-on build lab that opens with a jaw-dropper: we deploy a real, AI-powered app to the global edge live, in minutes — an unmistakable showcase of what serious engineering looks like now. Then the room builds their own. Provocative thesis: AI will write you working software AND real security holes in the same breath — and almost nobody teaches the second half. We do. That’s the difference between a demo and a product a real engineer would ship.
- Build and deploy a real, working AI app live — no coding background needed.
- Spot the security holes AI silently writes (the handful that actually bite) and close them on the spot.
- Leave with a reusable “ship-it-safely” checklist — the judgment layer AI can’t supply.
The Wow
I build and deploy a real, AI-powered app to the global edge — live, in front of the room. The thing that looks like a team-and-a-month, shipped in minutes. This is the engineering showcase.
You Build
The room builds their own: a live “idea validator” app — an AI-generated landing page that captures real email signups to a database, deployed to a real URL. No coding background needed; we facilitate and unblock the whole way.
Ship It Safely
The part every “build with AI” session skips. AI didn’t just write working code — it wrote real security holes. We find them and close them together, with the depth that separates a real engineer from a vibe-coder.
What everyone builds
— a real app, not a static pageThe AI “idea validator”. A real full-stack app: an AI-generated landing page + a live email-capture waitlist saved to a database, deployed to a real URL. Everyone at Innovation Week has an idea to test — this ships it.
- →Leaked AI API key in the browser → a stranger drains your account (the classic 2026 mistake).
- →World-readable signup database → anyone can pull everyone’s emails (an Alberta PIPA privacy problem, not just a bug).
- →No input validation → spam and injection straight through your form.
Why we can actually pull this off
Real apps, real production
We ship AI apps to the global edge for a living. This very platform — an AI assistant answering from live data, a double-entry books engine, e-signing with a legal audit trail — runs on that stack. We teach from what we run.
Security is our actual lane
25+ years across military communications, cloud engineering and cybersecurity, plus CNCF Ambassador. The “close the holes” half is our home turf, not a bolt-on.
Capability transfer, not a pitch
Everything demoed, the room rebuilds and takes home. The differentiator isn’t a secret tool — it’s the judgment, and we hand it over.
Tangible takeaway
A live AI app they built plus a security checklist they can reuse on anything AI helps them build.
The differentiator
Everyone can pitch “build with AI.” Only a 25-year cloud + security operator teaches shipping it safely.
Breaks the mold
A live build-and-secure lab, not a panel. We watch AI write a vulnerability — then close it together.
Portal answers — copy & paste
Event Title
Ship It Safely: Build & Launch a Real AI App in 90 Minutes
Event Description
Objectives · target audience · what to expect
A hands-on build lab that opens with a jaw-dropper: in front of the room, we build and deploy a real, AI-powered app to the global edge — live, in minutes — an unmistakable showcase of what serious engineering looks like in 2026. Then the room builds their own: a real "idea validator" app — an AI-generated landing page that captures real email signups to a database, deployed to a live URL. Everyone at Innovation Week has an idea to test; this ships it. Then we do the part every "build with AI" session skips. AI didn't just write you a working app — it quietly wrote you real security holes. We find them together and close them, live, with the depth that separates a demo from something a real engineer would ship. No coding experience required; a browser is all you bring. Objectives: (1) build and deploy a real AI app, hands-on; (2) learn to spot the handful of security mistakes AI silently introduces — the ones that actually bite — and fix them; (3) leave with a reusable "ship-it-safely" checklist, the judgment layer AI can't supply on its own. Target audience: tech-curious Calgarians, career-changers, and founders without a technical co-founder — anyone who wants to build, and to build without getting burned. We facilitate the whole way: you build, we unblock, and you leave with a live app you can safely show the world that night.
What does the attendee walk away with?
Tangible take-away — can they apply it right away?
Two things, both usable that day: (1) a live, working AI app they built themselves — a real, publishable URL that collects real signups, not a mockup; and (2) a plain-language "ship-it-safely" checklist they can apply to anything they build with AI from now on. The app is shippable immediately. The security checklist is the part that keeps a founder's first launch — or a career-changer's portfolio project — from leaking its users' data the week it goes live. They leave able to build, and able to not get burned doing it.
How does your session center and elevate underrepresented perspectives / new voices?
Two barriers usually keep new voices out of building: you supposedly need a CS degree to write code, and you need a specialist to make it secure. This session removes both. It's designed first for non-coders, career-changers, and solo founders without technical partners — and it hands them the security judgment normally gate-kept to professionals. My own path is non-traditional (military signals operator → cloud engineer → AI), and I facilitate for the room that's never written a line of code, not the room that already has. The result: people who were only ever allowed to watch leave able to build — and to build responsibly.
How will your session break the standard conference mold?
Two ways. First, the format: it opens with a live engineering showcase — a real AI app built and deployed to the global edge in minutes, in front of the room — then hands the tools to the audience so they build their own. No slides, no panel. Second, the idea: AI will happily write you working software AND real security holes in the same breath, and almost nobody is teaching the second half. Every other "build with AI" session stops at the demo; we keep going. We let AI write a real vulnerability, spot it as a room, and close it together. The audience doesn't watch someone build — they build, they break, they fix, and they leave with the receipt (a live app) and the judgment to keep it safe.
Industry jargon / technical language level — and support
Rank: High / Medium / Low
Low. No prior technical or security knowledge assumed. Every term — including the security concepts — is explained in plain language the moment it comes up, backed by a one-page cheat sheet, and we circulate to unblock anyone who gets stuck so no one is left behind. If you can use a web browser, you can complete this session.
Target Audience
Multi-select in the portal
Tech Curious Calgarians AND Founders (Tech Professionals also welcome).
Event logistics
— locked in; adjust on the form if needed| Field | Suggested | Note |
|---|---|---|
| Date | Tue, Nov 3 (Talent & Careers day) | Best-fit audience; Flexible: YES on the form |
| Duration | 90 min (e.g. 1:00–2:30 pm) | Enough time to actually ship |
| Format | Workshop / hands-on build lab | Not “presentation” |
| Anticipated attendees | 30 | Right size for a facilitated hands-on lab |
| Chairs for presenters | 1 | 2 if you co-facilitate |
| Mics | 1 | |
| Catering | No · 0 tables | Change if you want refreshments |
Host under Code to Cloud, in a personal / community capacity, and keep the tooling vendor-neutral (not a single-cloud showcase). That keeps this squarely inside the community & speaking work already disclosed — and away from any employer conflict-of-interest question.
Next steps
- 1.Concept, day (Tue Nov 3), and size (30) are locked — review the copy once and you’re ready.
- 2.Paste the answers above into the HQ Programming Request portal — copy each, or grab them all at once.
- 3.Submit before Jul 29. Questions: innovationweek@platformcalgary.com
- 4.Status arrives in August. If selected, prep the build-lab runbook + jargon cheat sheet.