Freelance Contract • 2024
Dockhive: Decentralized Cloud Platform
Overview
Designed how developers deploy and scale in a decentralized world, reducing setup time from 20 minutes to under five, scaling to 1,500+ active nodes across eight regions, and projecting $2.3M in staked operator value.
Role: Lead Product Designer
Scope: Product Design, UX Architecture
Timeline: 5 months (concept → launch)
Stack: Figma, React, Tailwind, Dune API, PostHog
Context
Dockhive is a decentralized cloud platform that lets developers deploy and scale AI or blockchain workloads across a distributed compute network; think AWS, but powered by a global network of independent nodes.
I shadowed 12 DePIN developers during node setup and found a recurring pattern: average setup time was 20 minutes, error rates were high, and every developer said the same thing: “It’s either powerful or usable, never both.”
Existing node managers were fragmented and brittle: CLI-only workflows, zero observability, confusing network states, and no predictability. The challenge: decentralization was invisible. Developers couldn’t see which nodes were handling their workloads, why deployments failed, or how to optimize performance. Without visibility, trust evaporates, and they return to AWS.
My Role & Approach
I led product design and UX architecture, mapping the developer dashboard, deployment flow, and orchestration model, while contributing to front-end layout in React and Tailwind.
Key Insight: decentralization shouldn't feel different to developers. They don't care about the underlying network topology; they care about speed, reliability, and being able to debug when things break. So I designed around three principles:
- Make the network transparent: show nodes, health, and resource allocation in real time
- Simplify deployment to match centralized cloud UX (one-click, not config files)
- Build trust through observability: logs, metrics, and failure states always visible
Solution
One-Click Deployment: Simplified complex node setup from 20 minutes to under 5. Developers connect their repo, choose a compute tier, and the platform handles orchestration across nodes.
Network Transparency: Real-time spatial visualization of active nodes by region, workload type, and health status. Signal View combines uptime, gas cost, and performance deltas into one dynamic map so developers can finally see what’s happening under the hood.
Full Observability: Logs, metrics, and error tracking integrated directly into the dashboard, replacing console spam with clarity. When something fails, developers instantly see which node, why it failed, and how to recover.
Impact
Dockhive launched in beta mid-2024 and gained traction with developers building on decentralized infrastructure:
- Setup time dropped from 20 minutes to under 5 during testing with early developers
- Scaled from 30 testers to 1,500+ active nodes across 8 regions, running AI inference and blockchain validators
- 20K+ job executions handled in load tests, proving the system could scale
- Error rate decreased 60% because developers could actually see what was failing and why
- $2.3M projected TVL in staked operator value for phase one
This project proved something critical: decentralization doesn't need to feel experimental. When you give developers the same clarity they get from centralized clouds, they'll choose the decentralized option. Visibility builds trust. Trust drives adoption.
“AWS, but the keys are mine.” — Developer feedback (became the unofficial slogan)
Freelance Contract • 2024
Dockhive: Decentralized Cloud Platform
Overview
Designed how developers deploy and scale in a decentralized world, reducing setup time from 20 minutes to under five, scaling to 1,500+ active nodes across eight regions, and projecting $2.3M in staked operator value.
Role: Lead Product Designer
Scope: Product Design, UX Architecture
Timeline: 5 months (concept → launch)
Stack: Figma, React, Tailwind, Dune API, PostHog
Context
Dockhive is a decentralized cloud platform that lets developers deploy and scale AI or blockchain workloads across a distributed compute network; think AWS, but powered by a global network of independent nodes.
I shadowed 12 DePIN developers during node setup and found a recurring pattern: average setup time was 20 minutes, error rates were high, and every developer said the same thing: “It’s either powerful or usable, never both.”
Existing node managers were fragmented and brittle: CLI-only workflows, zero observability, confusing network states, and no predictability. The challenge: decentralization was invisible. Developers couldn’t see which nodes were handling their workloads, why deployments failed, or how to optimize performance. Without visibility, trust evaporates, and they return to AWS.
My Role & Approach
I led product design and UX architecture, mapping the developer dashboard, deployment flow, and orchestration model, while contributing to front-end layout in React and Tailwind.
Key Insight: decentralization shouldn't feel different to developers. They don't care about the underlying network topology; they care about speed, reliability, and being able to debug when things break. So I designed around three principles:
- Make the network transparent: show nodes, health, and resource allocation in real time
- Simplify deployment to match centralized cloud UX (one-click, not config files)
- Build trust through observability: logs, metrics, and failure states always visible
Solution
One-Click Deployment: Simplified complex node setup from 20 minutes to under 5. Developers connect their repo, choose a compute tier, and the platform handles orchestration across nodes.
Network Transparency: Real-time spatial visualization of active nodes by region, workload type, and health status. Signal View combines uptime, gas cost, and performance deltas into one dynamic map so developers can finally see what’s happening under the hood.
Full Observability: Logs, metrics, and error tracking integrated directly into the dashboard, replacing console spam with clarity. When something fails, developers instantly see which node, why it failed, and how to recover.
Impact
Dockhive launched in beta mid-2024 and gained traction with developers building on decentralized infrastructure:
- Setup time dropped from 20 minutes to under 5 during testing with early developers
- Scaled from 30 testers to 1,500+ active nodes across 8 regions, running AI inference and blockchain validators
- 20K+ job executions handled in load tests, proving the system could scale
- Error rate decreased 60% because developers could actually see what was failing and why
- $2.3M projected TVL in staked operator value for phase one
This project proved something critical: decentralization doesn't need to feel experimental. When you give developers the same clarity they get from centralized clouds, they'll choose the decentralized option. Visibility builds trust. Trust drives adoption.
“AWS, but the keys are mine.” — Developer feedback (became the unofficial slogan)
Freelance Contract • 2024
Dockhive: Decentralized Cloud Platform
Overview
Designed how developers deploy and scale in a decentralized world, reducing setup time from 20 minutes to under five, scaling to 1,500+ active nodes across eight regions, and projecting $2.3M in staked operator value.
Role: Lead Product Designer
Scope: Product Design, UX Architecture
Timeline: 5 months (concept → launch)
Stack: Figma, React, Tailwind, Dune API, PostHog
Context
Dockhive is a decentralized cloud platform that lets developers deploy and scale AI or blockchain workloads across a distributed compute network; think AWS, but powered by a global network of independent nodes.
I shadowed 12 DePIN developers during node setup and found a recurring pattern: average setup time was 20 minutes, error rates were high, and every developer said the same thing: “It’s either powerful or usable, never both.”
Existing node managers were fragmented and brittle: CLI-only workflows, zero observability, confusing network states, and no predictability. The challenge: decentralization was invisible. Developers couldn’t see which nodes were handling their workloads, why deployments failed, or how to optimize performance. Without visibility, trust evaporates, and they return to AWS.
My Role & Approach
I led product design and UX architecture, mapping the developer dashboard, deployment flow, and orchestration model, while contributing to front-end layout in React and Tailwind.
Key Insight: decentralization shouldn't feel different to developers. They don't care about the underlying network topology; they care about speed, reliability, and being able to debug when things break. So I designed around three principles:
- Make the network transparent: show nodes, health, and resource allocation in real time
- Simplify deployment to match centralized cloud UX (one-click, not config files)
- Build trust through observability: logs, metrics, and failure states always visible
Solution
One-Click Deployment: Simplified complex node setup from 20 minutes to under 5. Developers connect their repo, choose a compute tier, and the platform handles orchestration across nodes.
Network Transparency: Real-time spatial visualization of active nodes by region, workload type, and health status. Signal View combines uptime, gas cost, and performance deltas into one dynamic map so developers can finally see what’s happening under the hood.
Full Observability: Logs, metrics, and error tracking integrated directly into the dashboard, replacing console spam with clarity. When something fails, developers instantly see which node, why it failed, and how to recover.
Impact
Dockhive launched in beta mid-2024 and gained traction with developers building on decentralized infrastructure:
- Setup time dropped from 20 minutes to under 5 during testing with early developers
- Scaled from 30 testers to 1,500+ active nodes across 8 regions, running AI inference and blockchain validators
- 20K+ job executions handled in load tests, proving the system could scale
- Error rate decreased 60% because developers could actually see what was failing and why
- $2.3M projected TVL in staked operator value for phase one
This project proved something critical: decentralization doesn't need to feel experimental. When you give developers the same clarity they get from centralized clouds, they'll choose the decentralized option. Visibility builds trust. Trust drives adoption.
“AWS, but the keys are mine.” — Developer feedback (became the unofficial slogan)