Client
A European hosting company specializing in cloud infrastructure and offering a cheaper alternative to modern hosting providers. The organization focuses on small and medium-sized businesses with the prospect of growing to enterprise clients.
Problem
There was a need for a single platform that would allow the company to continue growing and offering more services while not interfering with its current customer base.
What Chudovo Delivered
A special team at Chudovo worked on developing a microservice-oriented hosting platform that includes domain and environment management, multi-tenancy, networking & DNS, DDoS protection, bot management, configurable CDN, CI/CD, and monitoring with performance reporting. Afterward, there were other functions like user, service, and payment management, two-factor authentication, and virtualization management like VMManager and Virtfusion.
Outcome
The modular nature of this architecture helps the client grow their service offerings. The client says they got services delivered ahead of schedule, risk management done by the Chudovo team in advance, and reliable estimates.
Client
Same European hosting company as above, with the work extended to the customer web interface.
Problem
Following development of the hosting platform by Chudovo, the hosting company required an intuitive web interface for itself, in order for its customers to manage hosting services, tariffs, and accounts independently.
What Chudovo Delivered
A front-end developer developed the web client cabinet, with features such as managing services and subscriptions, account settings, multilingual support, and API integration with a typed data layer through SWR, in 65 man-days.
Outcome
The client successfully released a fully functional, mobile-optimized web panel where customers can manage their hosting settings without reaching out to support.
The solutions take care of the service lifecycle. This includes resource provisioning, service deployment, configuration and changes, and suspension or termination of a service. The provisioning algorithm is directly linked to the infrastructure, and thus the customer interaction within the portal initiates the infrastructure change without an intermediate manual step.
Companies, their users, roles, and quotas form the core of the platform. Multi-tenancy ensures that each customer’s resources and data are separate. Administrative delegation enables bigger companies to manage sub-users and roles.
Customers can control their own resources, configuration, and request support through the self-service portal. Meanwhile, the internal administrator control panel will provide the same visibility along with the ability to perform certain actions regarding the particular tenant or service. It also contains logs, status, and error visibility for the operations team to see the picture of the platform operations.
DNS records and zones, domain registration, and IP management are provided as a service in the service catalogue, managed by the platform directly.
Usage statistics create service plans, generate invoices, and enable payments on the platform, which is tied to each company’s billing system. Chudovo estimates billing integration for each individual client, as hosting businesses usually have different billing models.
Modular and Microservices Architecture
Chudovo structures hosting platforms as independent services with defined boundaries, so one module can change or scale without redeploying the rest of the system.
API-First and Event-Driven Integration
Chudovo connects services through APIs and event flows, keeping the platform open to new infrastructure providers, billing systems, and internal tools without a redesign of the core system.
Infrastructure and Workload Orchestration
Chudovo builds a control plane that provisions virtual machines, containers, and infrastructure resources through infrastructure APIs, replacing manual workload setup, with support for virtualisation environments such as VMManager and Virtfusion.
DevOps, CI/CD and Infrastructure Automation
Chudovo builds automated deployment pipelines that move platform changes into production with less manual intervention and fewer opportunities for configuration drift.
Hosting providers
Cloud service providers
Infrastructure providers
SaaS companies launching infrastructure services
Tenant and Access Security
Chudovo incorporates identity and access management, role-based permissions, multi-factor authentication, and API security in order to ensure that all resources of one tenant are separated from the resources of all other tenants within the platform. Secrets and credentials are managed separately from the application code.
Platform and Network Security
Chudovo incorporates DDoS protection and bot management, as well as vulnerability management and secure communication between services, into the network layer.
Availability and Disaster Recovery
Chudovo implements redundancy, failover procedures, and backup and restore procedures in order to minimize the effects of infrastructure failures on the entire platform. The restoration and failover processes are regularly tested under real failure scenarios to make sure that these procedures actually restore service.
Observability, SLOs and SLA Readiness
The service level indicators are used to measure what the platform provides, the service level objectives are used to set a target for these measurements, and the service level agreements commit a provider to providing a certain level of service to its clients. Chudovo develops platforms that operate according to certain SLOs; however, SLAs are based on the client's infrastructure providers and operating procedures.
Platform and Infrastructure Assessment
Chudovo maps existing services, tenants, infrastructure APIs, and technical debt to build a target architecture around what the platform actually needs.
Target Architecture
The team defines control-plane boundaries, the tenancy model, infrastructure abstraction and integration architecture, including a migration path where a current system exists.
Incremental Build or Modernisation
Platform modules ship in priority order. Working infrastructure stays in place unless replacing it delivers a clear benefit; modernisation projects rarely need a full rewrite.
Production Readiness
Performance and load testing, security checks and recovery-scenario testing confirm a release is ready for production, alongside a review of what the operations team can observe once it's live.
Operation and Evolution
After launch, Chudovo supports new infrastructure integrations, new service plans, and ongoing optimisation, so the platform keeps pace with the client's business.
One Team, Both Layers
Most hosting-platform vendors build the backend or the customer-facing UI, not both. Chudovo delivered the platform's API and the web UI on top of it, so the two were never designed by teams guessing at each other's contracts.
Built to Add Providers, Not Rebuild for Them
Most hosting platforms get locked to whatever infrastructure provider they launched with. On the delivered platform, provisioning logic stayed separate from day one, so adding VMManager or a new provider was a scoped integration, not a rewrite.
Modernization That Doesn't Start From Zero
A platform with paying customers has to stay live while it changes. Chudovo audits what's actually creating risk first, and replaces only that.
Telecom-Grade Provisioning and Billing Logic
Metered usage and billing that has to match the infrastructure is the same problem hosting and telecom platforms both run on. Chudovo's work across the telecom industry means it isn't being solved for the first time on your platform.