VMware vSphere
virtualization
Ocosify UIM
PlannedOne control layer for virtualization, private cloud and public cloud infrastructure.
Ocosify Unified Infrastructure Management is designed to bring infrastructure from different vendors, provider accounts and locations into a central inventory, operations and governance platform.
Provider ecosystem
Provider adapters for on-premises and hosted virtualization control planes.
virtualization
virtualization
private cloud
virtualization
virtualization
virtualization
private cloud
private cloud
Provider adapters for public cloud accounts, subscriptions, projects and regions.
public cloud
public cloud
public cloud
public cloud
public cloud
public cloud
public cloud
public cloud
public cloud
public cloud
Planned and roadmap entries are not commitments to a release date. Custom integrations require technical assessment.
From fragmentation to control
Infrastructure teams lose time and context when each platform, location and account has a separate inventory and control surface.
A provider-adapter layer and common resource model are intended to create consistent workflows without hiding meaningful provider differences.
Results depend on provider coverage, implementation scope, process adoption and data quality.
Reference architecture
Infrastructure providers
Provider Adapters
Ocosify Core Platform
Interfaces
Deployment editions
Organizations managing their own infrastructure
A central, self-hosted operations layer for internal IT, cloud and platform teams.
Hosting, data center and cloud service providers
Enterprise operations plus tenant-aware service delivery, customer self-service and commercial integration points.
Includes the applicable Enterprise Edition foundation
The correct edition depends on tenancy, customer-facing workflows, billing responsibilities and operational ownership.
Platform modules
Common resource inventory and provider-aware lifecycle operations.
Observe resource health, schedule work and support recovery planning.
Expose native, blueprint-deployed or registered services through a governed catalog.
Connect infrastructure operations to repeatable interfaces and workflows.
Define responsibility, permissions, usage visibility and administrative evidence.
Managed service model
Manage a service already offered by the provider directly through its supported API.
Where no suitable native service exists, deploy a defined service pattern on virtual machines or Kubernetes.
Register a running service in Ocosify inventory to provide centralized ownership and operational visibility without recreating it.
Not every operation applies to every service model. Availability must be shown per provider, service and release.
Backup, replication and synchronization
Multi Cloud Manager
Multi Cloud Manager is part of UIM and is not sold or positioned as an independent platform.
Connect one provider type or environment, such as one VMware, Proxmox, OpenStack or AWS connection, within the agreed license scope.
Connect two or more providers to create a cross-provider inventory, reporting and governance layer.
These capabilities require reliable provider coverage and mature operational safeguards. They are roadmap items, not currently promised outcomes.
Product roadmap
Create and manage real server resources through OpenStack, Proxmox and VMware integrations.
Manage real IP addresses, VLANs, firewall rules and load balancers.
Manage volumes, snapshots, object storage and automated backup workflows.
Deploy, back up and scale PostgreSQL, MySQL and Redis services.
Add authentication, multi-tenant structures, roles and permissions.
Add live metrics, logs, alerts and notification channels.
Measure real usage and support packages, payments and invoicing integrations.
Add API, CLI, Terraform provider, webhooks and scheduled tasks.
Add secret management, two-factor authentication and tamper-resistant audit records.
Build the backend API, database, job queue and real-time event system.
Expand integration and end-to-end tests, CI/CD, staging and error monitoring.
Where UIM fits
UIM FAQ
The integration direction includes VMware vSphere, Proxmox VE, OpenStack, major public clouds and additional providers. Each provider has an explicit planned, roadmap or custom-integration status; confirm current release support before evaluation.
Multi-data-center inventory and operations are part of the planned Enterprise Edition scope. The available operations depend on the connected providers and release.
The Service Provider Edition is designed for multi-tenant portals, self-service provisioning, quotas, catalogs and commercial integrations. Individual capabilities have separate availability states.
Multi Cloud Manager is a licensed UIM capability group rather than a separate product. A one-provider scope focuses on one connected provider, while the multi-cloud scope is intended for two or more providers and cross-provider visibility.
That is part of the product direction. A service may use a provider-native database, an Ocosify Blueprint or registration of an existing service. Database types and lifecycle operations must be confirmed by provider and release.
No. UIM is designed as a control and governance layer above those systems. The underlying provider remains responsible for its native virtualization or cloud capabilities.
Central discovery and inventory are planned to represent existing resources without recreating them. Import depth and supported metadata depend on the provider adapter.
No. Cross-provider disaster recovery is a roadmap direction, and recovery outcomes depend on workload design, data replication, provider behavior, testing and operational readiness.
Related products
Plan a unified operations layer