Skip to content

Igniters - Week 4 - Alex financial planner multi agent on GCP#143

Open
SectumPsempra wants to merge 1 commit into
ed-donner:mainfrom
SectumPsempra:week4-exercise
Open

Igniters - Week 4 - Alex financial planner multi agent on GCP#143
SectumPsempra wants to merge 1 commit into
ed-donner:mainfrom
SectumPsempra:week4-exercise

Conversation

@SectumPsempra
Copy link
Copy Markdown

Summary

  • Adds alex_financial_planner/, a full-stack multi-agent AI financial planning application deployed on GCP using OpenRouter for all LLM calls
  • Implements a six-agent pipeline: Planner, Instrument Tagger, Report Writer, Chart Maker, Retirement Specialist, and an autonomous Researcher that runs on a schedule
  • Deploys all services to Cloud Run with full infrastructure managed in Terraform

Details

1. Backend (backend/)

  • database/ — Cloud SQL PostgreSQL schema with pgvector for semantic search, asyncpg client with lazy connection pooling
  • agents/ — FastAPI service hosting five specialised agents; the Planner fans them out concurrently via asyncio.gather and writes results back to the jobs table
  • researcher/ — Separate FastAPI service that autonomously searches for financial news, generates embeddings, and stores them in the knowledge base
  • api/ — User-facing REST API handling auth (Clerk JWT), account/position CRUD, job triggering via Cloud Tasks, and job status polling

2. Frontend (frontend/)

  • Next.js app with Clerk authentication, portfolio management pages, and a polling-based analysis results view with charts

3. Infrastructure (terraform/)

  • Four Terraform modules: Cloud SQL + service account, Researcher + Cloud Scheduler, Agents + Cloud Tasks queue, API + Frontend Cloud Run services

4. Deployment (deploy.sh)

  • Single idempotent script that enables APIs, provisions infrastructure, runs DB migrations via Cloud SQL Auth Proxy, builds and pushes linux/amd64 Docker images, and deploys all services

Screenshots

Screenshot 2026-04-30 at 2 37 44 AM Screenshot 2026-04-30 at 2 38 05 AM Screenshot 2026-04-30 at 2 38 13 AM Screenshot 2026-04-30 at 2 38 32 AM

@iamumarjaved please review, as week 4 assignment is a multi-agent extension of the week 3 exercise the repo points to the same url where initially a single agent was developed and then it was further enhanced with multiple agents, I have kept a single deployment resource to save costs on GCP. Thanks!

@iamumarjaved
Copy link
Copy Markdown

iamumarjaved commented Apr 30, 2026

@SectumPsempra I believe final Week was supposed to be deployed on AWS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants