Skip to main content
OcosifyOpen Cloud Systems

Ocosify UIM

Planned

Unified Infrastructure ManagementManage complex infrastructure through one consistent control layer.

One 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

Connect the platforms that already run your infrastructure

The list communicates integration direction, not universal current support. Status is managed per provider and must be confirmed for the release used in an evaluation.

Virtualization and private cloud

Provider adapters for on-premises and hosted virtualization control planes.

Planned

VMware vSphere

virtualization

Planned

Proxmox VE

virtualization

Planned

OpenStack

private cloud

Roadmap

Microsoft Hyper-V

virtualization

Roadmap

XCP-ng

virtualization

Custom integration

KVM-based infrastructure

virtualization

Roadmap

Nutanix

private cloud

Roadmap

Apache CloudStack

private cloud

Public cloud

Provider adapters for public cloud accounts, subscriptions, projects and regions.

Planned

Amazon Web Services

public cloud

Planned

Microsoft Azure

public cloud

Planned

Google Cloud

public cloud

Roadmap

Huawei Cloud

public cloud

Roadmap

Oracle Cloud Infrastructure

public cloud

Roadmap

Alibaba Cloud

public cloud

Roadmap

DigitalOcean

public cloud

Roadmap

Hetzner Cloud

public cloud

Roadmap

Vultr

public cloud

Roadmap

Linode / Akamai Cloud

public cloud

Planned and roadmap entries are not commitments to a release date. Custom integrations require technical assessment.

From fragmentation to control

Replace console switching with a shared operational model

Operational fragmentation

Infrastructure teams lose time and context when each platform, location and account has a separate inventory and control surface.

  • Different management screens for different platforms
  • Fragmented inventory
  • Separate authorization systems
  • Manual capacity tracking
  • Independent management of multiple locations
  • Limited visibility between cloud and on-premises infrastructure
  • Vendor lock-in
  • Non-standard operating processes

The Ocosify approach

A provider-adapter layer and common resource model are intended to create consistent workflows without hiding meaningful provider differences.

  • Common provider-adapter layer
  • Unified resource model
  • Central inventory
  • Single management portal
  • Central roles and authorization
  • Shared workflow and job engine
  • Unified monitoring model
  • Cost and capacity visibility
  • Multi-cloud reporting

Expected operational outcomes

Results depend on provider coverage, implementation scope, process adoption and data quality.

  • Reduced operational complexity
  • Centralized visibility
  • Faster resource provisioning
  • More consistent operating processes
  • More informed capacity planning
  • Lower operational risk
  • Reduced dependence on a single vendor control plane
  • Stronger business continuity planning

Reference architecture

Adapters above providers, common services above adapters

The architecture separates provider-specific connections from shared inventory, workflows and user experiences.
  1. Infrastructure providers

    • VMware
    • Proxmox
    • OpenStack
    • Hyper-V
    • AWS
    • Azure
    • Google Cloud
    • Huawei Cloud
    • OCI
  2. Provider Adapters

    • Authentication
    • Resource mapping
    • Capability discovery
    • Operation translation
  3. Ocosify Core Platform

    • Inventory
    • Compute
    • Network
    • Storage
    • IAM
    • Monitoring
  4. Interfaces

    • Enterprise Portal
    • Service Provider Portal
    • API
    • CLI

Deployment editions

One platform direction for internal IT and service providers

Edition packaging and availability are confirmed during commercial evaluation. The comparison describes intended use and capability direction.

Self Hosted — Enterprise Edition

Organizations managing their own infrastructure

A central, self-hosted operations layer for internal IT, cloud and platform teams.

  • Central portal for internal IT teamsPlanned
  • Multi-data-center managementPlanned
  • Multi-provider supportPlanned
  • Central inventoryPlanned
  • Role-based access controlPlanned
  • Audit logsPlanned
  • MonitoringPlanned
  • Backup and disaster-recovery visibilityRoadmap
  • AutomationPlanned
  • Internal organizational usePlanned

Service Provider Edition

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

  • Multi-tenant architecturePlanned
  • Customer portalPlanned
  • Self-service resource provisioningPlanned
  • Tenant quotasPlanned
  • Usage meteringRoadmap
  • Billing integrationRoadmap
  • Product catalogPlanned
  • Packages and plansRoadmap
  • Reseller supportRoadmap
  • Customer-level reportingRoadmap
  • Tenant-level access isolationPlanned
  • White-label optionsRoadmap

The correct edition depends on tenancy, customer-facing workflows, billing responsibilities and operational ownership.

Platform modules

Organize infrastructure work around resources, operations and governance

Module entries describe intended product scope. Status labels indicate planned versus roadmap direction and should be displayed with every capability.

Infrastructure

Common resource inventory and provider-aware lifecycle operations.

  • Virtual MachinesPlanned
  • NetworksPlanned
  • FirewallsRoadmap
  • Security GroupsRoadmap
  • Public IPsPlanned
  • Private NetworksPlanned
  • VLANRoadmap
  • VPCRoadmap
  • VolumesPlanned
  • SnapshotsPlanned
  • ImagesPlanned
  • SSH KeysPlanned
  • Resource GroupsPlanned
  • Load BalancersRoadmap

Operations

Observe resource health, schedule work and support recovery planning.

  • MonitoringPlanned
  • MetricsPlanned
  • LogsRoadmap
  • AlertsRoadmap
  • Activity LogsPlanned
  • Audit LogsPlanned
  • BackupRoadmap
  • RestoreRoadmap
  • Disaster RecoveryRoadmap
  • Scheduled TasksPlanned

Managed Services

Expose native, blueprint-deployed or registered services through a governed catalog.

  • PostgreSQLPlanned
  • MySQLPlanned
  • RedisPlanned
  • Object StoragePlanned
  • Load BalancersPlanned
  • BackupPlanned
Extended service catalog
  • MariaDBRoadmap
  • MemcachedRoadmap
  • MongoDBRoadmap
  • OpenSearchRoadmap
  • RabbitMQRoadmap
  • KafkaRoadmap

Automation

Connect infrastructure operations to repeatable interfaces and workflows.

  • REST APIPlanned
  • CLIPlanned
  • Terraform ProviderRoadmap
  • WebhooksRoadmap
  • Scheduled TasksPlanned
  • Workflow AutomationRoadmap
  • TemplatesPlanned
  • Infrastructure BlueprintsRoadmap

Account and Governance

Define responsibility, permissions, usage visibility and administrative evidence.

  • Team & AccessPlanned
  • RolesPlanned
  • PermissionsPlanned
  • Usage & CostsRoadmap
  • BillingRoadmap
  • AuditPlanned
  • Account SettingsPlanned

Managed service model

Deliver services through the best available provider path

A service request can use a provider-native API, an Ocosify deployment blueprint or registration of an existing service. The supported path depends on provider capability, service type and product release.
Planned

Native Provider Service

Manage a service already offered by the provider directly through its supported API.

  • AWS RDS
  • Azure Database
  • Cloud-provider Redis service
  • Provider object storage
Roadmap

Ocosify Blueprint

Where no suitable native service exists, deploy a defined service pattern on virtual machines or Kubernetes.

  • PostgreSQL cluster
  • MySQL
  • Redis
  • RabbitMQ
  • OpenSearch
Roadmap

Existing Service Registration

Register a running service in Ocosify inventory to provide centralized ownership and operational visibility without recreating it.

  • Existing database cluster
  • Existing object-storage endpoint
  • Existing load-balancer service
Service Request
Native Cloud Service
Ocosify Blueprint
Existing Service
ProvisioningMonitoringBackupScalingAudit

Not every operation applies to every service model. Availability must be shown per provider, service and release.

Backup, replication and synchronization

Bring recovery posture into the same operational view

Resilience features are provider- and workload-dependent. Roadmap labels indicate direction only and must not be interpreted as current protection or a recovery guarantee.

Backup and recovery

  • VM backupRoadmap
  • Volume backupRoadmap
  • Database backupRoadmap
  • Snapshot policiesRoadmap
  • Retention policiesRoadmap
  • Incremental backupRoadmap
  • Scheduled backupRoadmap
  • Cross-location backupRoadmap
  • Backup health monitoringRoadmap
  • Restore testingRoadmap
  • Point-in-time recoveryRoadmap

Replication and disaster recovery

  • Cross-provider replicationRoadmap
  • Disaster-recovery plansRoadmap
  • Recovery point objective visibilityRoadmap
  • Recovery time objective visibilityRoadmap
  • Database replication visibilityRoadmap

Synchronization

  • File or object synchronizationRoadmap
  • Configuration synchronizationRoadmap
  • Image and template synchronizationRoadmap

Multi Cloud Manager

Activate multi-provider control as a licensed capability group

Multi Cloud Manager is not a separate product. It is a capability group intended to be licensed within either UIM edition. Packaging and release availability are confirmed during evaluation.

Multi Cloud Manager is part of UIM and is not sold or positioned as an independent platform.

1 Provider License

Connect one provider type or environment, such as one VMware, Proxmox, OpenStack or AWS connection, within the agreed license scope.

  • Single provider connectionPlanned
  • Basic inventoryPlanned
  • Compute managementPlanned
  • Network managementPlanned
  • Storage managementPlanned
  • Basic monitoringPlanned
  • Basic auditPlanned

Multi Cloud License

Connect two or more providers to create a cross-provider inventory, reporting and governance layer.

  • Two or more provider connectionsPlanned
  • Unified inventoryPlanned
  • Global resource searchPlanned
  • Cross-provider dashboardPlanned
  • Resource groupingPlanned
  • Central reportingPlanned
  • Unified cost analysisRoadmap
  • Global capacity visibilityRoadmap
  • Provider comparisonRoadmap

Advanced multi-cloud direction

These capabilities require reliable provider coverage and mature operational safeguards. They are roadmap items, not currently promised outcomes.

  • Policy-based placementRoadmap
  • Cost-based placementRoadmap
  • Location-based placementRoadmap
  • Capacity-based placementRoadmap
  • Provider-based automatic failoverRoadmap
  • Cross-provider disaster recoveryRoadmap
  • Cross-provider migration workflowsRoadmap
  • Global capacity optimizationRoadmap
  • Unified taggingRoadmap
  • Unified governance policiesRoadmap

Product roadmap

A phased path from inventory to end-to-end operations

The roadmap describes intended next phases and may change based on engineering validation, provider APIs and customer priorities. It does not represent committed dates or generally available functionality.

VM management

Planned

Create and manage real server resources through OpenStack, Proxmox and VMware integrations.

Network and security

Planned

Manage real IP addresses, VLANs, firewall rules and load balancers.

Storage

Planned

Manage volumes, snapshots, object storage and automated backup workflows.

Databases

Planned

Deploy, back up and scale PostgreSQL, MySQL and Redis services.

User management

Planned

Add authentication, multi-tenant structures, roles and permissions.

Monitoring

Planned

Add live metrics, logs, alerts and notification channels.

Billing

Roadmap

Measure real usage and support packages, payments and invoicing integrations.

Automation

Planned

Add API, CLI, Terraform provider, webhooks and scheduled tasks.

Security

Planned

Add secret management, two-factor authentication and tamper-resistant audit records.

Platform infrastructure

Planned

Build the backend API, database, job queue and real-time event system.

Quality

Planned

Expand integration and end-to-end tests, CI/CD, staging and error monitoring.

Where UIM fits

A shared control layer for internal platforms and service delivery

Hybrid enterprise inventory

Organize virtualization clusters, private cloud resources and public cloud accounts in one searchable model.

Multi-data-center operations

Coordinate resource ownership, capacity and operational workflows across locations.

Provider service catalog

Offer governed infrastructure and managed-service choices through repeatable fulfillment paths.

Customer self-service

Give service-provider tenants controlled access to quotas, catalogs and resource operations.

UIM FAQ

Questions about unified infrastructure management

What infrastructure platforms can Ocosify UIM connect to?

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.

Can it manage multiple data centers?

Multi-data-center inventory and operations are part of the planned Enterprise Edition scope. The available operations depend on the connected providers and release.

Is UIM suitable for service providers?

The Service Provider Edition is designed for multi-tenant portals, self-service provisioning, quotas, catalogs and commercial integrations. Individual capabilities have separate availability states.

How does the Multi Cloud License work?

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.

Can managed databases be offered through the platform?

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.

Does UIM replace VMware, Proxmox or OpenStack?

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.

Can existing infrastructure be imported?

Central discovery and inventory are planned to represent existing resources without recreating them. Import depth and supported metadata depend on the provider adapter.

Does cross-provider disaster recovery guarantee service continuity?

No. Cross-provider disaster recovery is a roadmap direction, and recovery outcomes depend on workload design, data replication, provider behavior, testing and operational readiness.

Plan a unified operations layer

Bring provider and location complexity into a clearer operating model.

Tell us which platforms, locations and workflows matter most. We will define a realistic UIM evaluation scope and confirm integration status.