Cloudmore Service Delivery

Experience is included!

Cloudmore has been delivering complex, high-scale technical solutions with a 99.99% SLA year-on-year for more than 15 years. The platform is designed to support the addition of new capabilities and functionality, ensuring that customers can customize and adapt their services to meet changing business needs. The platform is constantly upgraded, managed, and supported by a dedicated team of professionals with extensive experience in developing and executing high-scale multi-tenant solutions.

The platform is delivered as a single codebase SaaS service, with all management operations completed in the platform or via API calls, and runs on Microsoft Azure AWS in separated EU and US platforms. The platform uses SSL encryption to secure all data both in transit and at rest. Passwords are stored as salted hashes to add an extra layer of security, and daily backups and regular recovery tests are performed to ensure the platform is always available. Cloudmore also supports Role-Based Access Control (RBAC) and Key Account Manager (KAM) settings to control access and monitor usage.

Cloudmore's core development strengths lie in multi-tenancy, APIs, and scaling, making it a highly performant platform. The Cloudmore API supports integration with other business systems and is secured with OAuth 2.0 and JWT access token format. Detailed information on the API can be found in the Swagger document at https://api.cloudmore.com/swagger/.

Cloudmore is a secure, scalable, and flexible platform designed to support the needs of IT service providers. Cloudmore's core development strengths lie in multi-tenancy, APIs, and scaling, ensuring that the platform is highly performant and can be integrated seamlessly into existing technology stacks.

The platform is accessible through supported browsers, including Google Chrome, Mozilla Firefox, Microsoft Edge, Internet Explorer 11, and Safari.

Deployment and migration

Cloudmore onboarding can include platform configuration, data import, and integration work. The deployment plan should identify the services and customers in scope, the work each team owns, the required source data, and the target billing cycle. Agree on timing around those requirements and the readiness of your finance and operational systems.

For a controlled migration, we recommend agreeing on the following before go-live:

Data scope: which customers, tenant links, subscriptions, prices, and historical records will be carried over, and which will remain in the existing systems.
Validation: a representative billing comparison, checks for missing or duplicate records, and a documented list of unresolved differences.
Acceptance: named finance and operations approvers, agreed tolerances and evidence that the in-scope ERP import works as expected.
Cutover: when each system becomes authoritative, how changes during the transition are captured, and how duplicate customer billing is avoided.
Contingency: criteria for pausing the cutover, named decision-makers, and a recovery or rollback approach appropriate to the systems and transactions involved.

These are planning recommendations. Confirm the migration services, deliverables, and responsibilities included in your engagement with Cloudmore. Any rollback depends on what can safely be reversed in the connected systems. Final invoicing and credit notes remain in your ERP or accounting system.

Platform SLA

The Cloudmore SLA covers platform availability and our response times to support issues
View our SLA →

Data privacy and processing

When you use our solution, you’re trusting us with your data. We understand that this is a big responsibility and work very hard to secure your information and ensure that you're always in control of your data. Use the link below to view our privacy, data processing, security measures, and more
View our privacy terms →

100% Mobile Friendly

Carefully built in its core, Cloudmore looks great on any screen size, desktop, laptop, tablet or mobile device.

Find out more about customizing Cloudmore