Skip to content

Managing Managed App instances

A guide to managing your Managed App instances through the DanubeData dashboard — viewing status, creating the admin account, managing custom domains, upgrading plans, creating snapshots, and viewing metrics.

Prerequisites

Instance list

Navigate to Apps in the sidebar to see the app catalog and all your instances.

App catalog

The top of the page displays the available applications as cards. Each card shows the app name, category, and a brief description. Click Deploy to create a new instance of that app type.

Instance table

Below the catalog, the instance table shows all your existing instances.

ColumnDescription
Instance nameClick to open the instance detail page
App typeWordPress, n8n, or Ghost
StatusCurrent lifecycle state
Access URLDirect link to your app (opens in new tab)
RegionDatacenter location (FSN1)
Monthly costCurrent plan price in EUR
CreatedDate the instance was created
ActionsDropdown with View details, Edit configuration, Restart, and Delete

Searching instances

Use the search bar above the table to filter instances by name, app type, status, or subdomain. The filter applies instantly as you type.

Real-time status updates

The dashboard updates automatically when an instance changes state. Status changes appear within seconds as your instance moves through the lifecycle (Pending, Provisioning, Running). If another team member deletes an instance, it disappears from the list automatically.

Instance detail page

Click any instance name to view its full details. The detail page includes Overview, Monitoring, Backups, and Settings. Ghost instances also have an Email (SMTP) tab, and n8n instances a Parameters tab.

Overview tab

Instance details card

Displays instance information at a glance:

  • App type — WordPress, n8n, or Ghost
  • Plan — Current resource profile name (Starter / Professional / Business / Enterprise)
  • CPU / Memory — Allocated resources
  • Parallel workflows — Concurrent workflow limit (n8n only)
  • Monthly cost — Plan price
  • Version — Application version
  • Datacenter — FSN1 (Falkenstein, Germany)
  • Created — Date and time the instance was created
  • Deployed — Date and time the instance reached Running state

Access card

Contains everything you need to connect to your application.

Access URL — The full URL to your instance (e.g., https://my-blog.apps.danubedata.ro). Click the copy button to copy it to your clipboard, or click the external link icon to open it in a new tab.

Admin account — WordPress, n8n, and Ghost each create their admin account the first time they are opened, so the page shows no username or password for them. It shows where the app's setup screen is and, once the instance is running, a Create the admin account link. Create the account as soon as the instance is running: until it exists, whoever opens the setup screen first becomes the app's administrator.

An app that does keep an admin login shows its username, and keeps the password hidden until you choose Show the password. Only the project owner and administrators can do that. An editor can open and manage the app, but the card tells them to ask an owner or administrator for the password.

Custom domains card

Shows the default domain and any custom domains you have added.

  • Default domain — Your {subdomain}.apps.danubedata.ro URL, always available with managed TLS
  • Custom domains — Listed with their verification status and TLS status badges
  • Manage Domains — Link to the full domain management page

Monitoring tab

Displays real-time performance metrics for your instance:

  • CPU usage — Current and historical utilization
  • Memory usage — Current and historical consumption
  • Network traffic — Inbound and outbound data

Use the time range selector to view metrics over different periods.

Email (SMTP) tab (Ghost)

Connect your own SMTP provider to send Ghost password resets and staff invitations. A project owner or administrator can manage this connection.

  1. Open your Ghost instance and select Email (SMTP).
  2. Turn on Enable SMTP and enter your provider's public SMTP hostname, username, and password.
  3. Select the port and encryption your provider requires: STARTTLS on port 587 or 2525, or TLS on port 465. Unencrypted SMTP is not supported.
  4. Enter a sender email address verified with your provider, and optionally a sender name.
  5. Select Save and apply. Ghost restarts and your site is briefly unavailable while the settings take effect.
  6. Once the settings are applied, select Send test email. The test uses the saved Ghost settings and sends only to your DanubeData account's verified email address. Provider acceptance does not guarantee inbox delivery; check your spam folder as well.

The SMTP password is stored securely and cannot be viewed in the console. Leave the password field blank when updating settings to keep the saved password. If applying the settings fails, use Retry applying. Turning SMTP off prevents Ghost from sending password resets and invitations until it is enabled again.

This connection is for transactional email. Ghost newsletters use a separate Mailgun integration configured in Ghost Admin.

Parameters tab (n8n)

Beta. The Parameters tab is rolling out behind a feature flag. If you don't yet see Parameters on your n8n instance, it is not enabled for your account yet.

Change a curated set of n8n settings without leaving the console: timezone, log level, how long and how many executions are kept, which executions are saved, the Code node time limit and allowed built-in modules, data table storage, the public API, community nodes, and the metrics endpoint.

  1. Open your n8n instance and select Parameters.
  2. Change the settings you need. Your plan sets some limits: a setting that is locked shows the plan that unlocks it, and a capped setting shows the highest value your plan allows.
  3. Select Save and restart. n8n reads its settings once at startup, so the instance restarts and is briefly unavailable.

Prometheus metrics is on by default, and every n8n instance has it on until it is turned off. While it is on, n8n publishes Prometheus metrics at /metrics on your instance's public URL, without authentication, so anyone who knows the address can read them. If you do not use them, turn it off on the Parameters tab once it is available to you.

Backups & Snapshots tab

Manage snapshots for your instance:

  • Create Snapshot — Take a point-in-time snapshot of your instance
  • Snapshot list — All snapshots with status, creation date, and size
  • Restore — Restore the instance to a previous snapshot
  • Clone — Create a new, independent instance from a snapshot, leaving the current instance unchanged
  • Delete — Remove a snapshot
  • Automated snapshots — Toggle to enable or disable automatic snapshots

Custom domains

The domain management page provides full control over custom domains for your instance.

Default domain

Every instance has a default URL at {subdomain}.apps.danubedata.ro. This domain:

  • Is always available with no DNS configuration needed
  • Includes a managed TLS certificate
  • Serves as the CNAME target for custom domains

Adding a custom domain

  1. Click Add Domain
  2. Enter your domain name (e.g., app.example.com or example.com)
  3. Click Add

The domain is created with a Pending verification status.

Verifying domain ownership

After adding a domain, you must verify ownership via DNS:

  1. The dashboard shows a DNS TXT record to add:
    • Record name — _danubedata-verify.your-domain.com
    • Record value — A unique verification token
  2. Add this TXT record in your DNS provider's control panel
  3. Return to the dashboard and click the Verify button (refresh icon)

DNS propagation may take a few minutes. You can retry verification at any time if it fails.

Connecting your domain via CNAME

Create a CNAME record in your DNS provider, ideally together with the TXT record, before you click Verify:

Text
your-domain.com  CNAME  {subdomain}.apps.danubedata.ro

Once the CNAME is active, a TLS certificate is provisioned automatically. The TLS status will progress from Pending to Provisioning to Active.

If the CNAME is not published yet when the domain is verified, the domain shows Waiting for DNS. We look for the record every minute on the first day and hourly after that, and connect the domain as soon as we find it. You do not need to verify it again.

Domain statuses

Each domain shows two status badges:

Verification:

  • Pending — Waiting for DNS TXT record
  • Verifying — DNS check in progress
  • Verified — Domain ownership confirmed
  • Failed — Check DNS records and retry

TLS:

  • Pending — Waiting for certificate provisioning
  • Provisioning — Certificate being generated
  • Active — HTTPS is active
  • Failed — Certificate provisioning failed

Setting a primary domain

Click the star icon next to any verified domain to set it as the primary domain. The primary domain is used as the canonical URL for your application. Only verified domains can be set as primary.

Removing a domain

Click the trash icon next to any custom domain and confirm removal. The default apps.danubedata.ro domain cannot be removed.

Limits

Each instance supports up to 10 custom domains. Reserved domains matching *.danubedata.ro and *.danubedata.run cannot be added.

Upgrading your plan

You can upgrade your instance to a higher resource profile.

  1. Navigate to the instance detail page
  2. Click Edit Configuration from the Actions menu
  3. The current configuration is displayed at the top of the page
  4. Select a new resource profile from the available options
  5. Review the comparison sidebar showing changes to CPU, memory, storage, and cost
  6. Click Apply Changes

The sidebar highlights what will change — increases are shown in green, decreases in red.

Important notes:

  • Upgrading restarts the instance, causing brief downtime
  • Downgrading is not supported because persistent storage cannot be reduced
  • Only instances in Running state can be upgraded

Upgrading the app version

In addition to changing resources, you can upgrade the application version (for example, a newer release of WordPress, n8n, or Ghost) in place, without recreating the instance.

  1. Open the instance detail page
  2. If a newer version is available, a version upgrade option is shown
  3. Select the target version and confirm

What happens:

  • A pre-upgrade snapshot is taken automatically before the upgrade begins
  • The instance moves through the Upgrading state and returns to Running when the new version is healthy
  • If the upgrade fails to become healthy, recovery attempts to restore the previous version and pre-upgrade snapshot. The instance returns to Running only after recovery is verified; otherwise it needs attention.

Only the versions you can currently upgrade to are offered — some releases require an intermediate version or a manual migration first.

Automatic updates

In Overview → Version → Automatic updates, turn on Enabled, choose a daily window start and timezone, and select Save schedule. This setting applies only to that instance and defaults to off. Saving or disabling the schedule does not restart your app.

DanubeData checks for published, compatible releases in a one-hour window beginning at your selected local time. n8n and Ghost receive patch and minor updates within their current major version. WordPress receives maintenance updates within its current release series, such as 6.8.x; moving from 6.8 to 6.9 requires a manual upgrade. Releases requiring a manual migration or incompatible database changes also remain manual. A version must be reviewed and published in the managed-app catalog before it can be installed automatically.

The card shows the next window and the last result. No newer compatible release means no restart. Busy or stopped apps are skipped; work that cannot start within the window waits until the next day. Each local day has at most one scheduled check. A daylight-saving change that removes the selected time skips that day; a repeated time runs only once.

An update first takes a snapshot and then restarts the app. Both operations can cause downtime. Restoring the snapshot during recovery can lose changes made after it was taken. If an update fails, automatic updates pause and you receive a notification. Review the result and the app's health before enabling them again. A manual rollback also pauses automatic updates.

You can turn off the schedule while an update is queued. An update or recovery already running must finish. If DanubeData temporarily disables upgrades, you can still turn off your schedule.

This schedule controls DanubeData-managed app updates. WordPress's own core-update settings, plugins and themes are managed separately and can act independently. An app whose installed version cannot be verified needs a manual version reconciliation before automatic upgrades can run.

Rolling back

For 7 days after an upgrade, a Roll back option is available on the instance detail page. Rolling back restores the pre-upgrade snapshot, reverting both the application version and your data to their state before the upgrade. After the rollback window closes, the pre-upgrade snapshot may be cleaned up and rollback is no longer offered.

Only one upgrade or rollback can run at a time for a given instance.

Restarting an instance

To restart a running instance, open the Actions menu on the instance detail page and choose Restart. The instance moves through the Restarting state and returns to Running. A restart cycles the application without changing its version, plan, or data — a good first step if the app becomes unresponsive.

Account limits and billing

Instance limits

Each team has a configurable limit on the number of Managed App instances. When you reach your limit:

  • The create page shows an Account Limit Reached alert
  • You cannot create new instances until you delete an existing one or request a limit increase
  • Open Account limits in the sidebar (console.danubedata.ro/account-limits) to request an increase

Payment method

A card on your project is required to create instances. If you have not added one, a notice at the top of the create page says so. Click Set up billing in it (Add a card if your billing details are already saved) to add what is missing without leaving the page; the form keeps what you entered.

Budget limits

If your team has configured a monthly budget and a new instance would exceed it, the create page displays a Budget Limit Exceeded error with a link to manage your budget settings.

Billing details

  • Billing is hourly based on actual usage
  • Monthly invoices are generated on the 1st of each month
  • Billing starts at instance creation and stops at deletion
  • Plan upgrades take effect immediately with the new hourly rate

Next steps


Questions? Contact support at support@danubedata.ro