---
title: "Discussion on \"A Zero-Cost Demo for a Cloud App\" | Hashnode"
description: "Discussion on \"A Zero-Cost Demo for a Cloud App\". A static demo site and a 3-minute video, so reviewers never need my EKS cluster running"
url: "https://hashnode.com/posts/a-zero-cost-demo-for-a-cloud-app/6ae62dd8cb002d4151be61fd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Zero-Cost Demo for a Cloud App](https://blog.jennasrunbooks.com/a-zero-cost-demo-for-a-cloud-app?utm_source=hashnode&utm_medium=feed)

A static demo site and a 3-minute video, so reviewers never need my EKS cluster running

Oct 31 · 4 min read · blog.jennasrunbooks.com  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#aws](https://hashnode.com/tag/aws)
-   [#vite](https://hashnode.com/tag/vite)
-   [#githubpages](https://hashnode.com/tag/githubpages)
-   [#testing](https://hashnode.com/tag/testing)
-   [#eks](https://hashnode.com/tag/eks)
-   [#developer-tools](https://hashnode.com/tag/developer-tools)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)

## Written by

[Jenna's Runbooks](https://hashnode.com/@jennasrunbooks)

@jennasrunbooks

  
[View profile](https://hashnode.com/@jennasrunbooks)

Cloud Engineer & SRE transitioning to AI/ML Platform Engineering | Writing on AI Infra, MLOps & DevEx

Hi there! I'm a Cloud Engineer and SRE, documenting my transition into AI/ML Platform Engineering. I write technical deep-dives, hands-on implementation guides, CLI helper scripts, and visual architectures covering cloud, infrastructure, orchestration, governance, and modern AI runtimes.

## Responses 3

Markdown supported · ⌘↵ to post

[DemoVexa](https://hashnode.com/@demovexa)

[Nov 2](https://hashnode.com/posts/a-zero-cost-demo-for-a-cloud-app/6ae62dd8cb002d4151be61fd/comment/6ae7fbe4b0f2d798f80941c1)

Moving INC-14 to the hand-approved path once the real run came back with medium confidence was the right call, and it makes the tour more convincing, since reviewers watch the policy gate actually doing its job. The piece I'd keep an eye on over time is the 3-minute video. The static site rebuilds from the same codebase on every change, but the video stays exactly as it was on the day of the EKS run. Putting the commit it was recorded from in the video description, and linking that from the banner, would let a reviewer tell whether a difference between video and click-through is a new feature or just an older recording.

[Jenna's Runbooks](https://hashnode.com/@jennasrunbooks)

[Nov 2](https://hashnode.com/posts/a-zero-cost-demo-for-a-cloud-app/6ae62dd8cb002d4151be61fd/comment/6ae7fbe4b0f2d798f80941c1#reply-6ae8c0ac074556c7a962c937)

Noting the commit SHA in the video description is a great idea since the application will likely continue to evolve, outpacing what's seen in the video. Thank you for the suggestion.

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Nov 1](https://hashnode.com/posts/a-zero-cost-demo-for-a-cloud-app/6ae62dd8cb002d4151be61fd/comment/6ae6ab4a589e9f7b4b59c050)

The dual-build separation check is the detail I would steal for any demo. Proving the production build has no mock code, and the demo has no real data, removes the two risks people usually worry about with a click-through demo.
