Projectmeetup

Built at [Seattle] Build with Akamai Cloud at GitHub Bellevue

Autonomous Cloud Architect

Autonomous Cloud Architect is a Chrome extension plus backend that adds an AI chat panel to cloud.linode.com. A developer types "I need a secure data scraping environment in Seattle," and the agent builds it across Akamai Cloud while they watch. User and task: developers and small teams who need a locked-down environment (server, network rules, storage, record keeping) without clicking through five Cloud Manager pages. What it does, with one sentence: - Creates a VPC and a 1 GB Ubuntu 24.04 Linode in Seattle. - Creates a default-drop Cloud Firewall that allows SSH only from the requester's own IP and HTTPS from anywhere. - Creates a private Object Storage bucket with a key limited to that bucket, and uploads a manifest. - Records the environment in Managed PostgreSQL. - Answers "what have I built?" from PostgreSQL, answers read-only account questions, and tears everything down on request. A full build takes about 35 seconds and a teardown about 23. - An Activity tab shows Akamai's own event history (done, in progress, failed) next to the chat. How the services are used: Akamai Inference (qwen3-8-27b) does tool calling and chains eight tools, passing real IDs between steps. Compute runs the backend 24/7 and hosts each environment. PostgreSQL is the environment registry that teardown depends on, plus a chat audit log. Object Storage holds an append-only JSON archive of every chat turn plus each environment's manifest. Firewall and VPC secure each environment. Technical choices: API keys stay on the backend and the extension holds only a shared key. Tool errors are returned as text so the model can recover. The agent protects what it runs on: it refuses to tear down its own host Linode, firewall, database and audit bucket unless the user types an exact confirmation phrase. Checked by: a full build and teardown through the extension backend; asking for something the agent has no tool for (a Kubernetes cluster), which it declined; and asking to delete an environment that does not exist, which it reported as missing. Known limits: plain HTTP with one shared key, fixed regions (Linode in Seattle, buckets in Chicago), one environment per VPC address, no login or per-user permissions, no retention rules on the audit logs.

// latest_project_recording.mp4
// Project brief

Autonomous Cloud Architect is a Chrome extension plus backend that adds an AI chat panel to cloud.linode.com. A developer types "I need a secure data scraping environment in Seattle," and the agent builds it across Akamai Cloud while they watch. User and task: developers and small teams who need a locked-down environment (server, network rules, storage, record keeping) without clicking through five Cloud Manager pages. What it does, with one sentence: - Creates a VPC and a 1 GB Ubuntu 24.04 Linode in Seattle. - Creates a default-drop Cloud Firewall that allows SSH only from the requester's own IP and HTTPS from anywhere. - Creates a private Object Storage bucket with a key limited to that bucket, and uploads a manifest. - Records the environment in Managed PostgreSQL. - Answers "what have I built?" from PostgreSQL, answers read-only account questions, and tears everything down on request. A full build takes about 35 seconds and a teardown about 23. - An Activity tab shows Akamai's own event history (done, in progress, failed) next to the chat. How the services are used: Akamai Inference (qwen3-8-27b) does tool calling and chains eight tools, passing real IDs between steps. Compute runs the backend 24/7 and hosts each environment. PostgreSQL is the environment registry that teardown depends on, plus a chat audit log. Object Storage holds an append-only JSON archive of every chat turn plus each environment's manifest. Firewall and VPC secure each environment. Technical choices: API keys stay on the backend and the extension holds only a shared key. Tool errors are returned as text so the model can recover. The agent protects what it runs on: it refuses to tear down its own host Linode, firewall, database and audit bucket unless the user types an exact confirmation phrase. Checked by: a full build and teardown through the extension backend; asking for something the agent has no tool for (a Kubernetes cluster), which it declined; and asking to delete an environment that does not exist, which it reported as missing. Known limits: plain HTTP with one shared key, fixed regions (Linode in Seattle, buckets in Chicago), one environment per VPC address, no login or per-user permissions, no retention rules on the audit logs.

// Built with
AkamaiAkamai Inference (qwen3-8-27b, tool calling), Compute (Linode), Cloud Firewall, VPC, Object Storage (S3 API), Managed PostgreSQL, Linode API (linode_api4 SDK)
// Watch & explore
// More from this event

Keep exploring what builders shipped.

All projects →

Bainbridge

hedgefinder

kalshi hedge

Sahil Bhatt's team

Retry Storm

# CascadeIQ Virtual resilience audit: **AI interprets** an incident → **deterministic simulation** → **AI mitigation** → **verified rerun**. Hackathon prototype (Akamai Seattle AI Hackathon, Nov 2026). **Repo:** https://github.com/Sahil9477/CascadeIQ **Demo:** http://127.0.0.1:8000/ (`uv run serve.py`) **Active branch:** `main` ## Judging ```text User and task: CS / cloud students (and judges) learning why retry storms break checkout paths; they run Lab 01, see the outage, pick a mitigation, and verify it. Benefit: Turns an abstract SRE failure into a hands-on lab: AI proposes, deterministic sim proves, shareable /runs/{uuid} for grading. Services: Akamai Inference (Qwen interpret + recommend; Gemma chart review); Managed Postgres (persist audit runs / share links); Linode Types API (published compute pricing beside outage loss). App can run on a Linode VM (deploy/) — laptop demo uses serve.py. Inference: qwen3-8-27b for scenario JSON + allowlisted mitigation; gemma-4-26b-a4b-it reads the before chart as a hint (metrics win). Checked by same-seed Python verify and fixture vs live flags (inference_used). Technical choice: Simulator owns truth — models never invent metrics; allowlist + re-sim with same seed so AI can’t fake a win. Our idea: Scenario-first teaching lab (Build → Cost → Break → Fix → Learn), two-model diagnose with Python as the judge. Demo: Start Lab → untick fixtures → Run audit → Ask Qwen → Verify → Save → open /runs/{uuid}. Known limits: No public Linode app URL until Nanode is provisioned; shared minute token budget (429); retry_cap_reduction may show clearer wins than backoff alone. ``` ## Team | Owner | Owns | |---|---| | **Sahil** | Deterministic simulator, Qwen interpret/recommend, FastAPI `/api/interpret\|audit\|recommend\|verify`, contracts/fixtures, Lab 01 + catalog/cost panel | | **Danny** | Interactive dashboard (`static/` instrument), Postgres `/api/runs`, `serve.py`, Linode `deploy/` | ## Quick start ```bash cd ~/Desktop/CascadeIQ git checkout main cp .env.example .env # paste AKAMAI_API_KEY + PG* from workshop / Cloud Manager (never commit .env) uv sync --extra dev uv run serve.py # Lab UI: http://127.0.0.1:8000/ # OpenAPI: http://127.0.0.1:8000/docs # Health: http://127.0.0.1:8000/api/health # Engine-only (no Postgres overlay): # uv run uvicorn cascadeiq.api.main:app --reload --port 8010 uv run pytest -q uv run python scripts/demo_flow.py # live Qwen + sim uv run python scripts/demo_flow.py --fixture uv run python scripts/smoke_runs_db.py # POST/GET /api/runs when PG* set ``` ### Lab 01: The Retry Storm Open `/` after `serve.py` starts. **Start Lab** loads the Gateway→Orders→Payments demo. Leave **Use fixtures** unticked for live Qwen/Gemma; tick it for offline rehearsal (`inference_used` is always shown honestly). Flow: Start Lab → **Run resilience audit** → **Ask Qwen for a mitigation** (Gemma chart review → informed recommend) → **Verify** → **Save** → open `/runs/{uuid}`. Play streams the audit timeline only after a baseline exists. Cost panel uses published Linode types (`GET /api/catalog/compute?region=us-sea`) beside simulated outage loss — never invents prices. ## API See [`docs/cascadeiq-api-contracts.md`](docs/cascadeiq-api-contracts.md) and [`contracts/`](contracts/). - `POST /api/interpret` — Qwen → scenario JSON - `POST /api/audit` — baseline sim time series + metrics - `GET /api/catalog/compute?region=us-sea` — published Linode types (`source: live|unavailable`) - `POST /api/chart/review` — Gemma reads the chart (advisory) - `POST /api/recommend` / `POST /api/recommend/informed` — allowlisted mitigation (optional visual note) - `POST /api/verify` — same seed + mitigation deltas - `POST /api/runs` · `GET /api/runs/{uuid}` — Postgres persist + share (via `serve.py`) Mitigations allowlist only: `bounded_exponential_backoff_seeded_jitter` | `retry_cap_reduction`. ## Layout ``` cascadeiq/engine/ # simulator + schemas cascadeiq/inference/ # Akamai Qwen client cascadeiq/api/ # FastAPI intelligence endpoints checks/ # Gemma chart review + informed recommend (Danny) cloud/ # Postgres /api/runs (Danny) serve.py # production entry: app + runs + static static/ # Lab UI + instrument deploy/ # Linode service + deploy.sh contracts/ fixtures/ ``` Do not commit `.env` or API keys. See [`deploy/PROVISIONING.md`](deploy/PROVISIONING.md) for Linode + Managed Postgres checklist.

Akamai

Heyo

CloudHand

# CloudHand CloudHand gives an AI agent a computer it can use from a browser. Run jobs on an Akamai cloud computer that keeps working after you close the tab, or use your Mac to open local apps and run tasks with your installed Codex skills. ## Try the demo 1. Open the [public judge workspace](https://cloudhand-judges.66-175-217-106.sslip.io/). No sign-in is required. 2. Ask **Calculate 27 × 14 in Calculator** and choose **Confirm action**. 3. CloudHand opens Calculator on Akamai and reports the result, **378**, in the chat. You can also find the completed run under **Akamai computer → Runs**. [Watch the 35-second walkthrough](CloudHand-Demo.mp4) ## Use your Mac Open the [local Mac workspace](http://127.0.0.1:4317/) while CloudHand is running on your Mac. Try **Open Notes on my Mac** or **Open Downloads in Finder**. Your Mac needs to be awake and have the permissions required for the action. To use an installed Codex skill, sign in to the Codex CLI on your Mac, choose **Model → Codex on this Mac**, then select a skill under **+ → Plugins & skills**. ## Run from source From the CloudHand repository, use Node.js 24, npm, and Python 3.10 or later. ```sh npm ci npm run build npm start ``` Open [http://127.0.0.1:4317/](http://127.0.0.1:4317/). Use `npm test` to run the automated checks.