Helipack is Helipod's internal build engine that detects frameworks from your repository and generates production-ready Dockerfiles — with multi-stage builds, build secrets, and security best practices.
Helipack scans the repository and detects frameworks from configuration files, dependencies, and project structure.
Generated Dockerfiles use multi-stage builds to minimize production image size.
Environment variables used during build are not stored in image layers using BuildKit secrets.
Non-root user, tini init process, and optimized layer caching — all configured automatically.
FrankenPHP for Laravel 8.2+, standalone mode for Next.js, gunicorn for Python — optimized per framework.
Layers are arranged by change frequency. Dependencies rarely change, source code changes often — builds are fast.
Connect your GitHub/GitLab repo. Helipack starts scanning files in the repository.
Helipack reads composer.json, package.json, requirements.txt, and config files to detect the framework.
An optimal multi-stage Dockerfile is generated automatically — with security best practices.
The Docker image is built with optimal caching, then deployed to production.
Guides and tutorials related to this feature.
Helipack supports Node.js (Next.js, Nuxt, Remix, Astro, Express, NestJS), PHP (Laravel, Symfony), Python (Django, FastAPI, Flask), and Go (Gin, Echo). For other languages (Rust, Ruby, Java), use your own Dockerfile.
Check Build Logs during deploy. Or for local development, set HELIPACK_KEEP_DOCKERFILE=1 before build — Helipack will save the file as .helipack.Dockerfile.
Create a helipack.json file in the repository root to override build command, start command, port, health check, packages, and more. Read the full guide on the blog.
Yes. All Dockerfiles use BuildKit secrets (env vars not stored in layers), non-root user, and tini init process for graceful shutdown.
Start now, no credit card required. Just connect your repo and see how fast you can deploy.