Deep waters. Clear answers.
Browse the SensePC knowledge base for answers about setup, access, connection, performance, plans, billing, refunds, security, team access, and troubleshooting.
Jump to a topic
SensePC is a cloud desktop service that gives you a full computer experience over the internet. Instead of depending only on the hardware in front of you, your desktop runs in the cloud and can be accessed from supported devices with an internet connection.
A traditional PC depends on the physical hardware you own and use locally. SensePC runs your desktop in managed cloud infrastructure, so you can access your environment from different devices without being tied to one specific machine.
SensePC provides a full cloud desktop experience, not just a single application window. You connect to a complete desktop environment that is configured for your selected setup.
SensePC is built for individuals, remote professionals, developers, creators, gamers, small teams, and businesses that want flexible access to cloud desktops without relying on identical local hardware.
Yes. SensePC is designed for both personal and business use cases. Individual users can build and use their own cloud PC, while teams and organizations can manage access, assignments, and shared workflows under the right setup.
SensePC is suited for everyday computing, remote work, development, gaming, browser-based work, office tasks, and heavier workloads that benefit from stronger cloud resources. The best experience depends on choosing the right configuration for the job.
Yes. SensePC is designed to support users who need more compute power than their local device can easily provide. Heavier workloads should be matched with the right CPU, memory, storage, and other available configuration options.
SensePC is designed to support gamers and other performance-focused users. The experience depends on the configuration you choose, your connection quality, and the current client or access method available for your workflow.
No. One of the main benefits of SensePC is that it reduces your dependence on buying and upgrading expensive local hardware. Your desktop resources run in the cloud, while your local device is mainly used to access them.
SensePC can reduce how much you depend on your local computer, but your local device is still used as the access point. The cloud desktop does the heavy lifting, while your device is used to connect and interact with it.
No. Your SensePC runs in the cloud, so it is not dependent on your local laptop or desktop staying powered on in order to continue existing as a provisioned resource.
Yes. SensePC is designed so users can access their cloud desktop from supported devices instead of being locked to a single machine.
Yes. SensePC supports browser-based access, which allows users to connect to their cloud desktop without depending entirely on a heavy local setup.
For standard browser-based workflows, no additional local software may be required beyond a supported browser and a stable internet connection. Some advanced or future client experiences may have their own access methods.
You generally need a supported device, a modern browser or supported client path, and a stable internet connection. The local device does not need to provide all of the compute power that the cloud desktop itself is using.
Yes. SensePC is a cloud desktop service, so an internet connection is required to access and interact with your desktop.
Yes. SensePC is designed to make your desktop environment easier to access from different places, which is especially useful when traveling or switching between devices.
No. SensePC is designed for remote access. Your cloud desktop is not tied to one physical local machine in the same way a traditional PC is.
Depending on the available product options, users can choose things like operating system, compute profile, storage, location, and billing plan when building a SensePC.
Yes. SensePC supports operating system choices based on the configurations currently available on the platform.
Yes. SensePC setup can include location selection, which helps align the desktop with performance and deployment needs.
SensePC can give you access to stronger desktop resources without requiring the same upfront commitment to physical hardware purchases, upgrades, repairs, or device-specific limitations.
Not exactly. SensePC is intended to feel like a managed cloud desktop experience rather than a raw infrastructure service. It is built around user access, desktop usability, and workspace management.
No. SensePC is designed for both individual users and organizations. A solo user can use it for personal or professional work, while businesses can use it for team-based desktop access and management.
Yes. SensePC supports business and team-oriented workflows, including managed access and role-based usage depending on the workspace setup.
Yes. SensePC can support starting small and expanding later, which makes it useful for individual users, pilot rollouts, and growing teams.
Yes. SensePC is built so your desktop environment lives in cloud infrastructure rather than being limited to one local machine.
No. Your SensePC environment is designed to be associated with the cloud desktop itself, not permanently tied to one local endpoint device.
Sense Cloud is the storage side of the broader product experience, while SensePC is the cloud desktop side. They are related but not the same thing: SensePC focuses on desktop computing, and Sense Cloud focuses on cloud-based storage workflows.
Yes. Storage is part of the overall SensePC setup experience, and broader storage workflows may also involve Sense Cloud depending on how the account is used.
No. SensePC is intended to be straightforward enough for normal users while still being flexible enough for more advanced workflows.
Yes. SensePC is specifically useful for users whose local device does not offer enough power, consistency, or flexibility for the work they need to do.
The main benefit is that it gives users access to cloud desktop resources without forcing them to depend entirely on the limitations of a single local computer.
Yes. A core goal of SensePC is to make powerful desktop access more flexible, more portable across devices, and less dependent on local hardware constraints.
Yes. Depending on your setup, SensePC can support different kinds of workflows under the same broader account experience, including desktop and storage-related usage.
No. SensePC is not a shared computer. Every SensePC has its own dedicated resources and runs as an individual desktop environment.
Sense Cloud is the storage service in the broader SensePC product experience. It is designed to help users store, organize, preview, and manage files in the cloud alongside their desktop workflows.
SensePC is the cloud desktop service, while Sense Cloud is the cloud storage service. SensePC focuses on desktop computing, and Sense Cloud focuses on file storage, organization, sharing, and related storage workflows.
Yes. Sense Cloud is part of the broader SensePC experience and is designed to work alongside cloud desktop usage rather than as an unrelated product.
No. Sense Cloud is positioned as an integrated cloud storage experience, not just a simple attached drive. It is intended to support file organization, management, and access across the account experience.
Sense Cloud is designed for storing files, organizing folders, previewing supported content, sharing files, and managing storage usage inside your account.
Sense Cloud is intended to support common personal and work-related file storage needs, including documents, images, audio, video, and other standard file categories.
Yes. Sense Cloud includes category-based organization such as Documents, Images, Audio, and Video to make file browsing easier.
Yes. Sense Cloud is designed to support views such as Recent, Starred, and Shared so users can quickly find files based on activity and workflow.
Sense Cloud is built to support common cloud storage workflows, including uploading and organizing files. Folder and file management are part of the intended storage experience.
Yes. Sense Cloud is intended to support structured file organization so users can manage content in a way that fits their workflow.
Yes. Sense Cloud is designed to provide instant preview support for many common file types so users can review content without always downloading it first.
Yes. Sense Cloud supports file and folder sharing workflows so users can make content available to others when needed.
Yes. Sense Cloud is intended to support both file sharing and folder sharing as part of normal collaboration workflows.
Yes. Sense Cloud includes a Starred view so important files can be marked and found more easily later.
Yes. Sense Cloud includes a Recent view to help users return to files they accessed or worked with recently.
Yes. In team or shared account environments, users under the same account can use the broader Sense Cloud storage experience based on the workspace setup.
Yes. Users in the same account can share the same broader Sense Cloud storage environment depending on how the workspace is configured.
Yes. Sense Cloud supports collaboration-oriented storage workflows that are useful for teams and business environments.
Yes. Sense Cloud is designed to help users identify and clean up duplicate files so storage can be managed more efficiently.
Sense Cloud storage billing is separate from SensePC compute billing. Storage charges are based on the Sense Cloud billing model rather than the desktop compute plan.
Yes. Sense Cloud storage billing is distinct from SensePC desktop compute billing, even though both services are part of the broader product experience.
Sense Cloud storage billing is based on monthly usage rules. The final storage charge is tied to the highest usage tier reached during the billing period rather than only a single point-in-time snapshot.
Yes. Sense Cloud follows a billing model where monthly charges are based on the highest storage tier reached during the month.
Sense Cloud storage follows its own billing logic and is not positioned the same way as the Hourly, Daily, and Monthly desktop compute plans used for SensePC.
Managing and reducing stored content can help control future storage usage, but monthly billing is based on the highest usage tier reached during the billing cycle.
Yes. Sense Cloud is specifically designed to reduce dependence on the storage available on a single local device by keeping files in the cloud.
Yes. Sense Cloud is intended to make stored content easier to access across supported devices instead of tying your files to one local computer.
Yes. Sense Cloud can help users who need more flexible storage access without depending only on the available space on their local device.
Yes. Sense Cloud is designed to be useful for both individual users and teams that need organized cloud storage and sharing workflows.
Yes. Sense Cloud is intended to complement the SensePC desktop experience by giving users cloud-based storage alongside cloud-based computing.
The main benefit of Sense Cloud is that it gives users a cloud-based storage experience that supports organization, access, previews, and sharing without relying only on one local device.
Provisioning time depends on factors such as account readiness, wallet or billing setup, selected configuration, location, and whether the request is for an individual user or a team rollout. Some setups are straightforward, while larger or more customized deployments may take longer.
Provisioning usually includes account readiness, billing or wallet readiness, desktop configuration selection, location selection, operating system choice, storage selection, and preparation of the cloud desktop environment for the intended workload.
Before creating a SensePC, users should be ready with their preferred operating system, compute profile, storage size, location, and billing plan. Team environments should also decide user roles, ownership, and how desktops will be assigned.
Not necessarily. Individual users can usually start through the standard signup and build flow. Team and business deployments may require more planning around billing, user access, desktop assignment, and rollout structure.
Yes. SensePC supports starting with a single cloud desktop and expanding later, which is useful for individual users, pilot programs, and growing teams.
Yes. A pilot is often the best way to validate the selected configuration, user experience, access flow, and billing expectations before scaling to more users.
Yes. Provisioning is tied to your selected setup, including operating system, compute profile, storage, location, and billing plan based on the options available on the platform.
Yes. SensePC supports operating system selection during setup based on the configurations currently available on the platform.
Yes. Region selection is part of the provisioning flow and helps align the cloud desktop with performance, latency, and deployment preferences.
Yes. Billing or wallet readiness is an important part of the provisioning flow. Depending on the account state and selected plan, provisioning may depend on funding readiness or a valid payment setup.
A SensePC may remain in provisioning while the system completes account checks, billing readiness, infrastructure preparation, selected configuration setup, or location-specific resource preparation.
Provisioning is considered complete when the cloud desktop has finished preparing and is available for normal account use under the selected setup.
You can use it once provisioning has completed and the desktop is in a ready state. Immediate access depends on the account state, selected setup, and successful completion of the provisioning process.
Yes. Team rollouts usually require additional planning for billing ownership, workspace setup, user roles, assignment flow, and the number of desktops needed.
Yes. Teams should decide who will be the owner, who will have admin access, and how desktops will be assigned before inviting users into the workspace.
Yes. For team environments, billing setup is best completed early so desktop provisioning, wallet usage, and future account activity stay centralized for the organization.
Yes. Storage selection is part of the broader setup experience, and users should choose the storage size that fits their intended workload and billing expectations.
Yes. Individual provisioning is usually simpler, while team provisioning may involve extra decisions around billing, assignments, access control, and rollout planning.
First review your billing or wallet readiness, selected configuration, and account status. If the desktop does not move to a ready state after a reasonable period, contact support with your account and desktop details.
SensePC is designed to be accessed from modern laptops, desktops, and similar devices with a supported browser or supported access method and a reliable internet connection.
Usually no. Because the main desktop workload runs in the cloud, your local device typically does not need to provide the same level of compute power as the cloud desktop itself.
In many cases, yes. SensePC is useful for users whose local device is limited, as long as the device can handle the access method, display the session properly, and maintain a stable connection.
Yes. Browser-based access is part of the SensePC experience, which allows many users to connect without depending entirely on high-end local hardware.
For standard browser-based workflows, not necessarily. Many users can access SensePC through a modern browser, while some advanced workflows or future client experiences may use additional access methods.
Yes. SensePC is designed so users can access their cloud desktop from more than one supported device instead of being locked to a single local machine.
Yes. Your SensePC environment is associated with the cloud desktop, not permanently tied to one physical local device.
Yes. SensePC is intended to support access from different locations as long as you have a supported device, internet connectivity, and the right account access.
No. Your SensePC runs in the cloud, so it does not depend on your local computer staying powered on in order to continue existing as a provisioned resource.
Not necessarily. Since the desktop runs in the cloud, your local device does not need to store everything the way a traditional standalone PC would.
The most important factors are a supported access method, a stable internet connection, and a device that can comfortably display and interact with the remote desktop session.
Yes, but usually less than with a traditional PC. The cloud desktop handles the main workload, while your local device and network still affect things like responsiveness, display smoothness, and session comfort.
Yes. SensePC is designed to make your desktop environment available away from your main computer, which is useful when traveling or switching between locations.
Yes. As long as the device is supported and your account access is valid, SensePC can be used from different devices that fit your workflow.
No. One of the benefits of SensePC is that teams do not need identical local hardware in order to access a more standardized cloud desktop environment.
Yes. SensePC is particularly useful for users who need access to stronger desktop resources without depending entirely on the limitations of their current local device.
Yes. SensePC is designed to reduce the need for immediate local hardware upgrades by moving the main desktop resources into the cloud.
No. SensePC is not designed to be permanently locked to one local endpoint in the way a traditional physical computer is.
No. Many users can get started without the latest hardware, provided their device can support the connection method and maintain a usable session experience.
Yes. A major benefit of SensePC is that your desktop environment lives in the cloud, which makes it easier to access the same environment across supported devices.
Depending on the currently available options, users can choose items such as operating system, compute profile, storage, location, and billing plan when building a SensePC.
Yes. SensePC supports operating system choices based on the configurations currently offered on the platform.
Yes. Choosing a location closer to the end user usually helps improve responsiveness, especially for interactive workloads.
Yes, depending on the selected configuration. Workloads with heavier CPU, memory, graphics, or low-latency requirements should be matched to the right desktop profile.
Yes. SensePC configuration includes compute-related choices based on the options currently available on the platform.
Yes. Storage selection is part of the broader SensePC setup experience, and users should choose the size that fits their workload and billing expectations.
Yes. The selected location can affect latency and responsiveness, especially for interactive or performance-sensitive workloads.
Yes. The selected configuration should match the workload you expect to run so the desktop has the right level of CPU, memory, storage, and performance characteristics.
Yes. SensePC configurations are designed to support a range of workloads, from lighter day-to-day tasks to heavier professional or performance-oriented use cases, depending on the available options.
No. Different configurations are better suited for different workloads, so users should choose a setup that matches their expected performance and resource needs.
Yes. The operating system you choose affects the software environment and should match the tools, applications, and workflow you plan to use.
Yes. Users should choose a SensePC configuration based on the workload and performance they need, not only on the listed price.
SensePC offers Hourly, Daily, and Monthly plans. Public pricing is listed by plan across SensePC configurations and locations.
Hourly is best for flexible or on-demand usage, has no uptime limit, and is the only plan that supports on-demand CPU and memory resize. Daily is designed for regular day-based usage and supports up to 10 hours of total uptime per day. Monthly is designed for steady long-duration workloads and supports up to 180 hours of total uptime during the monthly cycle.
All SensePC plan charges are applied upfront at the beginning of the applicable billing cycle or billing unit.
The pricing page lists SensePC prices by PC configuration and location, with separate Hourly, Daily, and Monthly price columns for each listed setup.
No. The pricing page is a public pricing reference. For the most accurate final amount, users should check the live cost calculator, the pricing shown during PC creation, and their billing dashboard usage records.
Yes. Plan changes are supported. Upgrades apply immediately, while supported downgrades are scheduled immediately and take effect after the current billing cycle ends.
Yes. Users can upgrade from Hourly to Daily or Monthly, and the upgrade applies immediately.
Yes. Users can upgrade from Daily to Monthly, and the upgrade applies immediately.
Yes. Users can request a downgrade from Monthly to Daily or Hourly. The downgrade is scheduled immediately, but it takes effect only after the current billing cycle ends.
Yes. Users can request a downgrade from Daily to Hourly. The downgrade is scheduled immediately, but it takes effect only after the current billing cycle ends.
Upgrades apply immediately. Supported downgrades are scheduled immediately and take effect after the current billing cycle ends.
No. Users cannot cancel a plan directly. If a lower plan is needed, a supported downgrade can be scheduled and will take effect after the current billing cycle ends.
Resize support depends on the active plan. Only the Hourly plan supports on-demand CPU and memory resize after the SensePC is created.
Only the Hourly plan supports increasing or decreasing CPU and memory on demand.
No. On-demand CPU and memory resize is supported only on the Hourly plan.
Yes. Disk size can be increased after creation where supported by the active workflow.
No. Disk size reduction is not supported.
No. The Hourly plan does not have a total uptime limit.
The Hourly plan does not have a maximum total uptime limit.
The Daily plan supports up to 10 hours of total uptime per day.
The Monthly plan supports up to 180 hours of total uptime during the monthly billing cycle.
Yes. The Daily plan supports up to 10 hours of total uptime per day.
Yes. The Monthly plan supports up to 180 hours of total uptime during the monthly billing cycle.
Stopping a SensePC ends the active running session, but it does not automatically stop every possible charge. The billing effect depends on the active plan and any storage resources that remain allocated.
If your SensePC is on the Hourly plan, SSD storage charges continue even after stopping the SensePC because the disk remains allocated to preserve your data.
Yes. If your SensePC is on the Hourly plan, SSD storage charges continue after the SensePC is stopped because the disk remains allocated to preserve your data.
No. Billing behavior depends on the active plan. Stopping a SensePC does not have the same billing effect under every plan.
No. Stopping a SensePC is not the same as deleting it. Your environment, settings, and stored data remain available unless the resource is explicitly deleted or removed according to platform rules.
No. Sense Cloud does not use the same Hourly, Daily, and Monthly desktop plan structure. Sense Cloud is billed monthly based on the storage usage tier reached during the billing period.
No. Creating a SensePC template is a paid feature, and users are charged daily for that template.
Hourly is best for short sessions or variable usage and does not have a total uptime limit.
Daily is best for regular day-based usage and supports up to 10 hours of total uptime per day.
Monthly is best for steady long-duration workloads and supports up to 180 hours of total uptime during the monthly cycle.
When your Daily plan reaches the 10-hour usage limit, your SensePC will be stopped. You can start it again after the next daily billing cycle begins.
When your Monthly plan reaches the 180-hour usage limit, your SensePC will be stopped. You can start it again after the next monthly billing cycle begins.
Yes. Auto-renew is enabled by default for Daily and Monthly plans, but you can disable it later at any time.
Yes. You can turn off auto-renew for your SensePC plan at any time.
Once your SensePC is ready and in the correct state, you can launch it from the dashboard using the available PC connect option for your account and workflow.
Performance Mode is a PC connect option that lets you switch from the browser viewer to the NICE DCV native client for a smoother, lower-latency, and more responsive desktop experience.
Once your SensePC session is open in the browser viewer, you can find Performance Mode in the control panel on the right side of the screen.
First connect to your running SensePC in the browser viewer. Then open the control panel on the right side of the screen, select Performance Mode, review the confirmation dialog, and continue to launch the NICE DCV native client.
Yes. The current handoff flow starts from the active browser viewer session and then switches to the NICE DCV native client.
Yes. Performance Mode requires the NICE DCV desktop app to be installed on your computer.
No. Performance Mode switches the session from the browser viewer to the NICE DCV native client, so the desktop app must be installed.
A confirmation dialog appears first. After you confirm, SensePC attempts to open the NICE DCV native client using your current active session. If the handoff appears successful, the browser viewer disconnects. If not, the browser session stays active and fallback options are shown.
The confirmation step makes the switch intentional and explains what will happen next, including browser disconnect behavior, fallback safety, and how to reconnect later if the native client closes unexpectedly.
No. The browser session is not disconnected first. SensePC keeps the browser session active unless the native handoff appears successful.
If the native client does not open, the Performance Mode switch does not complete. Your browser session should stay active, and SensePC should show fallback options instead of ending your current browser session.
This is designed to protect fallback safety. The current handoff flow uses the active browser session first, so users do not lose access if the native client is missing or the auto-launch fails.
If auto-launch does not appear to work, SensePC can show fallback options such as NICE DCV download guidance and a .dcv connection file that you can open manually.
Yes. SensePC supports a .dcv connection file fallback so you can download the connection file and open it manually in the NICE DCV desktop app.
The .dcv connection file is a fallback option that lets you manually open the current session in the NICE DCV native client if the direct application launch does not succeed.
Allow the application launch so the NICE DCV native client can open and complete the handoff.
Install the NICE DCV desktop app for your operating system and system type, then return to your SensePC session and try Performance Mode again.
Yes. After the native client opens successfully and the handoff is completed, you can close the browser tab if you no longer need it.
After the native client opens successfully, your session moves from the browser viewer into the NICE DCV native client and the browser viewer disconnects.
No. The current handoff uses the existing active session for the browser-to-native switch rather than forcing a brand-new session during this flow.
Go back to your SensePC dashboard, locate the same running cloud PC, click Connect to reopen the browser session, and then use Performance Mode again to relaunch the NICE DCV native client.
Yes. If the native client is interrupted, closed by mistake, or loses connection, you can return to the dashboard, reconnect in the browser, and launch Performance Mode again.
No. The backend implementation supports both Windows and Linux for this handoff flow.
No. NICE DCV Client is a third-party application provided by Amazon Web Services.
You can connect once your SensePC has finished provisioning and is in a ready or running state that supports an active session.
The Connect button may be unavailable if the SensePC is still provisioning, stopped, starting, not yet ready, not assigned correctly, or otherwise not in a state that allows an active session.
Yes. In browser-based workflows, you may need to allow pop-ups or redirects so the remote desktop session can open correctly.
First check whether pop-ups or redirects are blocked, confirm the SensePC is running, refresh the dashboard, and verify that your browser session is still active. If the issue continues, open a support ticket with the SensePC name and account details.
Closing the browser usually ends your local view of the session, but it does not automatically delete, reset, or stop the SensePC. You can usually reconnect if the SensePC is still running and your account still has access.
No. Closing the browser does not automatically stop the SensePC. It usually only closes your local view of the session.
Yes. In many cases you can reconnect if the SensePC is still running, your session is still valid, and your account has access to the desktop.
Yes. SensePC supports browser-based access for supported workflows.
For standard browser-based access, not necessarily. Many users can connect through a supported browser. However, some PC connect options, such as Performance Mode, require the AWS DCV desktop app.
Performance Mode is a PC connect option designed for users who want the best possible remote desktop performance experience.
Performance Mode is available from the SensePC control panel on the right side of the screen during a session.
Yes. Performance Mode requires the AWS DCV desktop app to be installed.
No. Performance Mode requires the AWS DCV desktop app.
Performance Mode is the best PC connect option for users who want lower latency and higher maximum FPS, especially for more interactive or performance-sensitive workloads.
Yes. SensePC is designed so users can access the same cloud desktop from supported devices instead of being tied to one local machine.
You generally need a supported device, a supported browser or PC connect option, a stable internet connection, a ready or running SensePC, and valid account access.
Disconnecting closes your current session but does not turn off the SensePC. Stopping turns off the SensePC until you start it again. Rebooting restarts the SensePC. Deleting permanently removes the SensePC.
For most work, browser access is enough. For the best gaming and performance-focused experience, users should use the AWS DCV desktop app.
No. NICE DCV Client is a third-party application provided by Amazon Web Services.
No. NICE DCV Client is a third-party application, and SensePC does not manage its software updates, patches, or security lifecycle.
Your SensePC can start and stop automatically based on the schedule you set.
Idle timeout is a setting that automatically stops your SensePC after it has been connected but inactive for the configured amount of time.
SensePC performance is mainly affected by location choice, network quality, connection stability, local device responsiveness, workload type, and the desktop configuration you choose. Interactive workloads are usually more sensitive to latency than basic office tasks.
Responsiveness is usually shaped by network quality, distance to the selected location, workload sensitivity, and whether the desktop configuration is a good fit for the applications being used.
Latency depends on how far the user is from the selected location, the quality of the local internet connection, routing conditions, and the type of workload. Users who choose a location closer to them generally experience better responsiveness, especially for interactive tasks.
Yes. Choosing a location closer to the user can help reduce latency and improve responsiveness, especially for interactive workflows such as remote desktop use, development, design work, and performance-sensitive sessions.
No. Different workloads place different demands on CPU, memory, graphics, storage, and network responsiveness, so the experience will vary depending on the application and the selected desktop configuration.
Yes, when the selected configuration matches the workload. Heavier applications may require more compute, more memory, stronger graphics capability, or a location with better responsiveness for the user.
Yes. Performance-heavy and graphics-intensive workloads can be supported when the desktop configuration is chosen appropriately and the user has a stable, low-latency connection.
Yes. SensePC is suitable for users who need strong interactive performance. For the best experience, users should choose the right configuration, select the closest practical location, maintain a stable connection, and use the best PC connect option for their workload.
Performance Mode is a PC connect option designed to provide the best performance experience in terms of lower latency and higher maximum FPS.
For the best performance experience, users should choose the right configuration, select the best location for their use, maintain a stable connection, and use Performance Mode with the AWS DCV desktop app.
Yes. Performance Mode is designed to provide the best performance in terms of lower latency and higher maximum FPS.
Users who want the best possible performance, especially for more interactive or performance-sensitive workloads, should use Performance Mode with the AWS DCV desktop app because it is designed for lower latency and higher maximum FPS.
Browser-based access can deliver a strong experience for many workflows, but performance still depends on the browser environment, device responsiveness, and network conditions. Users who want the best performance in terms of latency and maximum FPS should use Performance Mode with the AWS DCV desktop app.
The cloud desktop does the main computing work, but your local experience still depends on how quickly your device can send input and receive the live desktop stream. That means internet quality and stability still play a major role in perceived performance.
Yes. Even though the main workload runs in the cloud, your local device still affects the session experience through display handling, browser or app responsiveness, and overall interaction smoothness.
Not necessarily. Even with the same desktop configuration, user experience can vary based on location, internet quality, local device condition, and workload sensitivity.
Two users can have different experiences because of differences in distance to the selected location, internet stability, local network conditions, local device responsiveness, and the applications they are running.
Yes. Choosing the right desktop configuration is one of the biggest performance factors. A configuration that is too small for the workload may feel slower even if the network connection is good.
Yes. If the selected CPU, memory, graphics capability, or storage setup does not match the workload, the desktop may feel slower or less responsive than expected.
No. Strong compute resources help, but overall performance also depends on network quality, location choice, workload sensitivity, graphics needs, and how the session is being accessed from the local device.
Yes. A stable connection is extremely important for cloud desktop responsiveness. Fast internet is helpful, but instability, packet loss, or frequent connection changes can still hurt the session experience.
Yes. Local Wi-Fi quality can affect the session experience, especially if the connection is unstable, congested, or inconsistent.
First check your local internet stability, confirm you selected a suitable location, review whether your desktop configuration matches the workload, and close unnecessary local browser tabs or apps. If the issue continues, open a support ticket with the workload details.
If your applications regularly feel slow, take too long to open, struggle during heavier tasks, or become less responsive under load, the selected configuration may not be the best fit for your workload.
A stable, low-latency internet connection generally provides the best experience. Consistency is especially important for interactive workloads that are sensitive to input delay or screen update lag.
In many cases, yes. Being physically closer to the selected location can reduce latency and improve responsiveness for interactive use.
Yes. Standard office and productivity workloads are generally less sensitive to latency than highly interactive tasks, so many users can get a strong experience with the right setup.
Yes. SensePC can support development and technical workflows, especially when users choose a configuration that matches their tools, workload size, and responsiveness needs.
Start by reviewing the selected location, the cloud desktop configuration, the local device condition, browser or access method, and the quality of the current network connection.
Yes. Improving location choice or moving to a better-fitting configuration can significantly improve the user experience when the original setup is not aligned with the workload or location.
Interactive tasks depend more heavily on immediate input response and rapid screen updates, so latency and connection stability are more noticeable than they are in lighter, less time-sensitive workflows.
A common mistake is assuming performance depends only on cloud compute size. In practice, location choice, connection quality, workload fit, and the local access experience also matter a great deal.
Performance Mode is designed to improve responsiveness by giving users a smoother experience, lower latency, and higher maximum FPS than standard browser-only use.
Users who want the best possible performance, especially for more interactive or performance-sensitive workflows, should use Performance Mode because it is designed for lower latency, smoother control, and higher maximum FPS.
Yes. Performance Mode is designed to provide the best performance experience in terms of lower latency and higher maximum FPS.
Performance Mode is especially useful for gamers, developers, designers, engineers, creative professionals, and other power users who want faster input response, smoother motion, and a more desktop-like experience.
You may want to use Performance Mode when you want better responsiveness for gaming, more fluid interaction for demanding applications, lower-latency control, or a more stable experience during longer sessions.
Yes. Performance Mode is one of the strongest options for gaming because it is designed to provide lower latency, smoother control, and higher maximum FPS.
Yes. Performance Mode is beneficial for developers, designers, engineers, creative professionals, and other users who want more responsive control and smoother session behavior.
Yes. Browser access can still work well for many workflows, but users who want the best available performance should use Performance Mode with the NICE DCV desktop app.
For the best overall experience, choose the right desktop configuration, choose the best location for the user, maintain a stable low-latency connection, and use Performance Mode with the NICE DCV desktop app.
No. Performance Mode improves the connection experience, but users still need a stable network and a suitable location choice for the best results.
No. Browser-based native app launch detection is best-effort, so SensePC uses fallback logic and keeps the browser session alive if the handoff does not appear to succeed.
Yes. Performance Mode uses the NICE DCV Client, which is a third-party application provided by Amazon Web Services.
SensePC billing is based on the selected desktop billing plan. SensePC offers Hourly, Daily, and Monthly plans, while Sense Cloud storage follows its own monthly usage-tier billing model.
All SensePC charges are applied upfront at the beginning of the applicable billing cycle or billing unit.
No. Sense Cloud does not use the same Hourly, Daily, and Monthly desktop plan structure. Sense Cloud is billed monthly based on the storage usage tier reached during the billing period.
SensePC accepts payment from most international credit and debit cards.
No. PayPal is not supported as a payment method.
No. Gift cards are not supported as a payment method.
The minimum wallet recharge amount is $20.
Users need billing readiness before using paid SensePC services. Wallet funding is part of that process for desktop usage, storage usage, and other paid features.
Yes. SensePC supports quick recharge so users can add funds to their wallet more easily.
Yes. Users can enable or disable auto-recharge for their wallet.
Yes. Users can enable or disable auto-recharge from billing and payment settings.
If auto-recharge repeatedly fails because a bank declines the payment, auto-recharge may be disabled automatically after multiple failed attempts.
Yes. Users can add multiple cards in Manage Payment Method.
Yes. Users can change which saved card is set as the default payment method.
If only one card is saved on the account, that card remains the default payment method.
No, not if auto plan renew is enabled. When auto plan renew is active, the last saved card must remain on file.
If auto plan renew is enabled, the last saved card must remain on file so renewal-related billing can continue correctly.
Yes. SensePC supports centralized billing workflows so teams can manage wallet funding, payment methods, and billing activity from one account experience.
Users can review charges in the billing page under Wallet Recharge and Billing History.
Wallet recharge history is available in the billing page under Wallet Recharge and Billing History.
Billing history is available in the billing page under Wallet Recharge and Billing History.
Yes. Users can review promotion and cashback information in the billing page.
Yes. Users can review wallet monthly spending in the billing page.
Yes. SensePC desktop billing and Sense Cloud storage billing follow different charging models, even though both are visible within the broader billing experience.
SensePC uses a wallet-based payment model. Users add funds to their wallet, and charges are applied based on the active SensePC plan, storage usage, and other paid features.
Billing readiness is part of the setup process. Depending on the workflow and account state, users may need wallet funding or a valid payment method before starting paid usage.
Yes. Auto-recharge can be enabled to help prevent service interruption by automatically adding funds when your wallet balance reaches the configured threshold.
Yes. Auto-recharge may be turned off automatically after multiple failed payment attempts caused by card declines.
Users can review charges, wallet recharges, and billing activity in the billing page under Wallet Recharge and Billing History.
Wallet recharge history is available in the billing page under Wallet Recharge and Billing History.
Users can review promotion and cashback information in the billing page.
Yes. SensePC supports centralized billing workflows so teams can manage wallet funding, payment methods, and billing visibility from one broader account experience.
No. A user can receive the signup promo only once. Creating multiple accounts does not make the user eligible to receive the signup promo again.
The signup promo balance amount may vary. It is intended to cover a limited amount of free SensePC usage.
No. Promo balance and cashback balance cannot be withdrawn, transferred, or redeemed as real money.
No. Promo balance and cashback balance are not eligible for refund.
Promo balance and cashback balance are automatically applied toward eligible SensePC and Sense Cloud usage.
Cashback balance is a promotional service credit earned from qualifying activity. It can only be used for eligible service usage and cannot be withdrawn or redeemed as real money.
Promotional balances include any signup promo credits, promotional credits, and cashback credits that have been added to the account.
Refunds are only considered in limited cases after investigation. A refund may be reviewed only if the issue was caused by improper billing by SensePC, a SensePC billing or platform error, or infrastructure downtime caused by the cloud resource provider.
A refund may be considered only if the issue was caused by improper billing by SensePC, a SensePC billing or platform error, or infrastructure downtime caused by the cloud resource provider.
To request a refund, submit a support ticket with the relevant billing and account details. The billing team will investigate the request before any refund decision is made.
No. Refunds are not automatic. Every refund request is reviewed through a support ticket and investigated by the billing team.
Refund requests are reviewed by the billing team after the user opens a support ticket.
No. Charges are not refundable in general. A refund is only considered in limited cases where the issue is caused by improper billing by SensePC, a SensePC error, or infrastructure downtime caused by the cloud resource provider.
Open a support ticket with your account details, the charge in question, the billing plan involved, and the approximate date of the charge so the billing team can investigate.
No. Plan changes or other account actions do not automatically create a refund. Refunds are only considered in limited cases after billing team investigation.
Yes. If a refund is approved, a transaction charge may be deducted from the refund amount, so the final refunded amount may be lower than the original charge.
No. Opening a support ticket starts the review process, but refund approval depends on the billing team’s investigation and findings.
Support can help collect the request and billing details, but refund approval depends on billing team investigation rather than immediate automatic approval.
Include your account details, the charge you are questioning, the billing plan involved, the approximate date of the charge, and a short explanation of the issue so the billing team can investigate properly.
Traffic between users and SensePC or Sense Cloud is encrypted in transit to help protect desktop access, storage activity, and account interactions.
Yes. Traffic between the user and SensePC is encrypted in transit.
Yes. Traffic between the user and Sense Cloud is encrypted in transit.
Yes. Each SensePC runs in its own isolated environment to help separate one user's desktop from another.
No. SensePC desktops are designed to run in isolated environments so one PC cannot directly talk to another user's PC as part of normal platform operation.
SensePC takes both user security and infrastructure security seriously. The platform is designed with security-focused controls around encrypted traffic, desktop isolation, account protection, and payment handling.
SensePC applies security-focused controls around account access, encrypted traffic, isolated desktop environments, and infrastructure protection. Payment data is handled through Stripe rather than being stored directly in SensePC systems.
No. SensePC does not store full user card information in its own infrastructure.
Payment method handling and transaction processing are managed by Stripe.
No. Payment card handling is managed by Stripe, so full card details do not pass through or stay stored in SensePC infrastructure.
Payments are handled through Stripe, which processes transactions using strong encryption. SensePC does not store full card information directly in its own systems.
Yes. SensePC may collect browser and related session information for security hardening and platform protection purposes.
Yes. SensePC may collect information such as IP address and location-related browser data to support security hardening, account protection, and infrastructure security monitoring.
SensePC collects browser and related connection information to strengthen platform security, help detect suspicious activity, and improve account and infrastructure protection.
Users should review the public Security page, Privacy Policy, and Terms of Service for the latest platform security, privacy, and usage information.
Yes. SensePC supports role-based team workflows so organizations can manage access more deliberately across owners, admins, and other users based on the workspace setup.
Organizations with stricter compliance or governance requirements should review the Security page, Privacy Policy, Terms of Service, and their own internal review standards before rollout.
Users should review the Terms of Service on the SensePC website for the current rules, account terms, service usage conditions, and related policies.
Users should review the Privacy Policy on the SensePC website for details about what information is collected, how it is used, and how privacy-related practices are handled.
No. SensePC does not store full payment card information in its own systems. Payment information is handled through Stripe.
SensePC may collect browser information, IP address, and location-related session data to strengthen security, protect accounts, and support platform hardening.
This information helps improve security, detect suspicious activity, strengthen infrastructure protection, and support safer account access.
Transactions are processed through Stripe.
Yes. Transactions handled through Stripe are protected with strong encryption as part of the payment processing flow.
Yes. SensePC supports MFA for login. Users can enable MFA using an authenticator app or email verification.
No. NICE DCV Client is a third-party application provided by Amazon Web Services. SensePC does not manage its updates, patches, or security lifecycle, so users should use it according to their own IT and security requirements.
Start by checking your internet stability, local Wi-Fi or network quality, selected location, and whether your current desktop configuration matches the workload. Interactive workloads are especially sensitive to latency and connection stability.
Check your network stability, selected location, browser or access method, and whether the workload is heavier than your current SensePC configuration is designed to handle.
Even though the desktop runs in the cloud, your session experience still depends on internet stability, distance to the selected location, local device responsiveness, and workload sensitivity.
First confirm that your account is signed in correctly, the desktop is in a ready or running state, your browser or device is supported, and your internet connection is stable. If access still fails, open a support ticket with the relevant account and desktop details.
The Connect button may be unavailable if the desktop is still provisioning, stopped, starting, not yet ready, or otherwise not in a state that allows an active session.
Refresh the dashboard, confirm the desktop is in the correct state, make sure your browser session is still active, and verify that pop-ups or redirects are not being blocked.
Check whether your browser is blocking pop-ups or redirects, confirm the desktop is running, and try launching the session again from the dashboard.
Yes. Browser-based remote desktop access may require pop-ups or redirects to open correctly, so blocked pop-ups can prevent the session window from opening.
Review your billing or wallet readiness, selected configuration, and account state first. If the desktop remains stuck in provisioning after a reasonable period, contact support with your desktop and account details.
A desktop can remain in provisioning while the system completes account checks, billing readiness, location preparation, configuration setup, and desktop environment preparation.
Check your billing or wallet readiness, confirm the desktop is not still provisioning, refresh the dashboard, and verify that the selected plan and account state are valid for continued use.
Review the current billing plan, any usage limits, and whether the desktop was stopped manually, by policy, or after reaching a plan-related condition. Then check the dashboard for the current state before trying again.
Performance can vary by location because distance to the selected location, local network quality, and connection routing conditions all affect responsiveness.
If performance is not meeting expectations and the selected location is far from the user, review whether a closer location would provide better responsiveness for the workload.
Review whether the selected configuration has enough compute, memory, storage, and other resources for the applications you are using. A mismatch between workload and desktop profile is a common cause of poor performance.
Yes. Unstable or congested Wi-Fi can reduce responsiveness, interrupt the session experience, or make remote desktop access feel inconsistent.
Yes. Even though the desktop runs in the cloud, the local browser, device responsiveness, and session environment still affect the overall access experience.
Review your billing page, wallet balance, payment method setup, and whether auto-recharge or card status needs attention. Billing readiness can affect provisioning and continued usage.
Check whether the saved card was declined by the bank, review your default payment method, and confirm that a valid card remains available for future billing activity.
If auto plan renew is enabled, the last saved card must remain on file so renewal-related billing can continue correctly.
Open a support ticket with your account details, the charge in question, the billing plan involved, and the approximate date of the charge so the billing team can investigate.
Submit a support ticket with the relevant billing details. Refunds are reviewed by the billing team and are only considered in limited cases such as improper billing, a SensePC error, or infrastructure downtime caused by the cloud resource provider.
If the knowledge base does not resolve your issue, open a support ticket so the team can review your account, desktop state, billing context, and any related session details.
If the FAQ does not solve the issue, use the support flow to open a ticket so the team can investigate with the appropriate account, billing, and desktop details.
Include your account email, desktop name, selected location, billing plan, a short description of the issue, when it happened, and any screenshots or error messages that can help the team investigate faster.
Yes. The support workflow is designed to allow attachments so users can include screenshots or other relevant files when reporting an issue.
Check your internet stability, confirm you selected the best location for your location, close unnecessary local browser tabs or apps, and review whether your workload needs a stronger cloud PC configuration.
Refresh the dashboard, wait for the status to update, and confirm your account and billing state are valid. If the status does not change, contact support with the PC details.
Check whether NICE DCV is installed, make sure your browser did not block the application launch, allow the launch prompt if it appears, and try Performance Mode again.
That is expected fallback behavior. Keep using the browser session, verify that NICE DCV is installed, check whether the browser blocked the app launch, and try again or use the .dcv connection file if available.
Use the available fallback flow, including the .dcv connection file download, and open the NICE DCV native client manually.
Return to the SensePC dashboard, reconnect to the same running SensePC in the browser, and then start Performance Mode again.
The current Disconnect action is a full session stop, not just a browser-only leave action. It ends the backend session and disconnects the browser viewer.
Potentially yes. The current Disconnect flow stops the backend session, so if another DCV client is attached to the same session, that action can affect it.
SensePC keeps the browser session alive first because disconnecting early creates a poor fallback experience if the native client is missing or the launch fails.
No. Although backend support exists for future force-new-session workflows, the current frontend Performance Mode handoff intentionally does not use that path during this feature.
Yes. Business users can invite team members into the workspace and manage access based on the account structure and assigned role.
SensePC team environments support role-based access with Owner, Admin, and Member users. Each role has a different level of access and management permission.
No. SensePC management permissions depend on the assigned user role. Owners and Admins have broader access, while Members have limited access.
Yes. Owners and Admins can assign a SensePC to a specific user so access is clearer and easier to manage.
Owners and Admin users can access any SensePC in the account.
No. A Member user can access only the SensePC that has been assigned to them by an Owner or Admin.
No. Member users can use only the SensePC assigned to them.
Only the Account Owner or an Admin user can assign a SensePC to a user.
Only the Account Owner or an Admin user can deassign a SensePC from a user.
No. Member users do not have permission to assign SensePCs.
No. Member users do not have permission to deassign SensePCs.
No. Member users do not have permission to create SensePCs.
No. Member users do not have permission to delete SensePCs.
A Member user can use only the SensePC assigned to them. They do not have permission to create, assign, deassign, or delete SensePCs.
For SensePC access and assignment management, both Owners and Admin users can access any SensePC in the account and manage assignments.
Yes. Admin users can access any SensePC in the account, including SensePCs assigned to other users.
Yes. The Account Owner can access any SensePC in the account, including SensePCs assigned to other users.
No. SensePC assignment management is limited to the Account Owner and Admin users.
The Member role is best for users who only need access to an assigned SensePC and do not need management permissions such as creating, assigning, deassigning, or deleting desktops.
The Admin role is best for trusted users who need broader workspace access and management capabilities, including access to any SensePC and assignment control.
The Account Owner should be the primary workspace owner responsible for overall account control and full SensePC access across the account.
Yes. SensePC is well suited for remote teams that want more consistent cloud desktop access without depending on identical local hardware across every user.
Yes. Business workspaces support inviting users and assigning roles based on the account structure, billing setup, and rollout plan.
Yes. SensePC can help teams onboard new hires faster by giving them access to a more repeatable cloud desktop environment instead of preparing every local workstation separately.
Yes. SensePC supports role-based access so organizations can manage who owns the workspace, who has administrative control, and how users are assigned to desktops.
Yes. SensePC helps teams create a more standardized desktop experience across users even when the team does not use identical local hardware.
Yes. SensePC supports centralized business workflows for user access, desktop assignment, wallet funding, and billing visibility from the broader account experience.
If you need help with a SensePC issue, sign in to your account and use the support feature to open a support ticket. The support feature is available to signed-in users.
Yes. You need to sign up and sign in to use the support feature and open a support ticket.
No. The Contact page is public, but the support feature is available only to signed-in users.
Use the Support feature when you need help with a SensePC account, desktop, billing, provisioning, access, or connection issue. The Contact page is public, but the support feature is designed for signed-in users who need account-specific help.
Include the SensePC name, account email, location, billing plan, a short description of the issue, when it happened, and any screenshots or error messages. This helps the support team investigate faster.
Yes. Signed-in users can use the support feature for billing-related issues, including charge reviews, payment concerns, and refund requests that need billing team investigation.
Yes. If you cannot access your SensePC, cannot open the remote desktop session, or see unexpected connection issues, sign in and open a support ticket with the relevant details.
Yes. The support workflow supports attachments, so signed-in users can include screenshots or other relevant files to help explain the issue.
Yes. The support experience is ticket-based, so signed-in users can review their ticket history and related replies.
Yes. Support replies are handled through the ticket-based support experience, and signed-in users can review updates there.
Use support for issues such as desktop access problems, billing concerns, refund review requests, provisioning delays, connection issues, and other account-related problems that need investigation.
Provide the SensePC name, account email, location, billing plan, time of the issue, a clear description of what happened, and any screenshots or error messages you have.
If you could not find the answer you need, contact the SensePC support team or review the tutorials for step-by-step guidance.