cloudron.io

Yes to both. Cloudron is built on an immutable infrastructure design that lets you move an entire server — including all its apps — to another cloud provider, and it supports encrypted backups stored on external object storage such as Amazon S3, Google Cloud Storage, and DigitalOcean Spaces. The two features work together: backups give you a recovery point, and portability lets you restore that point onto different hardware or a different provider.

How migration works

Cloudron packages each app as an immutable unit rather than a hand-configured server you gradually modify. Because the app definition doesn't depend on the specific machine underneath, the same apps can be brought up on a different server without rebuilding them from scratch.

In practice this means:

• You can move your entire server along with all its apps to another cloud provider.
• The move is described as taking "no time" relative to a manual rebuild, because you aren't reinstalling and reconfiguring each app by hand.
• The portability comes from the infrastructure design, not from a one-off export tool — it's a property of how apps are packaged.

This matters most when you want to change hosting providers, consolidate servers, or recover onto fresh hardware after a failure. If you were running apps installed manually, the equivalent task would mean reinstalling every app, recreating databases, and redoing configuration — the exact work Cloudron's design is meant to remove.

How backups work

Cloudron stores encrypted backups on external storage. The page names three supported destinations:

Two things are worth noting from this:

1. Backups go off the server. Because the target is external object storage, a backup survives the loss of the server itself — which is what makes it useful for disaster recovery rather than just local snapshots.
2. Backups are encrypted. The page states backups are stored encrypted, so the storage provider holds encrypted data rather than plaintext.

The page does not specify backup frequency, retention, or the exact encryption scheme, so treat those as things to confirm in the documentation before relying on a specific recovery window.

The disaster-recovery picture

Cloudron pairs backups with two other safeguards mentioned on the page:

• A built-in firewall.
• Auditable events, so activity on the server can be reviewed.

Together with external encrypted backups, this is the "disaster-proof" framing on the page: the firewall and audit trail reduce the chance and impact of an incident, and the off-site backup gives you something to restore from if the server is lost.

What to check before you rely on it

• Confirm your storage provider is supported. The page lists S3, Google Cloud Storage, and DigitalOcean Spaces; if you use something else, verify compatibility in the docs.
• Decide your migration trigger. Portability is most valuable when planned — moving providers, resizing, or recovering. Knowing in advance where your backups live and how to restore them turns a potential outage into a routine task.
• Read the docs for specifics. Backup scheduling, retention, restore procedure, and encryption details aren't on the landing page; the Documentation and Forum links are the place to confirm them.

If your goal is simply to understand what Cloudron does overall, the short version is: it runs apps on your own server, keeps them updated, and manages users centrally — with portability and off-site encrypted backups as part of the same design.

Cloudron handles updates for both the apps and the underlying server through its App Store, publishing new app and server releases within days and security fixes within 24 hours. If you run apps on your own server and don't want to track upstream releases, patch Dockerfiles, or manually provision databases, this is the mechanism that replaces that work. The trade-off: you're relying on Cloudron's packaging pipeline rather than installing apps directly from their original projects.

The update pipeline

Cloudron's stated model is that it packages apps and ships them through the Cloudron App Store, the same channel you install from. Two cadences apply:

• Regular releases — published within days of upstream.
• Security fixes — published within 24 hours, for both apps and the server.

Because updates arrive through the App Store rather than through your own build process, you don't rebuild containers or re-provision databases when a new version lands. That is the core of the "SaaS-style" update experience Cloudron describes for a private cloud.

What this replaces

The site frames the alternative directly: self-hosting apps is "time consuming and error-prone," and keeping a system up to date and secure is described as a full-time job. Cloudron's pitch is that you focus on using the apps while it handles system administration. Concretely, the tasks it absorbs are:

• Tracking upstream releases for each app you run
• Writing and maintaining Dockerfiles
• Manually provisioning databases
• Applying server-level patches

Security beyond patching

Fast patching is only part of the picture. Cloudron also includes:

• A built-in firewall on the server.
• Audit logging — the site states all events can be audited.
• Encrypted backups to external storage, with Amazon S3, Google Cloud Storage, and Digital Ocean Spaces named as supported targets.

The backup piece matters for the same reason updates do: if an update or a compromise goes wrong, you need a recoverable state. Storing encrypted backups off-server is the documented path.

Portability as a safety net

Cloudron describes its infrastructure design as immutable, which it says allows easy migration of apps across servers — including moving an entire server and all its apps to another cloud provider. For update and security purposes, this is a hedge: you are not locked to one host if you want to change providers or recover elsewhere.

What you still manage

Cloudron automates app and server maintenance, but it does not remove you from the loop entirely. Based on what the site describes, you remain responsible for:

• User access — you invite users and configure which apps they can reach; users then open apps from a dashboard.
• Mail configuration choices — DKIM, SPF, and DMARC setup is automated for reliable delivery, but the built-in mail server exposes options like catch-all addresses, subaddresses and tags, per-domain mail relays, cross-domain aliases, delivery logs, and custom spam filtering rules.
• Backup destination — you choose and connect the external storage.

How to evaluate it for your case

A practical first step is the Demo Cloudron, which the site lists with the username cloudron and password cloudron. It lets you see the dashboard, app installation flow, and user management before committing to a server. Pricing details are not specified in the available page content, so check the Pricing page directly for current terms.

Cloudron is a self-hosting platform that runs web apps on your own server and keeps them installed, updated, and secure. It fits you if you want the convenience of SaaS-style app management — one-click installs, automatic updates, central user accounts — but want the apps and data to live on infrastructure you control. It is not a hosting provider; you bring a server (or a cloud VM), and Cloudron manages the app layer on top of it.

What problem it solves

The site frames the core pain directly: self-hosting apps is "time consuming and error-prone," and keeping a system updated and secure is described as a full-time job. Cloudron's stated goal is to let you focus on using apps rather than on system administration.

Concretely, it takes over the tasks that normally make self-hosting tedious:

• Installation — deploy production-ready apps from the Cloudron App Store without writing Dockerfiles or manually provisioning databases.
• Updates — the project says it publishes the latest releases within days and security fixes within 24 hours, for both apps and the server, delivered through the App Store.
• User management — invite users and configure which apps each one can access; users open their apps from a dashboard.
• Mail — a built-in mail server with calendar and contacts sharing, a self-training spam filter, and automated DKIM, SPF, and DMARC setup for deliverability.
• Backups and security — a built-in firewall, auditable events, and encrypted backups to external storage such as Amazon S3, Google Cloud Storage, and Digital Ocean Spaces.

How it works in practice

The model is an immutable infrastructure design. Because apps are packaged and managed as standardized units rather than hand-configured on the host, the platform claims you can migrate apps — or an entire server with all its apps — to another cloud provider quickly. That portability is the practical payoff of not letting apps drift into bespoke server configurations.

The mail server is worth calling out because it is often the hardest part of self-hosting to get right. Cloudron's version supports catch-all addresses, subaddresses and tags, per-domain mail relays, cross-domain aliases, delivery logs, and custom spam filtering rules.

Who it is for

The site states that thousands of organizations use Cloudron, and the project is open source with published documentation, a forum, and a pricing page.

What to check before committing

• Server requirements and supported providers — you supply the server, so confirm your target environment is supported in the documentation.
• Which apps you actually need — availability is determined by the Cloudron App Store catalog; check it against your requirements rather than assuming any given app is packaged.
• Pricing and plan limits — the site links to a Pricing page, but the supplied material does not state prices or what each tier includes, so review that page directly.
• Mail deliverability — automated DKIM/SPF/DMARC helps, but sending mail from your own server still depends on your domain and IP reputation.

If you want to see the interface before installing anything, the site offers a demo (username cloudron, password cloudron) alongside its documentation and forum.

Cloudron centralizes user management in a single dashboard: you invite users, assign which apps each person can access, and they log in to one place to open everything they're allowed to use. This fits teams and organizations that run multiple self-hosted apps on one server and don't want to manage separate accounts per app.

Inviting users and setting access

User management happens from the Cloudron dashboard rather than inside each app:

• Invite users — add people to your Cloudron instance by invitation.
• Configure app access — decide which apps each user can reach. Access control is set up centrally, so permissions live in one place instead of being scattered across individual app settings.
• Users see their own apps — once invited, a user opens the dashboard and finds the apps they have access to, then launches them directly from there.

The practical effect: onboarding a new team member means one invitation and a set of app permissions, not a separate account on every service.

The central dashboard

The dashboard is the single entry point for everyone on the instance:

This is the "all in one place" model Cloudron describes: users don't need to remember a different URL and login for each app, and admins don't need to visit each app to adjust who can use it.

Why this matters for organizations

If you're running a private cloud for a group, the usual pain is account sprawl — every app has its own user list, and keeping them consistent is manual work. Cloudron's central user management addresses that directly:

• One place to grant or revoke access across apps.
• One dashboard for users to reach their tools.
• Consistent onboarding — invite once, assign apps, done.

This is most useful when several people share a server and you want access decisions to be auditable and quick to change, rather than buried in per-app admin panels.

Where to verify the details

The exact invitation flow, permission options, and dashboard layout can change between versions. To confirm current behavior for your setup, check the official documentation and forum, and you can try the flow yourself on the Demo Cloudron (the site lists demo credentials: username cloudron, password cloudron). Pricing for the plans that include these features is listed on the Cloudron pricing page.

Cloudron's built-in mail server is a full mail stack that runs on your own server, not just a forwarding layer. According to Cloudron's own description, it is a "modern solution with calendar, contacts sharing and self-training spam filter," and it handles the DNS authentication records (DKIM, SPF, DMARC) automatically so that mail you send is accepted by major providers. It is worth considering if you want mail, calendars, and contacts to live alongside your self-hosted apps under one user management system — and less suitable if you only need outbound transactional email or want to keep mail on a separate provider.

Core mail server capabilities

Cloudron describes the mail server as feature-packed, with these documented capabilities:

• Catch-all addresses — accept mail sent to any address at a domain, not only defined mailboxes.
• Subaddresses and tags — plus-addressing style variants so users can sort or filter incoming mail.
• Per-domain mail relays — route outgoing mail for a specific domain through a chosen relay.
• Cross-domain email aliases — an alias on one domain can point to a mailbox on another.
• Delivery logs — visibility into what happened to messages.
• Custom spam filtering rules — beyond the default self-training filter, you can define your own rules.

Automated DNS setup for deliverability

The page states that DKIM, SPF, and DMARC setup is "completely automated" for reliable mail delivery. In practice this means Cloudron generates the required DNS records for your domain and you publish them at your DNS provider. This is the part most self-hosted mail setups get wrong, and it is the main reason Cloudron frames its mail server as a "modern solution" rather than a raw MTA.

Calendar and contacts sharing

Calendar and contacts sharing is listed as part of the mail server feature set, so users on the same Cloudron instance can share calendars and address books rather than each running an isolated client-side store.

How it fits with the rest of Cloudron

The mail server is not a separate product you bolt on. It sits under the same central user management described on the page: you invite users, configure which apps they can access, and they use the dashboard to open their apps. Mail, calendar, and contacts are part of that same account model.

Two related properties from the page matter for mail specifically:

• Backups — encrypted backups can be stored on external storage such as Amazon S3, Google Cloud Storage, and Digital Ocean Spaces, which covers mail data as part of the server.
• Portability — Cloudron's immutable infrastructure design is described as allowing you to move your entire server, with all its apps, to another cloud provider. That matters for mail because moving a mail server normally means re-issuing DNS and risking deliverability.

What to check before committing

• DNS control — automated DKIM/SPF/DMARC setup still requires you to be able to publish records for the domain. If you do not control DNS, this will not work.
• Relay requirements — some hosting providers block outbound port 25. The per-domain mail relay feature is the documented way to route around that, but confirm your provider's policy first.
• Pricing and plan limits — the page links to a Pricing page but does not state prices or which mail features are gated behind which plan. Check the Pricing page directly rather than assuming the mail server is included at every tier.
• Demo access — the page offers a demo with username cloudron and password cloudron, which is the fastest way to inspect the mail, calendar, and contacts interfaces before installing.

If your goal is a single self-hosted system where mail, calendars, contacts, and apps share one user directory and one backup path, Cloudron's mail server covers that. If you need only SMTP relay for app notifications, or you want mail hosted by a third party, the built-in server is more than you need.