Cloudron

Starting today, we are making a Free Plan available. This plan will provide the complete Cloudron experience for 2 Apps and 5 users. This plan includes automatic updates and the Email solution. It's perfect suited for situations like: Newly ... [More] registered domains where one just wants to setup a web site and email Users who just want to run a single app like NodeBB, GitLab or Rocket.Chat. Please note that this does not affect current paid users. The pricing page looks like this now: What is Cloudron? For those unaware, Cloudron is a platform for running self-hosted and on-prem web apps. The idea is to deploy apps on your server via our App Store to get a SaaS style hassle-free continuous deployment experience for self-hosted apps. Cloudron has two pieces of technology. First, the platform that runs on the server which can run apps and update apps (just like what Android does for phones). Second, the Cloudron App Store which is an app distribution mechanism (similar to Google Play). Brief history of our pricing When we launched Cloudron about a year ago, we provided a free plan that allowed installing any number of apps. Automatic app and platform updates were only available if you moved to a paid plan. Users on free plan could compile the app from source and update it themselves (all our app packages are opensource) or pay us for the convenience. While this was great for onboarding users, we saw that users continued running Cloudron on a free plan without updating anything. To increase awareness, we tried sending out 'Updates pending' emails but these had little effect. Having outdated Cloudron and app installations is a big security risk and somehow we felt indirectly responsible for this situation. It also breaks our SaaS continous delivery model which is the UX we want to deliver. Indeed, over time, we have periodically gotten support requests for help updating outdated/broken servers - a problem we set out to solve with Cloudron in the first place! To fix the issue temporarily, we removed the free plan and instead offered a 15-day trial. This approach served us much better but a common request is to extend the trial period. A True Free Plan Which brings us to today. We have been working on a free plan that will let users use all the features of the Cloudron and get the entire Cloudron experience - just install apps and forget about keeping them up-to-date. With the free plan we are announcing today, users can start using Cloudron for free with a couple of apps. As the team grows and when they require more apps, they can switch to a paid plan. Note that it is still worthwhile to upgrade to a paid plan with less than 2 apps if you require priority support. Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. Comments? Comments/Suggestions/Feedback? Discuss in our Forum or email us. [Less]

We are happy to announce the release of Cloudron 2.3! For those unaware, Cloudron is a platform for running self-hosted and on-prem web apps. The idea is to deploy apps on your server via our App Store to get a SaaS style hassle-free continuous ... [More] deployment experience for self-hosted apps. Snapshot & Clone Apps The new Backup UI makes it easy to create on-demand backup of a single app. Say you want to test a wordpress plugin and are worried about how it might affect your installation. With this feature, you can create a point-in-time snapshot of wordpress before testing out the plugin. To create a backup, first click the backups button in the app grid: Then click on the Create Backup button: The App backup can be used to 'clone' an existing app as-is into another domain. For example, you can work on a Wordpress site installed at 'staging.domain.com'. When ready, simply create a backup and clone the application to 'prod.domain.com'. name.com name.com is now a supported DNS provider. If your domain is registered with name.com, first Generate the API keys and choose name.com as the DNS provider. With the credentials in place, Cloudron will automatically add and remove DNS records for the domain. In addition, when using Cloudron Email, it will also automatically setup the MX, DMARC, DKIM records! Advanced DNS settings The DNS zone name and Certificate provider can be set using the advanced DNS configuration. The Let's Encrypt Staging certificate provider is hosted by the Let's Encrypt project and is useful for testing out apps without hitting Let's Encrypt rate limits. The Self-Signed option generates a self-signed certificate that can be used for testing Cloudron in environments where the Cloudron cannot have inbound HTTP(s) connections (required for Let's Encrypt). A custom certificate can also be uploaded in the Domain UI. Persistent Addon Configuration Previous versions of Cloudron used to reset the database credentials (MySQL, PostgreSQL) of apps across updates, restarts. While this can seen as a security feature (automatic key rotation), this unfortunately makes it awkward to install apps that have a setup screen that ask for database credentials. This is very common when installing apps via the LAMP app. For this reason, the database credentials are now preserved across app updates and restarts. New Email UI The Email UI has been reworked to categorize various options into tabs. Email Masquerading By default, Cloudron has a security policy of only allowing users and apps to send and receive emails using the mailbox names allocated to them. This feature can be turned off to allow masquerading. This enables apps to send emails using the mailbox name of any user (for example, a CRM app or a help desk app). Note that only the mailbox name can be arbitrary, the domain name still has to match the Cloudron domain. Improved Sieve support Cloudron Email supports server side filters using the Manage Sieve protocol. Prior to this release, this service was exposed using TLS. For increased compatibility, we have changed the service to use STARTTLS instead. Rainloop, Roundcube and SOGo apps have already been updated to handle the change. The Thunderbird Sieve addon should also now work with this change. New SOGo We have also pushed a completely new version of SOGo that supports Sieve and multiple domains. Important: The old SOGo with the package id nu.sogo.cloudronapp is deprecated. This new version has the package id nu.sogo.cloudronapp2. Click on the information icon 'i' of the app and check the package version link to check the package id. Currently, there is no automatic way to migrate from the old package to the new package. We tried our best to not create a new package but the authentication mechanism of the new package has changed making automatic migration tricky. Please contact us if you need help migrating. App Mailbox name For apps that can send and/or receive email, Cloudron automatically creates a mailbox with the name .app. In this release, we have made it possible to change the name of this mailbox. Click on Configure in the app grid and edit the mailbox name in the Advanced tab. The app will get automatically re-configured to send emails using the new name. Dashboard Visibility The Dashboard of a Cloudron user displays the apps that the user can access. For apps that use Cloudron Single Sign-on, the dashboard only displays an app if the user has access to it. For apps configured to not use the Cloudron Single Sign-on (for example, some public app like a Forum or Chat), the apps are displayed on the dashboard of all users. In this release, we have added a Dashboard visibility setting using which admins can control if an app appears in the user's app grid. Note that this option appears only for apps that are configured to not use Cloudron authentication. Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. To update an existing installation, simply click on the 'Update now' button under Settings. Comments? Comments/Suggestions/Feedback? Discuss in our Forum or email us. [Less]

We are happy to announce the release of Cloudron 2.2! For those unaware, Cloudron is a platform for running self-hosted and on-prem web apps. The idea is to deploy apps on your server via our App Store to get a SaaS style hassle-free continuous ... [More] deployment experience for self-hosted apps. 2FA Users can enable 2FA authentication from the profile menu in the dashboard: Clicking on the Enable 2FA button will display a QR Code which can be scanned using a TOTP app such as Google Authenticator (Android, iOS), FreeOTP authenticator (Android, iOS Gandi LiveDNS LiveDNS is Gandi.net's DNS platform, a completely new service that offers its own API and its own nameservers. If your domain is registered with Gandi, you can use Cloudron's new Gandi DNS backend to manage the DNS. When apps are installed and removed, Cloudron will automatically add and remove DNS records. When using Cloudron Email, it will also automatically setup the MX, DMARC, DKIM records! To get started: Ensure that your domain is using LiveDNS. Go the DNS Records page in Gandi to verify that you are using LiveDNS. Old domains might see a Switch to LiveDNS banner. If you see this, click on Gandi's DNS Records button and wait for 2-3 hours for Gandi to migrate the domain. Next, create an LiveDNS API key from the security section In the Cloudron dashboard, choose Gandi LiveDNS from the drop down and provide the API key. GoDaddy GoDaddy is the world's largest registrar. If your domain is registered with GoDaddy, you can use Cloudron's new GoDaddy DNS backend to manage the DNS. When apps are installed and removed, Cloudron will automatically add and remove DNS records. When using Cloudron Email, it will also automatically setup the MX, DMARC, DKIM records! To get started: Create a GoDaddy API Key at their developer portal. When creating a new key select production environment. In the Cloudron dashboard, choose GoDaddy from the drop down and provide the key and secret. Other fixes Fix zone detection logic on Route53 accounts with more than 100 zones Warn user when disabling Cloudron Email Cleanup scope management in REST APIs Enhance user creation API to take a password Relax restriction on mailbox names now that it is decoupled from user management Fix issue where mail container incorrectly advertised CRAM-MD5 support Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. To update an existing installation, simply click on the 'Update now' button under Settings. Comments? Comments/Suggestions/Feedback? Discuss in our Forum or email us. [Less]

We are happy to announce the release of Cloudron 2.1! For those unaware, Cloudron is a platform for running self-hosted and on-prem web apps. The idea is to deploy apps on your server via an App Store to get a SaaS style hassle-free continuous ... [More] deployment experience for self-hosted apps. Improved mailbox management In Cloudron 1.x, users/groups and mailboxes/lists were tightly coupled. Each user had a mailbox of the same name and each group was also a mailing list. This tight coupling meant that if you just wanted to a create new mailbox, you had to create a new user and setup a new password for that user. In Cloudron 2.1, we have decoupled the mailbox management and user management. Mailboxes can be added and removed independently of user from the Email view. All Cloudron subscription plans include unlimited mailboxes and aliases. The way it works is that you can create a mailbox in a domain and then assign an existing user as the mailbox owner. The mailbox owner can access the mailbox using [email protected] as the username and the Cloudron password. Each mailbox can have one or more aliases. Aliases can be used by adding an identity in a mail client like Rainloop, Roundcube & Thunderbird. A mailing list can be created by providing a name and assigning one or more existing mailboxes. Once created, you can email [email protected] and a copy of the email will be sent to all the list members. Docker 18.03 Docker has been updated to 18.03.0-ce. This Docker release bring numerous security and stability fixes. You can read the full Docker changelog here. Support for private apps Cloudron is internally architected as a PaaS. Application requirements and setup is described in a Dockerfile. An accompanying CloudronManifest specifies addon requirements like databases, local storage, authentication etc. The current Cloudron app development flow uses the public Docker hub to build and deploy images. This means that any packaged app code is essentially publicly viewable. A popular request has been to develop and deploy private (closed source) apps. In 2.1, we have added initial support to build and deploy apps using a private docker registry like quay, Amazon ECR. See the packaging guide for more information on private builds. Other fixes Make S3 backend work reliably with slow internet connections mail: fix issue where hosts with valid SPF for a Cloudron domain are unable to send mail to Cloudron mail: fix crash when bounce emails have a null sender Add CSP header for dashboard Fix bug where browsers used a cached version of the Cloudron dashboard after an update Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. To update an existing installation, simply click on the 'Update now' button under Settings. Comments? Comments/Suggestions/Feedback? Discuss in our Forum or email us. [Less]

For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. Cloudron works best on public VPS providers like Digital Ocean, Vultr, Linode. This is simply ... [More] because those servers come with a public IP out of the box and the default firewall allows incoming traffic from all TCP ports to the server. A little known secret is that Cloudron works just fine on a Home Server! It just needs a little technical know how of your home network. In this post, we will see how to install Cloudron on a home server. The setup described here is for a home server installation that can be accessed from outside home as well. Prerequisites Cloudron requires the following: A public IPv4 address. This IP address does not need to be static. Cloudron has a feature where it will continually keep your DNS updated with a dynamic IP address. You can visit this site to view your current public IP address. Forward port 80 and port 443 from your router to the Home Server IP. For this, you have to login to your router and setup port forwarding in the firewall. See this site for router specific instructions on how to setup port forwarding. NAT loopback support in your router. Cloudron apps are accessed using domain names and the DNS entries point to the public IP of your home network. When apps are accessed with the DNS name from inside your home, the router needs to be capable of routing the public IP back ('hairpinning') to your home server. Most modern routers support this. Installation Create a fresh server (VM or baremetal) with Ubuntu Xenial (16.04 x64) and run these commands: wget https://cloudron.io/cloudron-setup chmod +x ./cloudron-setup ./cloudron-setup --provider generic Domain setup Once installation is complete, navigate to https://IP. If you meet the pre-requisites above, you should be able to use your current public IP address. If you are unable to access with the public IP address, now is a good time to investigate what is failing. Provide a domain name to complete the installation: We recommend choosing one of the automated DNS providers like Cloudflare, Digital Ocean and Route 53. If you use the wildcard or manual DNS with a dynamic IP address, you have to setup some other way to keep the DNS in sync with your public IP. Admin setup Once DNS is setup, Cloudron will redirect to https://my.domain.com. The browser address bar will show a green lock to indicate that the connection to your Cloudron is now secure (It does this by automatically getting a certificate via Let's Encrypt). Appstore setup You are now ready to start installing apps! When you click on the App Store link in the UI, you will be prompted to create a cloudron.io account. This account is used to manage your subscription & billing. Enable Dynamic DNS If you have a setup where you have a dynamic public IP, the Cloudron has to be configured to keep the DNS updated. For this, SSH into your server and run the following commands: mysql -uroot -ppassword -e "INSERT box.settings (name, value) VALUES('dynamic_dns', 'enabled')" systemctl restart box Other notes Remember to port forward TCP ports from the router to the server when using non-HTTP(S) ports. For example, you might have to forward SSH ports for git to work when using Gogs, Gitea & GitLab. Cloudron requires port 80 (HTTP) to be forwarded at all times for the Let's Encrypt integration to work. Cloudron itself serves web pages only on 443 (HTTPS). Cloudron requires x86 and does not work on Raspberry Pi. Comments? Comments/Suggestions/Feedback? Discuss in our forum. [Less]

For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. Cloudron works best on public VPS providers like Digital Ocean, Vultr, Linode. This is simply ... [More] because those servers come with a public IP out of the box and the default firewall allows incoming traffic from all TCP ports to the server. A little known secret is that Cloudron works just fine on a Home Server! It just needs a little technical know how of your home network. In this post, we will see how to install Cloudron on a home server. The setup described here is for a home server installation that can be accessed from outside home as well. Prerequisites Cloudron requires the following: A public IPv4 address. This IP address does not need to be static. Cloudron has a feature where it will continually keep your DNS updated with a dynamic IP address. You can visit this site to view your current public IP address. Forward port 443 from your router to the Home Server IP. For this, you have to login to your router and setup port forwarding in the firewall. See this site for router specific instructions on how to setup port forwarding. Cloudron supports a variety of DNS providers like Cloudflare, Route53, DigitalOcean, Namecheap and so on. If you decide not to use of those providers and instead use Wildcard or Manual DNS, then you must also forward port 80 from your router to the server. This is required for Let's Encrypt to work. NAT loopback support in your router. Cloudron apps are accessed using domain names and the DNS entries point to the public IP of your home network. When apps are accessed with the DNS name from inside your home, the router needs to be capable of routing the public IP back ('hairpinning') to your home server. Most modern routers support this. Installation Create a fresh server (VM or baremetal) with Ubuntu Bionic (18.04 x64) and run these commands: wget https://cloudron.io/cloudron-setup chmod +x ./cloudron-setup ./cloudron-setup --provider generic Domain setup Once installation is complete, navigate to https://IP. If you meet the pre-requisites above, you should be able to use your current public IP address. If you are unable to access with the public IP address, now is a good time to investigate what is failing. Provide a domain name to complete the installation: We recommend choosing one of the automated DNS providers like Cloudflare, Digital Ocean and Route 53. Admin setup Once DNS is setup, Cloudron will redirect to https://my.domain.com. The browser address bar will show a green lock to indicate that the connection to your Cloudron is now secure (It does this by automatically getting a certificate via Let's Encrypt). Appstore setup You are now ready to start installing apps! When you click on the App Store link in the UI, you will be prompted to create a cloudron.io account. This account is used to manage your subscription & billing. Enable Dynamic DNS If you have a setup where you have a dynamic public IP, the Cloudron has to be configured to keep the DNS updated. For this, go to Domains view and enable Dynamic DNS. Note: If you use the wildcard or manual DNS with a dynamic IP address, you have to setup some mechanism external to Cloudron to keep the DNS in sync with your public IP. Other notes Cloudron requires port 443 (HTTPS). Cloudron serves web pages and requests only on 443 (HTTPS). Cloudron requires x86 and does not work on Raspberry Pi. Remember to port forward TCP ports from the router to the server when using non-HTTP(S) ports. For example, you might have to forward SSH ports for git to work when using Gogs, Gitea & GitLab. Comments? Comments/Suggestions/Feedback? Discuss in our forum. [Less]

For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. Over the last year, the Cloudron team has been providing support over various channels - our chat ... [More] , website live chat, the git issue trackers, support email, phone to name a few. We are now consolidating our official support channels to make it more SEO friendly and improve discoverability of common problems. Help Forum We are happy to announce that the Help Forum is now ready. Using a forum will help SEO, discover-ability and easily help us track issues with threads. The Cloudron Forum is proudly powered by NodeBB and is (of course) hosted on Cloudron :-) You can login to the forum via Twitter, GitHub or create a new account with email. App wish list The help forum has an App Wishlist category. Please upvote for your favorite apps requests using the "^" button in the bottom right of the topic. Feel free to add new apps to the wish list as well. Knowledge base We have built extensive documentation for Cloudron. Simply use the Search bar on the top right to easily locate an article. The developer docs are located at a separate URL and has all the necessary information on building and maintaining custom packages. Each app on Cloudron App Store also has a separate documentation page - for example, see Wordpress, GitLab, NextCloud, LAMP and Ghost. Comments? Comments/Suggestions/Feedback? Please email us. [Less]

We are happy to announce the release of Cloudron 2.0! For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. The Big Picture Cloudron 2.0 is a big ... [More] exciting release for us and a tremendous amount of work has gone into making this happen. This release also marks a change in who Cloudron is targeting. Two years back, we started Cloudron to scratch our own itch. After Google Reader shutdown, we started looking for solutions that will let us self-host applications easily. We wanted the convenience of SaaS for apps deployed on our own servers. We wanted automated deployment, seamless updates, encrypted backups, timely security patches - all of which are big barriers to self-hosting. Our first iteration of Cloudron was designed primarily to be a personal cloud. Cloudron 1.x was installed on a domain name like girish.in and apps are then installed from the Cloudron App Store into subdomains like reader.girish.in, git.girish.in and so on. With the personal cloud angle, our target audience was privacy conscious individuals and companies. We took an appliance centric and consumer oriented approach for our product like Android/iOS that hides all complexities of app deployment - we didn't even have a log viewer!. As Cloudron gained more users, we received requests to build more tooling around managing running apps - web terminal, log viewer, advanced app configuration etc. What we have learnt is that Cloudron is solving the bigger problem of zero-effort application delivery, deployment and maintanence. Managed service providers, system administrators, IT teams and even some SaaS products are using Cloudron as the backend to deploy apps on the behalf of their own customers and users. With that in mind, the first big feature we are pushing out today is support for multiple domains. This feature can be used to use a single Cloudron to deploy and manage apps for their customers spanning multiple domains. Multiple domains support Domains can be added in the Domains view. Each domain has it's backend configuration. So, you can have one domain on Cloudflare, another on Digital Ocean DNS and so on. App installation When installing an app, simply select the domain in which it should be installed in the domain dropdown. Cloudron will automatically setup the DNS and install Let's Encrypt certificates when installing the app. Multi-domain email server Cloudron's built-in email server now supports hosting email on multiple domains. The email server can be enabled on a per-domain basis in the Email view. When email is enabled for a domain, Cloudron will automatically setup all the DNS records required for hosting email on that domain. A mail relay like Postmark, Mailgun, Amazon SES can be setup for outbound mails on a per-domain basis. The DNS status section in the Email view will have green check marks to indicate your domain is ready to use. Mailboxes Mailboxes can be assigned to users and groups on a per-domain level. To edit the mailboxes of a user, simply edit the user in the Users view. Email aliases can also be set on a per-domain basis. Webmail updates Rainloop and Roundcube have been updated to support multi-domain email. Login to the apps using the email ids to access the different mailboxes. Revamped log viewer The activity got a facelift and it's must easier to quickly browse through all the activity on the Cloudron. Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. To update an existing installation, simply click on the 'Update now' button on your dashboard. Comments? Comments/Suggestions/Feedback? Please email us. [Less]

We are happy to announce the release of Cloudron 2.0! For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. The Big Picture Cloudron 2.0 is a big ... [More] exciting release for us and a tremendous amount of work has gone into making this happen. This release also marks a change in who Cloudron is targeting. Two years back, we started Cloudron to scratch our own itch. After Google Reader shutdown, we started looking for solutions that will let us self-host applications easily. We wanted the convenience of SaaS for apps deployed on our own servers. We wanted automated deployment, seamless updates, encrypted backups, timely security patches - all of which are big barriers to self-hosting. Our first iteration of Cloudron was designed primarily to be a personal cloud. Cloudron 1.x was installed on a domain name like girish.in and apps are then installed from the Cloudron App Store into subdomains like reader.girish.in, git.girish.in and so on. With the personal cloud angle, our target audience was privacy conscious individuals and companies. We took an appliance centric and consumer oriented approach for our product like Android/iOS that hides all complexities of app deployment - we didn't even have a log viewer!. As Cloudron gained more users, we received requests to build more tooling around managing running apps - web terminal, log viewer, advanced app configuration etc. What we have learnt is that Cloudron is solving the bigger problem of zero-effort application delivery, deployment and maintanence. Managed service providers, system administrators, IT teams and even some SaaS products are using Cloudron as the backend to deploy apps on the behalf of their own customers and users. With that in mind, the first big feature we are pushing out today is support for multiple domains. This feature can be used to use a single Cloudron to deploy and manage apps for their customers spanning multiple domains. Multiple domains support Domains can be added in the Domains view. Each domain has it's backend configuration. So, you can have one domain on Cloudflare, another on Digital Ocean DNS and so on. App installation When installing an app, simply select the domain in which it should be installed in the domain dropdown. Cloudron will automatically setup the DNS and install Let's Encrypt certificates when installing the app. Multi-domain email server Cloudron's built-in email server now supports hosting email on multiple domains. The email server can be enabled on a per-domain basis in the Email view. When email is enabled for a domain, Cloudron will automatically setup all the DNS records required for hosting email on that domain. A mail relay like Postmark, Mailgun, Amazon SES can be setup for outbound mails on a per-domain basis. The DNS status section in the Email view will have green check marks to indicate your domain is ready to use. Mailboxes Mailboxes can be assigned to users and groups on a per-domain level. To edit the mailboxes of a user, simply edit the user in the Users view. Email aliases can also be set on a per-domain basis. Webmail updates Rainloop and Roundcube have been updated to support multi-domain email. Login to the apps using the email ids to access the different mailboxes. Revamped log viewer The activity got a facelift and it's must easier to quickly browse through all the activity on the Cloudron. Comments/Suggestions/Feedback? Email us. [Less]

We are happy to announce the release of Cloudron 2.0! For those unaware, Cloudron is a platform that makes it easy to run web apps on your server and keep them up-to-date. Think SaaS for self-hosted apps. The Big Picture Cloudron 2.0 is a big ... [More] exciting release for us and a tremendous amount of work has gone into making this happen. This release also marks a change in who Cloudron is targeting. Two years back, we started Cloudron to scratch our own itch. After Google Reader shutdown, we started looking for solutions that will let us self-host applications easily. We wanted the convenience of SaaS for apps deployed on our own servers. We wanted automated deployment, seamless updates, encrypted backups, timely security patches - all of which are big barriers to self-hosting. Our first iteration of Cloudron was designed primarily to be a personal cloud. Cloudron 1.x was installed on a domain name like girish.in and apps are then installed from the Cloudron App Store into subdomains like reader.girish.in, git.girish.in and so on. With the personal cloud angle, our target audience was privacy conscious individuals and companies. We took an appliance centric and consumer oriented approach for our product like Android/iOS that hides all complexities of app deployment - we didn't even have a log viewer!. As Cloudron gained more users, we received requests to build more tooling around managing running apps - web terminal, log viewer, advanced app configuration etc. What we have learnt is that Cloudron is solving the bigger problem of zero-effort application delivery, deployment and maintenance. Managed service providers, system administrators, IT teams and even some SaaS products are using Cloudron as the backend to deploy apps on the behalf of their own customers and users. With that in mind, the first big feature we are pushing out today is support for multiple domains. This feature can be used to use a single Cloudron to deploy and manage apps for their customers spanning multiple domains. Multiple domains support Domains can be added in the Domains view. Each domain has it's backend configuration. So, you can have one domain on Cloudflare, another on Digital Ocean DNS and so on. App installation When installing an app, simply select the domain in which it should be installed in the domain dropdown. Cloudron will automatically setup the DNS and install Let's Encrypt certificates when installing the app. Multi-domain email server Cloudron's built-in email server now supports hosting email on multiple domains. The email server can be enabled on a per-domain basis in the Email view. When email is enabled for a domain, Cloudron will automatically setup all the DNS records required for hosting email on that domain. A mail relay like Postmark, Mailgun, Amazon SES can be setup for outbound mails on a per-domain basis. The DNS status section in the Email view will have green check marks to indicate your domain is ready to use. Mailboxes Mailboxes can be assigned to users and groups on a per-domain level. To edit the mailboxes of a user, simply edit the user in the Users view. Email aliases can also be set on a per-domain basis. Webmail updates Rainloop and Roundcube have been updated to support multi-domain email. Login to the apps using the email ids to access the different mailboxes. Revamped log viewer The activity got a facelift and it's must easier to quickly browse through all the activity on the Cloudron. Install or update Cloudron New to Cloudron? Get started for free by running with 3 simple commands on your server. To update an existing installation, simply click on the 'Update now' button on your dashboard. Comments? Comments/Suggestions/Feedback? Please email us. [Less]