Managing deployments

Once your application is running, the Clouve dashboard is where you monitor its health, apply updates, and control its lifecycle. This page covers day-to-day operations for business users.


The deployment dashboard

The main dashboard shows the following for each deployment:

ElementDescription
StatusWhether the application is Running, Stopped, or has an issue
URLThe HTTPS link to open the application
VersionThe currently running version
Last UpdatedWhen the deployment was last changed

Click a deployment to open its detail view, which has more information and the available actions.


Monitoring your application

Status indicators

StatusMeaningAction needed?
RunningAll components are healthyNone
StartingApplication is starting upWait; this usually resolves in a few minutes
DegradedSome components have issues, but the app may be partially functionalContact support
StoppedApplication has been manually stoppedStart it from the dashboard
FailedApplication has crashed and cannot auto-recoverContact support

The platform restarts crashed containers automatically. A container that crashes repeatedly (three or more times in quick succession) shows Failed and needs investigation.

Automatic recovery

The platform monitors your application continuously with health checks. If a container stops responding:

  1. Kubernetes attempts to restart the container
  2. If restarts resolve the issue, the status returns to Running on its own
  3. If restarts don't help after several attempts, the status changes to Failed

The platform handles most transient issues, such as temporary network glitches or brief resource spikes, without any action from you.

Outage emails

Clouve checks the address of each running deployment every 5 minutes, along with each custom domain you've added to it. If one stops responding for about 10 minutes, every Administrator in your organization gets an email saying the application isn't responding, and a second one when it responds again. The second email only goes out if the first one did.

The times in these emails run late. The time the first email gives for the start of the outage can be 10 to 20 minutes after the application stopped answering, and the outage length in the second email is short by about as much.

Clouve doesn't send these emails for the AI Assistant's address. Clouve's own team is alerted about outages as well.


Applying updates

When a new version of an application is available in the marketplace, an Update Available notification appears on the deployment card.

An update may contain security patches for known vulnerabilities, bug fixes, new features, or newer versions of the underlying software. Apply security patches promptly.

How to update

  1. Open the deployment detail view
  2. Click Update to Version X.Y.Z
  3. Review the change summary (if provided)
  4. Click Confirm Update

The platform then:

  1. Downloads the new application version
  2. Starts new containers alongside the existing ones
  3. Shifts traffic to the new containers once they're healthy
  4. Removes the old containers

This sequence keeps downtime to a minimum. In most cases the application stays accessible throughout the update, though brief interruptions (typically 10 to 30 seconds) are possible during the transition.

Before updating

If you have a non-production workspace, apply the update there first to verify everything works before touching production. Schedule major updates for low-traffic periods, and for applications with many users, announce the planned update window in advance.

If an update fails

The platform rolls back to the previous version automatically and your data is preserved. Contact support with the error details.


Starting and stopping a deployment

Stopping a deployment

Stopping an application shuts down all its containers while keeping all data. Do this when the application isn't needed for a while, when you want to reduce resource usage, or when you need to perform maintenance.

From the deployment detail view, click Stop Deployment.

Important: Stopping a deployment does not delete any data. Everything stored on the persistent volumes (database records, uploaded files) is preserved, and the application can be restarted at any time.

Starting a stopped deployment

Click Start Deployment in the deployment detail view. The application goes through the same startup sequence as an initial deployment, so expect 3 to 10 minutes before it is fully available.


Cloning a deployment

Cloning makes a copy of a deployment, data included. The copy is a new deployment with the same title, its own number and its own Clouve address. Custom domains aren't copied.

You can clone a paid deployment, a pending one, or one in an organization with free services. A free trial can't be cloned, and its Clone icon in the deployments list is crossed out. You also can't clone a deployment while its status in the deployments list is Open or In Progress. The status is In Progress while an action runs and Open after one fails. You need a verified email address to clone.

To clone a deployment, click Clone on its page, or the Clone icon on its row in the deployments list, then click Proceed. If you manage client organizations as a partner, you first choose the organization the copy goes to.

The copy starts as a free trial unless the organization it goes to has free services, and a free trial can only be X-Small. So a larger deployment can't be cloned into an organization without free services. The copy runs in the same region as the original, so you can't clone into an organization whose new deployments go to another region. The organization's admins get an email about the copy.


Deleting a deployment

Deleting a deployment permanently removes all application containers, all application data (databases, uploaded files, configuration), and the workspace's HTTPS URL assignment.

This action is irreversible. Before deleting, export any data you need to keep (download database dumps, export files, or use the application's built-in export features), confirm with your team that no one is still using the application, and make sure important data has a backup copy.

To delete a deployment, open the detail view, click Delete, type the deployment name to confirm, then click Confirm Delete.


Data export and backup

Persistent volumes protect your data against container failures. Backups are not switched on by default: on a paid plan, use the deployment's Backups tab to schedule them (daily, weekly or monthly) or take one on demand. For business-critical data, also export regularly.

How to export data

WordPress:

  • Use the built-in Tools → Export to export content as XML
  • Use a plugin like UpdraftPlus for full database + file backups

Moodle:

  • Go to Site Administration → Server → Backup → Automated Backup to configure scheduled backups
  • Manually: Site Administration → Courses → Restore

SuiteCRM:

  • Admin → Studio for schema exports
  • Use the import/export functionality in each module

Odoo:

  • Use the Backup Database feature in Settings → Technical → Database Structure → Backup

For scheduled or on-demand backups of the whole deployment, use the Backups tab (paid plans).


The AI Assistant

Some applications offer an AI Assistant: a helper that works inside your deployment and can set up and look after the application when you ask it to. Listings that offer it show an AI Assistant badge and its monthly price next to the application's own price. On a paid plan, the AI Assistant's price includes a monthly AI usage allowance. Clouve provides the AI model access, so you don't need an API key or an account with an AI company. A free trial, or an organization with free services, gets the AI Assistant at no charge but with no AI usage included. You use it with your own Claude subscription.

Adding it

  • New paid deployments: checkout has an Add the AI Assistant box, checked by default. Clear it to deploy without the AI Assistant.
  • Free trials: the install form has the same box, checked by default and marked Free during the trial. Clear it to install without the AI Assistant.
  • Organizations with free services: the box on the install form is marked Free for your organization. Clear it to install without the AI Assistant.
  • Subscribing after a trial: checkout offers the box at its monthly price. It starts checked if the AI Assistant is on in your trial and cleared if it's off, so check it to add the AI Assistant. If the AI Assistant is on, leave the box checked to keep it on. From then on you pay the monthly price and get the monthly AI usage allowance. If you're signed in with your own Claude subscription, the AI Assistant keeps using that. It restarts once when your subscription starts, which takes about a minute, and it keeps its files and chat history. If you clear the box, it turns off when your subscription starts.
  • Existing deployments: open the deployment's AI Assistant tab and choose Turn on the AI Assistant. On a free trial or with free services, it turns on right away at no charge. On a paid plan, today's charge covers the AI Assistant for the rest of your current billing period, and you get a partial usage allowance to match. From your next bill, you pay the full monthly price and get the full allowance. The tab shows today's charge and your new monthly price before you confirm.

Monthly usage

On a paid plan, every month includes an AI usage allowance. The AI Assistant tab shows how much of it you've used, as a percentage, and the date it resets. Your organization's admins get an email when 80% is used and another when it runs out.

To get more, choose Buy more. It adds more usage right away and is charged once, to your own saved card or a card you enter. Anything you haven't used when the allowance resets is gone, including usage you bought.

Using your own Claude subscription

On a free trial, or in an organization with free services, the AI Assistant comes with no AI usage. To use it, you sign in to the AI Assistant with your own Claude subscription. Until you do, the AI Assistant shows this notice: "No AI usage is included with this deployment. Sign in with your own Claude subscription to use the AI Assistant. Type /login to sign in." With no allowance, the AI Assistant tab has no usage meter and no Buy more.

On a paid plan, signing in is optional. While you're signed in, the AI Assistant uses your subscription, and the allowance covers any time you're not.

Turning it off

Choose Turn off on the AI Assistant tab. On a paid plan, the AI Assistant keeps working until the end of the period you've paid for, then switches off, and your monthly price drops from the next bill. There's no refund for the current period. If you change your mind before then, choose Keep it on; there's no charge. On a free trial or with free services, it switches off right away.

Clouve keeps its files and chat history while it's off, so you can turn it back on later and carry on where you left off.


Managing multiple deployments

If your organization runs several deployments (different applications, or the same application in different workspaces), the dashboard lists all of them, organized by workspace. Production and staging environments appear under their own workspace headings, and the search bar and category filters help you find a specific deployment quickly.


User access and permissions

Each person in your organization is either an Administrator or a User. Administrators choose who else is one on the Users page, so ask one of them if your role needs to change.

  • Administrator: can do everything a User can, manage the organization's users, and make purchases: subscriptions, paid size changes, the AI Assistant and extra AI usage, and the organization's payment methods.
  • User: can start free trials and work with the organization's deployments: start and stop them, back them up, and run the other actions that cost nothing. Instead of a buy button, a User sees a note asking them to have an Administrator make the purchase. A User who pays for one of the deployments on their own card can still update that card under Profile > Payment Method.

Common management tasks

I need to change the application password

Log in to the application itself and use its built-in password change function. The platform does not provide a way to reset application-level passwords; that is handled within the application.

The application is running but slow

Performance issues usually have one of these causes:

  1. Resource limits: the container may not have enough memory or CPU. Contact your administrator to increase the resource allocation.
  2. Application-level issues: too many plugins, unoptimized queries, or misconfiguration inside the application. Check the application's performance settings.
  3. Traffic spikes: performance may degrade when many users hit the application at once. Contact your administrator about scaling options.

I need to move the application to a different cloud region

This requires administrator involvement. Contact your Clouve administrator with the request.

The application shows an error page

  1. Check the deployment status in the dashboard; the application may be restarting
  2. Wait 2 to 3 minutes and try again
  3. If the error persists while the status shows Running, contact support with a screenshot of the error

Next steps

Moodle, Gibbon, Odoo, SuiteCRM, WordPress, ownCloud and other product names are trademarks of their owners. Clouve is not affiliated with or endorsed by them. LimeSurvey is a registered trademark of LimeSurvey GmbH, Germany. Clouve is not affiliated with or endorsed by LimeSurvey GmbH.