Dustin DeYoung

The Morpheus Software platform anchors HPE's private cloud portfolio, shipping as HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials and serving as the core control plane for HPE SimpliVity PC1000, HPE Private Cloud PC3000, HPE Private Cloud PC7000, and HPE Private Cloud AI. Morpheus gives enterprises a unified control plane for hybrid infrastructure, reducing cost and complexity without locking them into a single vendor's stack.

Morpheus Data was acquired by HPE in August 2024, bringing a startup product and engineering organization into a Fortune 500 company with a much larger portfolio, customer base, and network of dependencies. I moved into engineering leadership during that transition, helping scale the organization while preserving the product knowledge, ownership, and speed that had driven Morpheus from the beginning.

As the business grew, we changed more than the size of the team. We evolved how engineering was structured, how work moved from strategy to execution, and how teams coordinated across products and organizations. I continue to remain technical and close to the platform, using that foundation to guide architecture and execution while broadening my perspective across people, process, product strategy, and the needs of the larger business.

Morpheus began as an effort to simplify the growing complexity of hybrid infrastructure. The platform gave IT teams a common layer for provisioning, automation, governance, and cost visibility across public clouds, private clouds, and on-premises environments without forcing them into a single vendor ecosystem.

I joined the engineering team in 2016 as a Senior Software Engineer and spent the following years helping build the platform from the inside out. My work crossed the full stack, including backend services, user interfaces, data models, cloud integrations, deployment systems, and platform architecture. Working across that breadth gave me a deep understanding not only of the technology, but also of how the product was used and operated by customers.

As Morpheus grew from an emerging startup into an enterprise platform, my responsibilities expanded with it. I became a Staff Engineer and then moved into engineering leadership, shifting from ownership of individual systems toward the architecture, team design, and engineering practices required to support a larger product and organization. That progression established the pattern that continues to shape my work: remain grounded in the technology while steadily widening the scope of the problems I help solve.

Bertram Capital acquires and grows operating companies, and Bertram Labs served as the technology engine behind that work. The team developed shared infrastructure and software for the firm and its portfolio companies, repeatedly encountering similar challenges across a diverse set of businesses.

Those recurring problems became products. BitCan provided cloud-based database backup and recovery, while OohLaLog delivered centralized cloud log management. Over time, the opportunity emerged to bring those capabilities together within a broader platform for managing increasingly complex infrastructure.

That platform became Morpheus. What began as an internal technology initiative grew into a dedicated software company, creating the environment where I would spend the next stage of my career helping build the product, scale the platform, and eventually grow into engineering leadership.

My early career was shaped by consulting, product development, and startup experimentation within the Indianapolis technology community. At 10-Spaces Consulting, Westlake Design, and DeveloperTown, I worked directly with clients and founders to turn business problems and early-stage ideas into working software. Moving across industries and company stages taught me to quickly understand unfamiliar domains, find the essential problem, and connect technical decisions to practical business outcomes.

Consulting also taught me to operate without a complete roadmap. Clients rarely arrived with perfectly defined requirements, so the work required discovery, product thinking, communication, and judgment alongside software development. Those experiences made ambiguity feel less like an obstacle and more like the natural starting point for building something useful.

Small Spark Labs became my outlet for moving from advising and implementing to creating. I used it to explore my own startup ideas and partner with founders on theirs. That included Ads2Leads, a digital marketing optimization platform I developed with two co-founders. These experiments introduced me to customer discovery, product strategy, market validation, technical architecture, and the realities of building without guaranteed demand.

At DeveloperTown, those threads came together in my role as an Associate Partner helping entrepreneurs turn ideas into operating businesses. One of those ideas became TenantTracker, a commercial real estate platform I helped take from concept to launch as CTO.

The through-line across these early experiences was learning to take responsibility for more than the code. I learned to understand the problem, shape the product, build the technology, and adapt the approach as customers and businesses revealed what they actually needed.