Overview
Timeweb Cloud had Kubernetes, VMs, object storage, and load balancers. Each service shipped with its own UI and vocabulary.
For new customers, the product felt like infrastructure without a front door — capable, but hard to enter.
The redesign goal: one coherent path from signup to a running server.
Challenge
Engineers built quickly. End users saw terminals, configs, and inconsistent screens across services.
There was no shared UX model — each team owned its own patterns and language.
Most new users never deployed a first server.
Analytics showed ~70% dropped off before first deployment.
The interface tested technical patience instead of supporting a first success.
Research and Insight
We started by observing real users: startups, developers, designers, small business owners.
Each of them had one pain - infrastructure seemed unfriendly.
People don't want to "build a server by hand," they want to "deploy a project and have everything work."
We looked at how Amazon, DigitalOcean, and Hetzner solve this task, and understood the main thing:
all these platforms build UX around "an engineer", but not around "a person who just wants a result".
Concept
Timeweb Cloud is an attempt to make the cloud understandable.
The goal is to turn a DevOps tool into a product with transparent architecture, simple UX, and human interface.
We created the concept of "Cloud as Experience":
cloud not as code or infrastructure, but as a "visual environment" where everything is connected: computing, databases, network rules, storage.
The user sees how services interact with each other, can manage them visually, not "memorize commands".
Process and Design
The work began with an architecture map - we visualized all Timeweb Cloud components: compute, storage, network, DNS, load balancers, backups.
Each of them had its own API and UI.
We needed to combine everything into a unified system with recognizable visual logic.
Key UX Solutions
1. "Infrastructure as Map" model - the user sees their project architecture as connections between objects (server ↔ database ↔ domain ↔ load balancer).
2. "One-step principle" - any resource can be created in one window, without transitions and hidden settings.
3. "Smart Defaults" - most settings are selected automatically based on patterns, but can be changed if desired.
Architecture and Interaction
Technically, the platform is based on Kubernetes and Timeweb's own orchestration system.
The interface became a layer over Timeweb Cloud API - everything the user does is instantly reflected in the infrastructure.
Results
After launching the new version of Cloud Dashboard and server deployment interface:
What Changed
Timeweb Cloud ceased to be a product "for engineers" and became a product with engineering inside.
It became transparent, alive, and logical.
For the company, this became a symbol of transformation:
Impact
Timeweb Cloud is a story about how infrastructure becomes a product.
About how an engineering stack can turn into an understandable user experience.
More users reached first deployed server after UX redesign.
Shorter path from signup to running infrastructure.
Fewer confusion-driven tickets on core flows.