Release ownership
Your team approves application versions and licenses. Confirm customer separation, embed behavior and branding before rollout.
Deliver your desktop application inside your product.
Use the session API to open streamed application sessions for your users. Your team manages application images and release groups. Neverinstall supplies the streaming and session layer.
Customers run whatever version they installed.
A desktop application runs on each customer’s machines, at the version they installed, on hardware and operating systems you do not control.
Tally Solutions
Read the Tally Solutions story- Users migrated
- 50,000
- Lower cost after moving from AWS NICE DCV to Neverinstall on OCI
- 60%
Connect your product to an application session.
Your product signs the user in and requests a session through the API. Neverinstall runs the session from your application image.
Your productYour brand · your users
Your desktop applicationStreamed inside your product
Session API
Your chosen cloudNeverinstall Cloud or your supported account
Image versions
User access
Sessions
- Application images
Versioned by your team and released by user group
- Session API
Create and manage sessions from your product
- Deployment
Neverinstall Cloud, your cloud account or your own servers with Neverinstall Private Cloud
- Pricing
Per user, per month. Infrastructure is quoted separately.
Versions and the stream, on screen.
Application versions
See the applications installed on a desktop, with each version and publisher. Check them after you roll out an updated image.
The stream
The browser client connects over WebTransport and falls back to WebSocket. Stream quality adapts to each user’s connection.
Agree on deployment and support responsibilities.
Delivery cost
Review session records alongside infrastructure costs. Use the pilot’s users and workload to evaluate your own delivery economics.
Test launch, return visits and image updates.
Integrate one application and a test user group before rollout.
- Package and connect
Build the application image with our engineers. Connect identity and session requests, and confirm embed and branding requirements.
- Use the complete session
Test sign-in, launch, reconnect and close from your product. Check customer separation and how errors reach your support team.
- Release and reconcile
Roll an updated image out to the test group. Check files and access, then reconcile session records with pilot users and cloud costs.
Installed application and streamed session.
| Installed by customers | Streamed session | |
|---|---|---|
| Getting started | Download, install and configure | Open it from your product in a browser |
| Version in use | Whatever each customer installed | The image version you released to their group |
| Where it runs | On each customer’s machines | In Neverinstall Cloud, your cloud account or your own servers |
Related
Questions from software vendors.
Do users install anything?
No. Application sessions open in a browser, embedded in your product.
Who updates the application image?
Your team manages application versions, licenses and release groups. Our engineers help build the first image during the pilot.
Where do sessions run?
In Neverinstall Cloud, your OCI, Google Cloud, Azure or AWS account, or your own servers with Neverinstall Private Cloud. The integration review sets capacity, image and support responsibilities.
Can we separate our customers?
The deployment separates customers’ users and sessions. Verify customer access, files and session permissions with test accounts during the pilot.
Can sessions carry our brand?
Yes. The session client shows your logo and colors inside your product. We agree on the branding and embed requirements before the pilot.
Plan your application delivery.
Tell us the application, deployment location and integration requirements. We will work through one customer session with your engineers.