CloudSmith is a full-lifecycle platform for Hyper-V and Azure Local hybrid cloud environments. Not a deployment tool. Not a monitoring add-on. Every capability — from pre-sales sizing to day-2 operations to retirement — in one modular, composable platform.
Today's operations teams rely on fragmented tooling — scripts, SCVMM, Windows Admin Center, vendor consoles, spreadsheets, and tribal knowledge. CloudSmith replaces that patchwork with a single, extensible platform that covers the entire infrastructure lifecycle.
Strategy and sizing, deployment, day-2 operations, security, governance, optimization, and eventual retirement. Every phase is a first-class capability, not an afterthought.
Enable the Planning module without enabling Monitoring. Enable Troubleshooting without enabling Deployment. Every module installs, upgrades, and removes independently. No bloat forced on you.
Intelligent log analysis, anomaly detection, guided diagnostics, and natural-language queries enhance your engineers — they don't replace them. AI is always optional and explainable.
Multi-tenant, scoped RBAC, delegated access via Azure Lighthouse, and white-label branding. Managing 30 customers is the same experience as managing 1 — just scaled.
Dell iDRAC, Lenovo XCC, HPE iLO, and DataOn hardware — all first-class targets behind a single abstraction layer. Firmware inventory, health, boot control, and OOB operations unified.
No proprietary lock-in. Self-host it, extend it, contribute to it. Community and OEM partners can ship modules into the same registry that ships with the platform.
CloudSmith organizes every capability around six lifecycle pillars — the complete journey from first conversations with a customer through years of steady-state operations and, eventually, graceful retirement.
Workload discovery, TCO and ROI analysis, vendor selection, cloud-vs-on-prem decision support. Answers the "should we, and if so — what hardware?" question.
S2D capacity sizing, Bill of Materials generation, network topology design, site surveys, Azure Local vs. Hyper-V decision questionnaire. Design artifacts, not guesswork.
Automated cluster deployment for Hyper-V and Azure Local. Storage Spaces Direct configuration, Network ATC, Arc onboarding, pre-flight validation. Repeatable, auditable, pipeline-driven.
Monitoring, update management, troubleshooting, workload lifecycle, image library, AI-assisted diagnostics, ITSM integration. The daily platform — not a one-time event.
Identity and access management, secrets management, security posture, compliance scanning, policy-as-code. Security is the foundation — not a module you bolt on later.
Right-sizing recommendations, resource reclamation, workload placement optimization, cost reporting and chargeback, modernization paths. Make what you have work harder.
Graceful decommissioning workflows, data sanitization, asset disposal tracking. The part every platform forgets to build. CloudSmith doesn't.
CloudSmith's modular architecture means every capability is an independently installable module. Enable what you need today — grow into the rest when you're ready.
cs / cloudsmith CLICloudSmith doesn't dictate where the control plane lives. Three models — pick what fits your security posture, connectivity requirements, and operational model today. You can migrate between models later.
The full CloudSmith control plane runs inside your data center. No Azure dependency required at runtime. Air-gapped environments supported. You own everything.
CloudSmith control plane runs in Azure Container Apps. Lightweight runners execute on-premises and report back. Ideal for MSPs and organizations already invested in Azure.
On-premises instance and PaaS control plane operate independently, connected by bidirectional selective sync. Best of both: local execution with cloud visibility and management.
CloudSmith ships incrementally. The MVP ships a working platform — planning, deployment, identity, and the full API surface. Operations and extended features follow in subsequent phases.
| Phase | Name | Focus | Key Modules |
|---|---|---|---|
| Phase IV | MVP | Platform kernel, identity, secrets, inventory, cluster management, deployment, planning, and the full external surface (API, SDK, CLI, PowerShell) | core, identity, secrets, inventory, cluster-mgmt, deploy, planning, api, sdk, cli, powershell |
| Phase V | First Operations | Day-2 operations: hardware management (Dell + generic Redfish), monitoring, updates, troubleshooting, workload lifecycle, image library, AI engine, MSP, runners | hardware-dell, hardware-generic-redfish, monitoring, update, troubleshooting, workload, image-library, ai-engine, msp, runners |
| Phase VI | Hyper-V Renaissance | Bidirectional sync, full Hyper-V cluster deployment parity, workload discovery and assessment, as-built documentation generation | sync, deploy-hyperv, assessment, docs-gen |
| Post-MVP | Extended Ecosystem | Security posture, governance, FinOps, ITSM, BCDR, Lenovo/HPE/DataOn hardware, AKS, AVD, migration, retirement, optimization, on-host agent, IaC providers | security, governance, finops, itsm, bcdr, hardware-lenovo, hardware-hpe, hardware-dataon, aks, avd, migration, retirement, optimization, agent, iac |
CloudSmith isn't a C-suite dashboard. It's a platform built for the engineers and operators who plan, deploy, and run Hyper-V and Azure Local environments every day.
Deploys and operates Hyper-V and Azure Local clusters day-to-day. Lives in the terminal. Needs fast answers and guided workflows — not dashboards designed for a demo.
Designs the infrastructure, creates Bills of Materials, sizes S2D clusters, plans network topology. Needs calculation tools and output artifacts — not vague spreadsheets.
Manages multiple clusters and sites, owns identity and policy, drives update compliance. Needs fleet-level visibility and policy enforcement — not per-cluster point-and-click.
Manages multiple customer environments from a single control plane. Needs scoped access, white-label branding, and customer-level reporting without context-switching between 30 portals.
CloudSmith is being built in the open. Follow the GitHub org to stay current — code repos open from day one of Phase IV.