Beyond a self-service portal
Dorsa Enterprise Private Cloud adds service and operations management to cloud and data center infrastructure. It connects product definitions, request lifecycles, governance, provisioning, asset registration, monitoring and support in one operating model.
Product, consumer, project, order and service request definitions, with cost visibility.
Organizational quotas, policies, workflows, roles, approvals and audit.
Provisioning, CMDB, resource discovery, state reconciliation, alerts, changes and support.
The product's distinction is the traceable connection from Request → approval workflow → resource → asset → event → alert → change → incident rather than simply creating a resource from a form.
Six-layer logical architecture
Catalog · Request · Approval tasks · Assets · Actions
Product · Consumer · Project · Order · Cost visibility
Quota · Policy · Workflow · Roles and access · Audit
Service request · Automated provisioning · Asset registration · Change
Configuration Management Database (CMDB) · Resource discovery · State reconciliation · Warning · Incident · Issue
OpenStack · Kubernetes · KubeVirt · Ceph · VMware (optional; disabled by default) · Networking and security
The integration hub spans these layers, supporting REST APIs, webhooks, OAuth2, API keys, data mapping, retries, dead-letter queues (DLQ), correlation IDs and two-way synchronization.
Single sign-on (SSO), role-based access control (RBAC), organizational roles and separation of duties
REST APIs, webhooks, data mapping, retries, dead-letter queues (DLQ) and correlation IDs
Events, metrics, alerts, audit history and end-to-end tracing
Six boundaries that remain separate
What is delivered?
Defines resource types, inputs, constraints, costs, provisioning interfaces, lifecycle and required policies.
In what context is it delivered?
Defines the consumer, environment, owners, quotas, networking, business sensitivity, data classification and approver mappings.
Which deterministic decisions does the machine make?
Validates, constrains, enriches, labels, routes or rejects requests without human intervention.
Which human decisions are required?
Manages approver roles, stage order, parallel paths, rejection, return for correction, escalation and audit history.
What capacity is permitted?
Controls capacity at both consumer and project levels, with workflows for increasing or transferring quotas.
What has actually been delivered?
Registers provisioned resources in the CMDB with owners, projects, lifecycle, backup status, monitoring and links to requests.
The standard path from request to operation
The user selects the product and required operation.
Organizational and environment information is read from the project.
The form schema and product constraints are checked.
Costs are calculated for display to the user.
Consumer and project quotas are evaluated.
Deterministic security, eligibility and placement rules are applied.
A human approval path is built from the request context.
The appropriate provisioning executor and provider are selected and invoked.
The resource and its request relationship are registered in the CMDB.
Status, configuration drift, alerts, changes and support are tracked.
Organizational control without unnecessary interruption
The enterprise edition follows controlled continuation when no rule exists (Fail-Open). The absence of a rule alone must not stop delivery. Only an active rule that explicitly rejects or a final workflow rejection stops the process.
| Condition | Behavior | Result |
|---|---|---|
| No quota | No limit is applied | Continue |
| No active policy | The request continues without additional rules | Continue |
| No active workflow or stage | Approval not required is recorded, and provisioning begins | Provision service |
| Valid workflow | A role-based task is created and the request waits for a decision | Wait |
| Policy explicitly rejects | The request stops with a traceable reason | Stop |
| Final rejection | The service lifecycle stops and request and order states are synchronized | Reject |
A deterministic machine rule: allow, reject, warn, automatically amend a request or route it.
An accountable human decision: approve, reject, return for correction, escalate or delegate.
From asset registration to configuration drift control
Cloud assets and CMDB
- Automatic asset registration
- Owner and project
- Lifecycle status
- Links to requests and changes
Resource discovery and reconciliation
- Discover resources outside the platform
- Compare provider state with the CMDB
- Detect configuration drift
- Generate operational differences
Events, alerts and incidents
- Operational and business events
- Alert severity and instances
- Acknowledgment and resolution
- Convert alerts to issues
Change and support
- Change request
- Before and after state
- Execution and rollback results
- Issues, notes and escalation
From design to stable operations
The platform does more than provision resources. It covers design, delivery and operations with traceable responsibilities and outcomes.
Cloud and data center integration scope
Final integrations and provider coverage are defined during technical assessment. The architecture is designed to manage these resource groups.
OpenStack and compute resources
Virtual machine · Operating system image · Machine resource configuration · Storage volume · Snapshot · Backup · Network · Floating IP · Load balancer
Kubernetes
Cluster · Node · Namespace · Workload · Service · Ingress · Persistent Volume Claim (PVC) · Managed database · KubeVirt virtual machine
Ceph and storage
Cluster · OSD · RBD image (block storage) · RGW bucket (object storage) · Storage pool · Cluster health and maintenance
Data centers and integration
VMware (optional; disabled by default) · DNS provider · Physical server · Rack · Network device
Enterprise edition scope status
| Area | Product readiness status |
|---|---|
| Basic catalog and ordering | Ready to deliver |
| Governance, quotas and policies | Ready and extensible |
| Multi-stage workflows and approval tasks | Ready to deliver |
| Service request lifecycle | Ready; service coverage is extensible |
| Cloud assets and CMDB | Ready to deliver |
| Resource discovery and reconciliation | Operationally ready |
| Warning | In progress |
| Incident and issue mapping | Basic and extensible |
| Change request | Basic |
| Capacity and quota transfer | Basic |
| Unified audit foundation | Being completed and improved |
The exact operations, providers and integrations covered for each customer are recorded in the project's technical scope and delivery matrix.
Three levels of incremental maturity
Basic
- Enterprise portal
- Product catalog
- Requests and orders
- Basic automated provisioning
- Basic cloud assets
- Basic users, roles and audit
Enterprise operations
- Quotas and policies
- Workflows and approvals
- Service lifecycle
- Advanced CMDB
- Resource discovery and reconciliation
- Basic alerts, issues and changes
Enterprise cloud OSS/BSS
- Advanced capacity management
- Quota increases and transfers
- Advanced incident and change management
- Management reports
- Additional providers
- Custom policies and workflows
What is intentionally outside this edition's core scope?
Cost calculation supports visibility and management reporting but does not automatically create or change financial approvals. The platform does not rebuild a complete ITSM suite; it integrates with existing enterprise tools.
Turn your organization's real requirements into a technical matrix
The meeting's output can define provider coverage, modules, roles, integrations and deployment stages.