DuckOps scaffolds the code, creates the GitHub repo, deploys it to Kubernetes, wires a Jenkins pipeline and starts health checks. Every stage streams live to your dashboard. No YAML to write, no glue to maintain.
New project
my-apiLanguage
Framework
Database
ORM
Think of DuckOps as a transfer line. Your project rides it from station to station, and each one does a real job before the lamp turns green.
project saved, job queued
code rendered from templates
pushed to GitHub
image built, namespace by Terraform
Ansible deploys to Kubernetes
Jenkins job created
first build running
/health every 30 s
Choose a framework, a language and an ORM. Every template ships with a landing page that shows the API status and its routes.
TypeScript or JavaScript · Prisma, Drizzle or raw SQL
TypeScript or JavaScript · Prisma, Drizzle or raw SQL
Vite build served by nginx
Vite build served by nginx
Node standalone server
Next.js 15 + Express 5 API + Prisma in one repo
Dockerfile
A production image, built and pushed to the cluster registry.
Jenkinsfile
Build, push and rolling update on every commit, with live logs.
Kubernetes manifests
Deployment, Service and Ingress, applied by Ansible.
Health checks
/health is pinged every 30 seconds and shown on the dashboard.
Ask for a feature in plain words. The AI service writes the code into your repo, streaming as it goes, and the commit goes through the same Jenkins pipeline as yours. Give it a first prompt when you create a project and it runs once the app is live.
A TypeScript monorepo. The provisioning service runs a BullMQ queue that survives restarts and retries on failure, and drives GitHub, Terraform, Ansible and Jenkins.
Sign in with GitHub and get your first project running on Kubernetes.