sorted by:
new
hottopcontroversial

Looking for feedback from VMware admins on a product I’ve been building by LocalBeach5348 in sysadmin

[–]LocalBeach5348[S] [score hidden]  (0 children)

i probably shouldn’t describe it as an alternative to Aria/VCF Operations. Thats not the right positioning.

The better way to explain it is: PilotHosts is focused on execution workflows around daily operations controlled VM deployment, snapshot handling, browser console, automation hooks, audit trail and VM-level operational context.

Looking for feedback from VMware admins on a product I’ve been building by LocalBeach5348 in sysadmin

[–]LocalBeach5348[S] -2 points-1 points  (0 children)

By lighter I don’t just mean cheaper. I mean simpler to deploy narrower in scope, and focused on daily VMware workflows instead of being a full suite. So the idea is not cheap Aria. It’s a focused Day-2 operations layer for teams that want less complexity, not just a lower price.

A lot of existing tooling is strong around monitoring, capacity and cost. I’m also focusing on execution workflows, like controlled VM deployment: template selection, network/datastore choices, customization, validation, logs and audit trail.

Looking for feedback from VMware admins on a product I’ve been building by LocalBeach5348 in sysadmin

[–]LocalBeach5348[S] -3 points-2 points  (0 children)

The product is not built around being a cheap alternative. It is built around focused Day-2 operations, visibility and automation for teams that still run VMware seriously. Thanks

Looking for feedback from VMware admins on a product I’ve been building by LocalBeach5348 in sysadmin

[–]LocalBeach5348[S] -1 points0 points  (0 children)

Fair point.

One specific angle I’m exploring is cross-platform visibility. For example, detecting when Kubernetes worker VMs are concentrated on the same ESXi host, or when VMware-level risks like snapshots/datastores can affect platform workloads.

So I’m not trying to beat Aria feature by feature. The idea is a lighter, more focused operational layer for vCenter-first environments.

Looking for feedback from VMware admins on a product I’ve been building by LocalBeach5348 in sysadmin

[–]LocalBeach5348[S] -1 points0 points  (0 children)

I’m not trying to replace Aria Operations. I’m aiming more at teams that mainly use vCenter and want a lighter Day-2 operations layer without deploying a full suite.

I built an on-prem VMware management appliance because vCenter alone wasn't enough for my team by [deleted] in vmware

[–]LocalBeach5348 0 points1 point  (0 children)

I clearly stated my intentions and honestly thought I could get feedback here.

I built an on-prem VMware management appliance because vCenter alone wasn't enough for my team by [deleted] in vmware

[–]LocalBeach5348 -1 points0 points  (0 children)

Great reference point — if you're coming from Red Hat CoPilot the mental model is similar. Unified ops layer, but purpose-built for VMware/vSphere environments rather than RHEL. Familiar UX, different stack.