Docker Stacks is now available in beta. You can deploy and manage Docker containers directly from the RunCloud dashboard without writing Compose files or manually configuring NGINX. 

Pick from a catalog of 24 pre-configured apps, including n8n, Uptime Kuma, Plausible, Grafana, Meilisearch, and Ghost.org, or deploy any image from a public or private registry. RunCloud sets up the domain, the reverse proxy, Let's Encrypt SSL, and the private network between your containers. You can also provision a MariaDB or Redis service and inject its credentials into your container.

• Push-to-deploy webhooks: Redeploy automatically when a new image is pushed to Docker Hub, GitHub Container Registry, or GitLab. You can filter by tag and require an HMAC signature.
• Automatic rollback: If a new image fails within 60 seconds of deploying, RunCloud restores the previous image and configuration.
• Registry credentials and Secrets Vault: Save registry logins once for the whole workspace. Secrets are encrypted, can't be read from the dashboard, and are mounted in containers as read-only files instead of as environment variables.
• Persistent volumes: Data in volumes is kept through restarts and image updates. Named volumes are also kept when you delete a stack, unless you choose to remove them.
• Monitoring: Each container shows CPU, memory, and network usage, with history going back up to 30 days.

Docker Stacks is available on the Business and Enterprise plans & runs on Containerized servers. It requires RunCloud Agent v2.20.0.

Learn more about Docker Stacks (Beta) in our documentation →

RunCloud Agent v2.20.0

What’s New

• New: Added native support for deploying and managing multi-service applications using Docker Stack.
• Fix: Resolved an issue where the autohealing process could be interrupted during cloud-init execution.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

RunCloud Agent v2.19.6

What’s New

• Fix: Fixed an issue where the slow-query threshold was never applied due to a formatting error
• Fix: Fixed containerized slow-query log path for Docker-based MySQL servers
• Improvement: Slow Query Monitoring now displays live results while monitoring runs (previously only after it ended)
• Improvement: Users can now edit php.ini and other extension INI files for containerized servers

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

What’s New

• Upgraded OpenLiteSpeed to v1.9.2

This release introduces support for the MKCALENDAR request method. Additionally, it strengthens HTTP/2 and HTTP/3 header validation, enhances Node.js process management.

For full upstream details, refer to the OpenLiteSpeed 1.9.x release log.

Deployment Information

• Automatic updates will roll out to all compatible servers within 72 hours
• No action required from users for the update process

RunCloud Agent v2.19.4 (Patch)

What’s New

• Fix: Resolved a bug that caused unintended additions or modifications to Redis keys during cloning operations.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

PHP Updates Now Available for NGINX

• PHP 8.5.10
• PHP 8.4.25

Note: If your server runs on OpenLiteSpeed, RunCloud does not handle PHP version updates. However, once a PHP version update becomes available for OpenLiteSpeed, it should also be automatically available on your server(s).

Access your terminal on any server directly in the browser with RunCloud Web Terminal. No SSH client, no key management, and nothing to install. 

Note: Web Terminal is off by default. Workspace owners can enable it with an 8-digit code sent via email, and each session requires a new 2FA challenge.

What's New

• Browser-based shell: A full interactive terminal in the RunCloud dashboard, on any machine, with no plugins.
• Scoped sessions: Launch from a server for a root shell, or from a web application to start in its directory, logged in as its system user.
• Shared sessions: Up to 10 people can join one session and type in it live.
• Command logging: Every command is recorded with the user who ran it. Logs are purged after 30 days.
• Automatic cleanup: Sessions close after 10 minutes of idle time, at 4 hours, or on disconnect. Up to 3 concurrent sessions per server.

Getting started

To get started, navigate to your server and look for the Enable Terminal option, as shown below:

Requires RunCloud Agent v2.19.0 or newer and 2FA on your account.

Learn more and get started with RunCloud Web Terminal ->

RunCloud Agent v2.19.3 (Patch)

What’s New

• Fix: Resolved an issue where overlapping cron processes prevented scheduled jobs from running.
• Fix: Addressed an issue where Ctrl+C became unresponsive during heavy output stream bursts.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

RunCloud Agent v2.19.0

What’s New

• Fix: Resolved a health monitoring issue that occurred when processing ⁠setfacl⁠ permission checks across a large number of web applications.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

RunCache 1.1.0 introduces CDN edge caching support for Cloudflare, including integration with Cloudflare page cache and Cloudflare APO (Automatic Platform Optimization). 

• CDN Edge Cache: A new section for managing Cloudflare page cache and Cloudflare APO from inside RunCache
• Fixed: Default cache rules not applying as expected
• Fixed: Scheduled purge and scheduled preload not always running on schedule
• Fixed: Preloading issues on archive, category, and other taxonomy pages
• Additional minor fixes and stability improvements

Note: RunCache Native refers to the version of RunCache that is available to RunCloud customers. 

You now decide which notifications RunCloud sends and where they arrive. Every notification type can be turned on or off per server, and routed to any of your channels: email, Slack, Telegram, Discord, or webhook.

What's new:

• Granular preferences: enable or disable any of 33 notification types across 6 categories, per server.
• Per-type channel routing: deliver each notification type to email, Slack, Telegram, Discord, or webhook.
• Zero-disruption defaults: everything stays on, matching current behavior. Existing server channel assignments migrate automatically.
• Email suppression with automatic recovery, so bounced addresses do not block future alerts.
• Audit logging for every preference change, so you can easily keep track of changes to notification preferences.

Note: Server notifications are delivered to the workspace owner's channels. Team members continue to receive invitation emails and in-app notifications.

Learn more ->