GitHub Integration for CI-Based Deploys

Feature Requests
1

One feature that would really unlock Nexlayer’s potential for production use is GitHub integration for CI/CD-based deploys.

Right now, the Playground is incredible for manual prototyping — but if I want to turn that into a real workflow, I’m still tied to the editor. A proper GitOps-style connection would let me automate deploys and treat my launchfiles like real infrastructure code.

This is what I imagine the ideal workflow to be:

  • Connect a GitHub repo (OAuth or PAT)
  • Pick a branch (main, staging, etc.)
  • On push, trigger a Nexlayer deploy with the latest launchfile.yaml
  • Deploy logs + result shown either in Nexlayer or back in a GitHub Action job
  • Bonus: nexlayer.yaml can include deploy targets, envs, and secrets reference

Example:

Let’s say I’m working on an OpenAI-based chatbot stack — it has:

  • A Next.js frontend
  • A FastAPI backend
  • A Postgres DB and Chroma vector store

I commit changes to main → GitHub Action kicks off → Nexlayer reads launchfile.yaml → deploys updated pods.

I don’t have to manually open the Playground every time, and I can use PRs to review infra changes just like app code.

Why This Matters

  • Enables team workflows — infra tracked, reviewed, and versioned in Git
  • Production-ready — I can ship confidently with every push
  • Seamless rollback — via Git history, not manual fiddling
  • Dev + Ops convergence — all from a single launchfile.yaml

this would be ideal for solo builders and fast-moving teams alike. Playground is already ahead of the curve on YAML DX… now it just needs the automation to match. Thanks!