brain
projects·source-summary

portfolio-neploy

Portfolio narrative for Neploy, "one-click deployment platform that abstracts infrastructure, CI/CD, and runtime config for early-stage builders." Status: Archived.

Key extractions

  • Thesis: "deploying a side project shouldn't require DevOps knowledge" — the gap between works on my machine and running in production is absurdly wide.
  • Three phases: Detection (framework + build plan from repo structure), Build (optimized multi-stage Dockerfiles), Deploy (AWS ECS + ALB + Route53 with zero-downtime rolling updates).
  • Trigger: git push. No dashboard, no config files.
  • Key decision: auto-detection over config files — requiring neploy.yml would defeat the purpose. Ask only for what can't be inferred.
  • Key decision: Docker as universal packaging — one abstraction regardless of language.
  • Key decision: AWS primitives over custom cloud — 90% value at 10% cost.
  • Hard problem: build detection across polyrepos (Next.js + Python ML + static site in one) — used scoring model across framework markers.
  • Outcome: deployment hours → seconds for early-stage projects.
  • Archival implicit: status "Archived" but reason not given.