preevy
Preevy is a CLI tool that automatically provisions ephemeral preview environments by deploying Docker Compose applications to cloud VMs or Kubernetes clusters. It integrates into CI/CD workflows to create per-PR environments accessible via public HTTPS URLs without manual DNS or certificate management.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | livecycle/preevy |
| Owner | livecycle |
| Primary language | TypeScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 2.2k |
| Forks | 89 |
| Open issues | 51 |
| Latest release | v0.0.67 (2025-06-30) |
| Last updated | 2026-02-06 |
| Source | https://github.com/livecycle/preevy |
What preevy is
Preevy provisions VMs (AWS Lightsail, GCP, Azure) or Kubernetes Pods, builds and deploys Docker Compose apps, and exposes services via a tunnel server providing HTTPS URLs. It requires Node.js 18+, Docker with Compose and BuildX, and cloud credentials; environments are managed via CLI commands.
Get the preevy source
Clone the repository and explore it locally.
git clone https://github.com/livecycle/preevy.gitcd preevy# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Git repository initialization (at least one commit) to calculate stable environment IDs; use --id flag as fallback.
- Cloud credentials must be configured locally (aws configure, gcloud auth, az login) before first deployment; credentials remain on user machine.
- Profile setup (preevy init) must select a deploy target (AWS Lightsail, GCP, Azure, or Kubernetes) and storage location; local storage available for trials.
- Docker Compose files can include x-preevy configuration blocks for environment-specific customization (e.g., resource limits, access controls).
- CI integration requires adding preevy commands to pipeline workflows; documentation mentions example repos but no pre-built CI templates detected in README.
When to avoid it — and what to weigh
- No Docker Compose Definition — Preevy requires a Docker Compose file as the source of truth. Applications not containerized or using alternative deployment definitions need refactoring.
- Cost-Sensitive with High PR Velocity — Ephemeral environments per PR incur cloud costs (VMs/Pods). Teams with very frequent PRs or tight budgets should evaluate cost implications against savings from reduced bugs.
- Complex Multi-Tenant or Long-Running Infrastructure — Preevy is optimized for ephemeral, stateless environments. Applications requiring persistent databases, complex networking, or long-lived state may require additional setup.
- Minimal or Proprietary CI/CD Pipelines — Integration assumes standard CI runners (GitHub Actions, GitLab CI, etc.). Highly custom or air-gapped CI systems may require significant adaptation.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI-approved license allowing commercial use, modification, and distribution with liability disclaimers and trademark restrictions.
Apache-2.0 permits commercial use. However, Preevy also appears linked to Livecycle (a company offering hosted services). Commercial deployment should clarify whether hosted tunnel services, storage, or integrations incur separate licensing fees beyond the open-source CLI tool itself. Requires review of Livecycle commercial terms.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Strong |
| Assessment confidence | High |
README states credentials remain local on user machines and are not sent externally. Private environments and network isolation options mentioned but not detailed in excerpt. Public environments expose services to the internet; access control mechanisms not fully documented in excerpt. Livecycle tunnel server data handling mentioned under 'Livecycle access to data' section but content not provided. Evaluate tunnel server security posture and whether sensitive data transits external infrastructure.
Alternatives to consider
Vercel / Netlify Preview Deployments
Purpose-built for frontend/Jamstack; automatic previews tied to Git. Simpler for static/Next.js apps but vendor lock-in and limited backend support.
Argo CD / Flux with GitOps
Full-featured CD with multi-env support and GitOps principles. Higher operational complexity and requires Kubernetes; better for long-lived infrastructure.
Heroku Review Apps or Cloud Run
Managed preview environments with lower operational burden. Less flexible, higher cost, and tied to specific platforms.
Build on preevy with DEV.co software developers
Preevy automates ephemeral environment provisioning for every pull request. Deploy to your cloud with one command and share live, interactive previews.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
preevy FAQ
Does Preevy store my cloud credentials?
Can I use Preevy with an existing Kubernetes cluster?
What cloud providers are supported?
How are preview environments accessed?
Software developers & web developers for hire
DEV.co helps companies turn open-source tools like preevy into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source devops stack.
Simplify PR Reviews with Instant Preview Environments
Preevy automates ephemeral environment provisioning for every pull request. Deploy to your cloud with one command and share live, interactive previews.