Running a server should feel as easy as building the website on it.

What they said

It started with one sentence on a call. Everything below traces back to it.

What I heard

In the first call I listen for the problem under the request. 3 notes came out of it, and they became the brief.

The plan

Before any pixels, a sketch everyone could point at and argue with. Cheap to change, and it keeps the client's words in the room.

+------------------------------------+
| menu   |  my services  [ + build ] |
| ----   |  +------+ +------+ +----+ |
| ----   |  | cpu  | | ram  | | __ | |
| ----   |  +------+ +------+ +----+ |
|        |  |||  ||| |||| ||  |||    |
+------------------------------------+

The decisions

1. 01Processor, memory and storage as three simple gauges, so health reads at a glance.From “Server health is hard to read.”
2. 02Turn on, turn off and restart sit together, one click each.From “Every site needs the same few actions.”
3. 03Every project in one list, with its address, its status and a Connect button.From “Customers run many projects at once.”

solid-builder

1. Said
2. Heard
3. Sketch
4. Design
5. Shipped

What changed

• Server health readable in seconds.
• The everyday actions one click away.
• Every project managed from one screen.

solid-builderLiveView the design

1. Said
2. Heard
3. Sketch
4. Design
5. Shipped