For organizations
Give distributed teams, classrooms, labs, and specialist users governed browser desktops on infrastructure your organization controls.
DaaS
Available on request
Cloud desktops for your workforce or customers.
WECORE Cloud deploys and operates secure virtual desktops on your OpenStack infrastructure, giving users browser access while your organization controls images, access, capacity, and data.
Full Linux desktop in a browser
Governed desktop pools
No inbound display ports
Runs on your OpenStack
The product view shows the desktop experience your authorized users receive after deployment.
Cloud desktop preview with sample data; the names, windows and states are illustrative only.
A managed desktop service for your organization
Provide cloud desktops to employees, students, researchers, or customers without building and operating a separate VDI stack.
For service providers
Add a managed desktop service to your catalog, with organization-specific images, access policies, resource pools, and service levels.
What your users can do
Open an assigned full graphical desktop in a modern browser, use organization-approved applications, and return to persistent files and settings when pool policy permits.
What your infrastructure team gets
Control image metadata, desktop pools, entitlement, persistence and reclaim policy, session limits, clipboard and display policy, capacity limits, and lifecycle operations.
How WECORE deploys and operates it
We integrate the service with your OpenStack, identity, network, and storage environment, validate the user journey, and provide the agreed ongoing operations.
Pool
Declared image, target, and policy
Browser
Full graphical session, no client
One sign-in
Gateway authentication and ownership check
Audited
Desktop and session lifecycle
Desktop access that is declared and governed.
Pools, entitlement, and browser sessions form one controlled service
1
Declared
Desktop pools
Your infrastructure team declares the image, network, security groups, target count, persistence class, and reclaim policy. The service converges the pool to that target.
Discuss pools →2
Entitled
Assignment by user or group
Grant a pool to named users or groups. On first login, an authorized user is bound safely to one ready desktop; everyone else is refused.
Discuss access →3
Browser-first
One authenticated front door
A full graphical Linux session opens in a modern browser after one sign-in. The desktop dials out to the gateway, so its display port is never opened inbound.
Discuss the user journey →What Cloud Desktop gives your organization
A browser desktop service with explicit pool, session, and lifecycle rules
Persistent or ephemeral by policy
Persistent desktops keep their data. An ephemeral pool can reset to its declared image only when an explicit reset policy is present.
Images classified by metadata
The catalog uses declared operating system, protocol, distribution family, and contract metadata rather than guessing from an image name.
Governed sessions
Sessions are time-bounded (each launch token is valid for 30 minutes) and centrally revocable by force sign-out. The user's desktop stays assigned, and a new session can be opened at any time. Clipboard direction, resolution, and color depth are enforced per pool.
Capacity boundaries
Each pool has a desktop cap and a ready-floor policy. Idle desktops may power off without dropping below the declared ready floor.
Sealed desktop credentials
Desktop login credentials are encrypted at rest and delivered privately to the guest, never through instance metadata or logs.
Controlled image rollout
Publish a new image version and replace pool desktops in bounded stages instead of changing every assigned desktop at once.
Service controls
From declared pool to governed browser session
The service connects pool policy, entitlement, assignment, access, and lifecycle on your OpenStack
Pool declaration
Define image metadata, network, security groups, target count, persistence, reclaim, and capacity policy.
Entitlement
Grant a pool to named users or groups; requests from anyone else are refused.
First-login assignment
Bind an entitled user safely to one ready desktop and return that assignment on reconnect.
Browser gateway
Authenticate once, authorize the desktop owner, and open the graphical session without an inbound display port.
Image contract
Classify supported images by declared capability metadata. Ubuntu-family images install the session components at first boot and require outbound internet then.
Lifecycle policy
Keep, stop, release, or delete a returned desktop according to the pool's persistence and reclaim rules.
Session policy
Enforce the session limit, force sign-out, clipboard direction, display resolution, and color depth on the server.
Audit and metering hooks
Record desktop and session lifecycle and emit desktop-hour and reserved-capacity signals for a downstream meter; rating and settlement are separate.
Choose the service for the user journey
Cloud Desktop is a governed pool; Cloud Server is an individually administered machine
| Product | Best for | Infrastructure | Access | Commercial model |
|---|---|---|---|---|
| Cloud Desktop Governed desktop pools |
Employees, students, researchers, classrooms, and contractors | Declared pools on your OpenStack | Full graphical session in a browser | Infrastructure engagement; metering hooks available |
| Cloud Server | General compute, web apps, burst workloads, databases | Governed VMs on your OpenStack infrastructure | Browser terminal or desktop; administrative access | Usage metering defined per deployment |
| Dedicated Cloud | Providers offering dedicated OpenStack and Ceph clouds | Dedicated infrastructure controlled by the provider | Service catalog and tenant controls | Defined for the engagement |
FAQ
Cloud Desktop questions, answered
The pool model, browser access, platform limits, and responsibility boundary
Cloud Desktop gives your users full desktops in the browser, served from pools your infrastructure team defines. Under the hood it is a browser-first desktop broker and pool control plane that WECORE deploys and operates on your OpenStack; your team defines pools, images, entitlement, session policy, and lifecycle rules.
A persistent desktop keeps its data between assignments and is the default. An ephemeral pool may reset a released desktop to its declared image only when the pool carries an explicit reset policy.
No. A full graphical Linux session opens in a modern browser. The desktop dials out to the gateway, so no display port is opened inbound.
No. The current display path is CPU-based and does not provide in-session GPU or 3D acceleration.
Desktops run on your OpenStack and connect through one authenticated gateway. The desktop's display port is not exposed inbound, requests are checked against ownership, login credentials are sealed, and desktop and session lifecycle is audited. Your organization can additionally require a second factor at connect time, per pool.
Cloud Desktop is delivered through an infrastructure deployment and operations engagement. The platform can emit desktop-hour and reserved-capacity metering signals; rating, settlement, and commercial terms are defined for the engagement.
Yes. The deployment engagement can include WECORE deploying and validating the underlying OpenStack environment on hardware you own or lease; if you already operate a compatible OpenStack, we integrate with it. Physical infrastructure is sourced separately.
Windows desktops connect over RDP through the same broker; your organization supplies the Windows Server and RDS/CAL licensing. The Windows path is defined and validated for each deployment.
WECORE deploys and operates the agreed broker and pool-control service. Your infrastructure team controls images, networks, pool targets, entitlement, persistence and reclaim policy, session rules, capacity limits, and the underlying OpenStack resources. WECORE monitors service health, coordinates upgrades, and works incidents within the responsibility split agreed for your deployment. Panel access is role-based, and administrative actions are recorded in tamper-evident audit records. Hardware and facility stay with the infrastructure owner unless included separately; the pricing page carries the full responsibility and access model.
Plan your desktop service
Define the pools, access, and operating model for your organization.
Review images, entitlement, session policy, capacity controls, and the OpenStack environment with our team. In the briefing, our team walks through the working service itself, from pool definition to a signed-in desktop session in the browser.