- If independent, documented enterprise compliance and certification evidence is required
- The vendor does not publish SOC 2/ISO status, detailed hosting region options, or a detailed security architecture on public pages; this can impede procurement in regulated environments.
- If a single control plane for many resource types is required
- Organizations seeking a single product that explicitly covers SSH, Kubernetes, databases, internal web apps, and secrets management may find more clearly-documented breadth with other platforms.
- If identity-only SSH enforcement is the primary objective without a new terminal UX
- For organizations that only need identity-based SSH policy enforcement within existing connectivity fabrics, lightweight network/identity products that provide SSH policies may be a simpler fit.
- If browser-rendered SSH must be part of a broader Zero Trust/SASE consolidation
- Organizations consolidating on a Zero Trust stack that includes SWG/CASB and policy plane integration may prefer platforms that already include SSH browser rendering as one component of that stack.
- If open-source and self-hosting are procurement or deployment requirements
- Open-source self-hosted PAM/bastion alternatives exist and may be preferred where community editions and source control are procurement drivers.
- Current limitations acknowledged in public materials
- Public-facing marketing does not enumerate product limitations in detail.
- Features on the roadmap
- No public roadmap or feature timelines were located.
- Scale limitations
- Documented system limits by tier: Personal (10 systems), Starter (150 systems), Pro (500 systems); Enterprise limits are not specified and likely negotiable.
- Security or compliance gaps
- No publicly documented security certifications (SOC 2, ISO) or published privacy policy located in accessible public sources.
- API limitations or integration constraints
- No public API documentation or comprehensive integration list was located.