Smoooth v0.1.0

Moving from Coolify or Docker Compose

Migrate production stacks in seconds with zero downtime, automatic database volume safeguards, and over 1.3 GB of RAM instantly reclaimed on your VPS.

Scenario // Solo SaaS & Indie Founders

Eliminate OOM build crashes on $5/mo VPS nodes

Coolify consumes 1.4 GB RAM just idling with PHP, Laravel Horizon, and internal daemons. When Next.js builds trigger on a 2 GB VPS, the Linux kernel terminates your Postgres database.

  • 1.35 GB RAM Reclaimed: Smoooth idles at under 28 MB.
  • Volume Lock: Automatic pgdata retention prevents data loss.
  • Zero-Downtime TLS: Embedded Caddy with sub-second ACME.
View complete Indie Hacker playbook →
terminal — smoooth migrate coolify bash
# 1. Preview detected Coolify Next.js + Postgres stack
$ smoooth migrate coolify /data/coolify/services/saas-prod
✓ Detected Coolify Service: Next.js 15 App + Postgres 16 + Redis
• Target Ingress: https://app.indiesaas.com (auto Caddy route)
• Volume: /var/lib/postgresql/data → is_persistent: true [LOCKED]
# 2. Apply transactional migration
$ smoooth migrate coolify /data/coolify/services/saas-prod --apply
✓ PostgreSQL 16 ready (port 5432 healthy)
✓ Redis 7 ready (in-memory caching layer active)
✓ Next.js 15 container healthy (HTTP 200 on /)
✓ Ingress route cutover successful. Reclaimed 1,380 MB RAM.

Technical Architecture & Efficiency Comparison

Verified on Ubuntu 24.04 LTS (x86_64, 2 vCPU, 4GB RAM).

Dimension Coolify v4 Smoooth Runtime
Idle Memory Overhead 1,200 – 1,800 MB RAM < 28 MB RAM (98% reduction)
AI Agent Native Access None (Web dashboard only) Native Model Context Protocol (MCP)
Reverse Proxy & TLS Traefik (label parsing, file race risks) Embedded Caddy (sub-ms route reload)
Stateful Volume Safeguards Generic Docker volumes Dedicated Database Adapters + Volume Locks
Zero-Downtime Host Adoption Requires container restart Live Container Scanner (in-flight adoption)