Leadership
CEO & Founder
Sets product direction, narrative standards, deployment philosophy, and the operating constraints that keep the system aligned to its identity.
Team
The team is represented by function, not persona theater.
Liminal is organized around operational roles. This page describes the structure that supports delivery, oversight, reliability, and growth without inventing public-facing identities.
Board
5 strategic oversight members
Provides governance, capital discipline, strategic pressure-testing, and long-horizon oversight across growth and infrastructure decisions.
Sales team
Client onboarding and growth
Qualifies inbound demand, shapes deployment expectations, coordinates onboarding, and keeps revenue discussions tied to practical fit.
Development team
Core system engineering
Builds the application layer, interaction behavior, page system, integration surface, and the logic that governs continuity and response quality.
Infrastructure team
Uptime, failover, and deployment
Maintains service reliability, region strategy, deployment health, failover readiness, and performance at the GPU and storage layers.
Why this page is structured this way
Role-based representation is more truthful for this site than placeholder biographies. Buyers need to know coverage and accountability, not fictional profile cards.
Next step
The team structure matters when the system is running on your site.
If you need to understand who covers architecture, uptime, onboarding, and product direction, the deployment review is where that mapping becomes specific.
Use Liminal to map out your future