The Aethir Checker Platform supports the operation and verification of Checker Nodes, a core component of Aethir’s decentralized cloud infrastructure.
Checker Nodes verify the integrity and performance of Containers to ensure network-wide Quality of Service. To accommodate different participation models, the platform consists of three products:
- Owner Portal — for Node NFT holders to monitor rewards and manage delegation
- Checker Client — a lightweight runtime that keeps nodes active and compliant
- Operator Portal — for professional operators to manage Checker Nodes at scale
Although all three platforms interact with the same node infrastructure, they serve distinct user roles, requiring clear responsibility boundaries and consistent system state representation.
Project Duration: April 2024 - Sept 2025
My Role: Product Designer, UXD and UI.
Responsibility:
As the Product Designer, I worked closely with product managers, engineers, and infrastructure teams to:
- Define user roles, responsibilities, and system boundaries across platforms
- Design information architecture and state models for node status and monitoring
- Translate technical constraints into clear UX patterns and dashboards
- Iterate on usability findings to improve clarity, error prevention, and scalability
The Problem:
The UX Goal:
<aside> <img src="/icons/star-of-life_lightgray.svg" alt="/icons/star-of-life_lightgray.svg" width="40px" />
Although all three platforms serve the same Checker Node infrastructure, each addresses distinct user goals at different layers of participation.
By clearly differentiating user intent and responsibilities across these three platforms, the Checker Platform aligns incentives, reduces confusion, and enables reliable participation in Aethir’s decentralized cloud infrastructure.
</aside>
<aside> 👤
The Owner Portal is designed for Checker Node NFT holders.
The experience prioritises financial clarity and trust, not technical control.
</aside>
<aside> 🖥️
The Checker Client is the runtime layer of node operation.
The client is designed to “stay out of the way” while ensuring the node remains active and compliant.
</aside>
<aside> 🌍
The Operator Portal serves professional node operators who manage Checker Clients across multiple machines.
Here, the experience supports operational decision-making at scale, not ownership concerns.
</aside>
A single Checker Node follows one lifecycle, while different roles interact with it at distinct moments, through different platforms, with intentionally scoped visibility.
<aside> 🖥️
While all roles interact with the same Checker Node, ownership, operation, and execution are deliberately separated.
Each platform exposes only the information required for that role’s decisions—preserving trust boundaries, preventing responsibility overlap, and enabling the system to scale across owners, operators, and runners.
</aside>
Role-based visibility
Single source of truth for node state
Progressive disclosure for verification logic