The Docker Compose-based CI/CD pipelines make deployment predictable — what runs locally is exactly what runs in production, no surprise buildpack behavior. We migrated a Nuxt frontend + Directus CMS setup across several pipelines, including a monorepo restructuring, and Elestio's support team was fast and precise when we ran into edge cases (e.g. how to correctly structure a Docker Compose pipeline sourced from a monorepo subdirectory). The blue-green style workflow — spin up a new pipeline, verify it, then cut the domain over — made a risky migration low-stress, since rollback was always just a domain change away. Yes, for our use case it's worth it. We're running multiple services (CMS, frontend, internal tools) on a single managed VM instead of paying separately for hosting plus a CI/CD platform plus managing our own reverse proxy/SSL — that consolidation alone offsets the cost. The ability to add pipelines without provisioning new infrastructure each time, and to do zero-downtime cutovers between versions, has saved us real engineering time. If you're running a handful of small-to-medium services and want managed infra without a large DevOps overhead, the pricing scales reasonably compared to piecing together separate hosting, CI/CD, and reverse-proxy tools yourself. Review collected by and hosted on G2.com.

Honestly hard to find real complaints — the platform has been solid for our use case. If I had to nitpick, some of the more advanced pipeline creation flows (e.g. automating setup via their API/integration tooling) took a bit of back-and-forth with support to get exactly right, but that was resolved quickly and didn't slow us down in any meaningful way. Review collected by and hosted on G2.com.