Frequently Asked Questions
No. There are no long-term contracts. ISP services are charged at their anniversary and can be cancelled at renewal. There are no charges for transferring domains away or for cancellations.
Yes. We can configure a centralised identity service that provides single sign-on across your applications — Odoo, Nextcloud, email, instant messaging and others. User accounts are managed in one place, so when someone joins or leaves, access is updated everywhere. See our integration page for details.
Yes. When your VoIP telephone system is integrated with Odoo, you can dial contacts directly from their record. Incoming calls show caller ID matched against your Odoo contacts, and call logs are recorded against the relevant record. See our integration page for more on how telephony and business applications work together.
Yes, if required. We provide hardened SSH gateway servers with key-based authentication and audit logging. Access can be configured to suit your needs — from full root access to restricted access for specific tasks.
Yes. We support deployment of OCA modules and custom modules alongside the core Odoo Community codebase. Modules are managed through version control, enabling clean upgrades and rollbacks. If you are developing your own modules or working with a developer, you push your code and we ensure it runs correctly in production.
Yes. We can port your existing numbers from your current provider at no charge. Your numbers are not tied to a physical location — if you move office or work remotely, your numbers stay with you.
Yes. We can migrate domains, email, applications and data from other providers. The process depends on what you are moving — for some services it is straightforward, for others (such as Odoo databases) there is a defined transfer process. See our Odoo database transfer guide for an example, or get in touch to discuss your specific situation.
Yes. We provide multiple related environments as standard for well-managed deployments. These typically include a preview database (a snapshot of production for testing changes on live data), a staging or UAT environment (with anonymised data for verifying new development), and development environments for building and testing modules. This means changes are validated before they reach your users.
Yes. VoIP apps are available for both Android and iOS. You can make and receive calls on your business number from your mobile, wherever you have an internet connection. Calls between your VoIP devices are free regardless of location.
Yes. If your application runs on Linux — whether in a Docker container, on a VM, or as a standalone service — we can host it. We work with you to understand the requirements and build an appropriate environment, including networking, storage, email integration and SSL.
Yes. We handle domain transfers in and manage the process for you. There are no charges for transferring domains away from Cloudient either. See our domain information page for full details.
Odoo Community is the open source edition, freely available and maintained by the community and the OCA (Odoo Community Association). Odoo Enterprise is the proprietary edition sold by Odoo S.A. with additional features and a per-user licence fee. Cloudient specialises in the Community edition, which covers the core business functions — accounting, CRM, sales, purchasing, inventory and more — without licence costs. The OCA ecosystem provides many additional modules that extend functionality further.
No. VoIP works with software phones (apps on your computer or mobile), dedicated desk phones, or a combination. You need a reasonable internet connection but no specialist hardware or phone lines. We can advise on suitable handsets if you prefer physical phones.
No. We manage the infrastructure and applications on your behalf. You use the applications through their normal web interfaces. If you have technical staff or developers, we can provide the level of access they need, but it is not a requirement.
Yes. Backup management is included with every managed service. Backup strategies are designed around your requirements — from file-level backups to full environment replication with regular tested restores. Offsite backup to secondary locations is available for disaster recovery.
No. We run our own physical infrastructure. This gives us complete control over the environment and means we always know exactly where your data is. There is no dependency on hyperscaler platforms or proprietary cloud services.
Get in touch and tell us what you need. We will discuss your requirements, provide a quote for standard scenarios, and agree a plan. For more complex requirements, a consultation may be needed to properly establish the scope before quoting.
Please follow our responsible disclosure policy. This provides guidelines for reporting security issues with our services and systems. You can also report issues via our contact form using the "Security report" subject.
We support OpenUpgrade migration paths. Upgrades are planned and executed with a testing environment where the migration is verified against your data before committing. We generate changelogs, review warnings and errors, and provide a summary so you know exactly what has changed. Rollback capability is maintained throughout the process.
We conduct regular code scanning, dependency checks, and infrastructure patching. We use open source software which benefits from broad community review and rapid fixes. We do not assume our systems are free of issues — our responsible disclosure policy provides a clear process for managing issues as they are found. If we discover a vulnerability affecting your services, we act on it directly.
We charge a one-off set-up fee followed by a recurring subscription. Your subscription is based on a service profile that defines what you need — the cost is fixed and predictable, not metered by usage. If your needs change, we adjust the profile. See our pricing page for full details.
Details of email app configuration are on the E-mail settings page. It is important to select an encryption option and SSL/TLS is recommended.
We adjust your service profile to match. This is the key control for your spend — you decide the level of service and the cost follows. Whether you need to scale up, add new applications, or simplify your setup, we reconfigure accordingly.
Our infrastructure is monitored and we are alerted to availability issues automatically. We respond directly — there is no third-party support queue. For services where high availability is critical, we can configure redundancy and failover. Disaster recovery options including replication to secondary sites are available.
An SSL certificate encrypts the connection between your users and your services, protecting data in transit. It is what puts the padlock icon in the browser address bar. Yes, you need one — and we provide SSL certificates as standard for all hosted services, automatically provisioned and renewed.
IP-based restriction limits access to your services to specific internet addresses — only connections from approved locations can reach the service. This is the simplest form of access control and is effective for services that do not need to be publicly available. Visit our What's my IP address page to find your current address, and send it to us to configure access.
Multi-factor authentication (MFA) adds a second step when logging in — typically a code from an app on your phone or a hardware key. Even if your password is compromised, the attacker cannot log in without the second factor. We strongly recommend enabling MFA on all services that support it. Authenticator apps such as FreeOTP or Aegis are preferred over SMS codes. See our password policy guidance for more details.
Plus-addressing lets you create variations of your email address on the fly by adding a
+ and a tag before the @ symbol. For example, you+amazon@example.com still arrives in your inbox but lets you identify which service shared your address if you start receiving spam. See our guide to plus-addressing for details.
Most hosting providers offer commodity services — shared hosting, cPanel, standard packages. Cloudient is a boutique provider that runs its own infrastructure, deploys and manages open source applications as a service, and provides personal support from the team that built your environment. We handle the full stack from the hardware through to the application, and our services integrate with each other by design.
We accept payment by card, regular bank transfer, direct debit and SEPA. Cloudient is UK VAT registered and all prices are quoted exclusive of VAT.
We work with high-growth companies, start-ups, small businesses, charities and foundations. Our clients typically need more than commodity hosting — they want open source applications configured to their requirements, hosted on infrastructure they can trust, with personal support from a provider who understands the software.
Our infrastructure is hosted in European data centres, currently in France with UK locations planned. We chose to host in Europe for the strong data protection framework provided by EU regulations. We run our own hardware — we do not resell hyperscaler or third-party cloud services.
We specialise in Odoo Community, Nextcloud, Jitsi, PeerTube, and identity management (OpenLDAP, LemonLDAP, FusionIAM). We also host bespoke and containerised applications — if it runs in a Docker container or on a Linux VM, we can host it. See our application hosting page for details.
The following apps are most popular with our users:
- Thunderbird (PC/Linux/Windows)
- Outlook (Windows)
- Apple mail (MacOS)
- K9 Mail (Android)
- Bluemail (Mobile devices)
This is usually caused by missing or misconfigured email authentication records. SPF tells receiving servers which servers are allowed to send email for your domain. DKIM adds a cryptographic signature to verify the message has not been altered. DMARC ties these together with a policy for handling failures. We configure all three as standard for every domain we manage. If you are experiencing deliverability issues, get in touch and we will investigate.
Forwarding email to external ISP's creates risks of generating junk mail relays.
This is because it is not feasible to check in real-time if the address at the destination ISP is valid or not. If our servers accept the message, and then are unable to send it on, we are stuck with the message.
Spammers may use false senders, and the bounce message becomes the spam (known as backscatter).
Therefore we don't allow offsite forwarding to high-volume ISP's.
We do offer custom forwarding to enterprise email servers. Please get in touch to discuss.
This is because it is not feasible to check in real-time if the address at the destination ISP is valid or not. If our servers accept the message, and then are unable to send it on, we are stuck with the message.
Spammers may use false senders, and the bounce message becomes the spam (known as backscatter).
Therefore we don't allow offsite forwarding to high-volume ISP's.
We do offer custom forwarding to enterprise email servers. Please get in touch to discuss.
The root cause is that the specification for the SMTP (email sending) protocol (RFC 5322) is such that any line of an email MUST NOT exceed 1000 characters.
The problem is, despite it being a 'MUST NOT' in the specifications, it appears that Microsoft clients (eg. Outlook, IIS, etc.) ignore this part of the specification. It is uncommon for a line in an email to get this long, so it is not all Microsoft-based mail, but if it does occur, those emails will be invalid SMTP messages.
Lines that are too long can be built up when there are many messages in a thread. The mail client should fold these lines tro be within the specification.
Many modern mail servers enforce this limit and will reject the message. The solution is to create a new email which then should be deliverale.
The problem is, despite it being a 'MUST NOT' in the specifications, it appears that Microsoft clients (eg. Outlook, IIS, etc.) ignore this part of the specification. It is uncommon for a line in an email to get this long, so it is not all Microsoft-based mail, but if it does occur, those emails will be invalid SMTP messages.
Lines that are too long can be built up when there are many messages in a thread. The mail client should fold these lines tro be within the specification.
Many modern mail servers enforce this limit and will reject the message. The solution is to create a new email which then should be deliverale.