CloudPanel Gateway

What the company appears to be: A self-reported server automation control plane named CloudPanel Gateway, built by one developer (Sumit Gohil), designed to provide secure, programmable access to CloudPanel-managed servers via REST APIs, MCP tools, and a local CLI. It aims to replace manual dashboard or SSH-based workflows with structured, permissioned operations.

What changed: The project evolved from an API and MCP wrapper for CloudPanel’s CLI into a broader automation control plane that supports multiple interfaces (REST, MCP, CLI) and enforces scoped permissions and policy gates.

Single most important open question: Is there any evidence of real-world usage or adoption beyond the author's own development and testing?

The description states that CloudPanel Gateway is a secure server automation control plane. It provides:

• REST APIs for applications and integrations
• MCP tools for AI agents
• A local administrator CLI for controlled server operations

It supports infrastructure workflows such as:

• Site management
• Logs
• Deployments
• Backups
• Runtime management
• PHP and TLS controls
• Static/Node/SSR application hosting
• CloudPanel-compatible cron jobs

The system is built in Go, designed to run as a single binary with minimal footprint. It separates public interfaces from privileged actions using:

• Scoped permissions
• Local policy gates
• Explicit confirmations for destructive actions
• Revision checks for concurrent changes
• Audit events for sensitive operations

It interacts with CloudPanel and the underlying OS through:

• Privileged helper services
• SQLite-based cron job updates (by directly modifying CloudPanel’s database and regenerating cron files)

Evidence: Self-reported by author.

The author states that CloudPanel Gateway was initially conceived as an API and MCP wrapper for CloudPanel’s CLI, but later evolved into a secure server automation control plane.

The positioning is:

• A safer, more programmable alternative to manual dashboard or SSH-based workflows.
• Designed to allow administrators, platforms, and AI agents to interact with infrastructure through structured tools and explicit security boundaries.
• Not intended to replace CloudPanel but to extend its capabilities in a secure way.

Evidence: Self-reported by author. No external validation or market positioning data provided.

The description does not explicitly name target customers or define an Ideal Customer Profile (ICP). However, it implies:

• Primary users may be system administrators managing CloudPanel servers
• Secondary users could include platforms or AI agents seeking to automate server operations
• The product is built for environments where CloudPanel is used, suggesting a specific niche in web hosting and infrastructure management

There is no evidence of:

• Named customers
• Customer segments
• Use cases beyond the author’s own testing

Evidence: Inferred from context; not explicitly stated.

No information is provided about:

• Revenue model
• Pricing structure
• Monetization strategy
• Paid features or tiers

The project is described as a self-built tool, not a commercial product. It is not clear whether it is intended for sale, licensing, or internal use.

Evidence: Not evidenced.

The system is built in Go, designed to be deployed as a single binary with a small operational footprint.

Architecture:

• Public interfaces (REST, MCP, CLI) are separated from privileged actions
• Uses scoped permissions
• Implements local policy gates
• Requires explicit confirmations for destructive actions
• Includes revision checks, audit events, and concurrent change handling

Key technical features:

• Direct SQLite interaction for cron jobs (modifies CloudPanel’s database and regenerates cron files atomically)
• Isolated helper services for privileged operations
• Support for CI/CD release signing with Minisign

Challenges addressed during development:

• SQLite transaction blocking
• Service readiness races
• Optional cache directory failures
• Non-interactive release signing

Evidence: Self-reported by author.

There is no evidence of:

• Revenue
• Customers
• User adoption
• Product usage metrics
• Market traction or growth

The project is described as a personal development effort, built and tested on disposable CloudPanel servers. It was submitted to a hackathon, indicating it may be in early stages.

Evidence: Not evidenced.

No information is provided about:

• Competitors
• Market landscape
• Alternative solutions
• Product differentiation

The author does not reference existing tools or platforms that offer similar functionality.

Evidence: Not evidenced.

• Single-person development: The entire project was built by one individual (Sumit Gohil), which raises questions about scalability, long-term maintenance, and support.
• No external validation or adoption: No evidence of real-world usage beyond the author’s own testing.
• Unproven commercial viability: The product is not described as a commercial offering; no pricing, monetization, or business model details are provided.
• Limited scope: It is tightly coupled to CloudPanel and its ecosystem, which may limit broader applicability.

Inference: The lack of traction, customers, or revenue suggests the project has not yet entered a market-facing phase.

1. What specific use cases are you targeting beyond your own testing?
2. Are there any existing CloudPanel users or partners interested in adopting this tool?
3. How do you plan to scale beyond a single developer and personal development environment?
4. Is there a roadmap for monetization or commercial deployment?
5. What are the key technical challenges that remain unresolved or untested at scale?