Actinis Cloud Device
Retired

Enterprise mobility
without the hardware

Cloud Device ran corporate apps on hosted virtual Android devices, accessed from the iOS, Android, or desktop hardware employees already used. It was built for teams that needed Android app access without shipping dedicated phones or installing device management on personal devices.

Retired

Cloud Device is no longer offered. This page describes what it did. For Android apps on Linux, see Drion; for Android platform work, see our services.

Watch video
Why teams looked for alternatives

Corporate app access often brought hardware, policy, and support overhead

01

Cost burden

  • Buying, shipping, and replacing corporate phones
  • Per-device EMM or MDM licensing and administration
  • Support for setup, returns, and lost hardware
  • Asset tracking across employees and contractors
02

Endpoint data risk

  • Corporate data copied onto personal or field devices
  • Lost and stolen endpoints
  • Gaps between BYOD policy and real device state
  • App-to-app sharing paths that are hard to inspect
03

Employee inconvenience

  • Carrying multiple phones
  • Privacy concerns with BYOD
  • Complex device setup
  • Limited cross-platform support
How it worked

Corporate apps on hosted virtual Android devices

Employee device

Access from any iOS, Android, or desktop device

Hosted session

Isolated virtual device instance per user or deployment

Virtual Android

Android environment configured for the apps and policy in scope

Corporate apps

Custom behavior & security policies

Hosted Android sessions
Bandwidth-conscious streaming
App access from existing devices
Deployment-specific policy
Data handling

Corporate app sessions stayed off personal storage

Endpoint footprint

Corporate app data stayed in hosted virtual devices instead of being copied onto personal phones.

Isolated sessions

Each virtual device ran in its own managed environment.

Remote administration

Admins could lock or remove access to the hosted device when needed.

Audit options

Deployments could include monitoring and recording where policy and law allowed.

  • Browser tracker and ad-blocking options
  • Encrypted transport
  • Controlled file transfer
  • Location and sensor policy controls
  • Per-app policy hooks where supported
App policy customization

Selected Android app behavior, shaped for managed deployments

Messaging

  • Limit local media saving where app flow allows
  • Restrict forwarding or sharing paths
  • Control file exchange with the endpoint

Email

  • Attachment policy
  • Forwarding controls
  • Watermarking or audit labels when scoped

Browser

  • Download policy
  • Allowed and blocked site rules
  • Browser setting lockdown

Line-of-business apps

  • Button or intent behavior changes after review
  • Data-sharing boundaries
  • Deployment-specific policy enforcement
What it changed

Less device logistics, fewer endpoint data paths

Device operations

No fleet shipment
For eligible app-access programs
  • Avoided dedicated phone procurement for selected users
  • Reduced setup and replacement handling
  • Kept contractor and pilot programs lighter
  • Scoped device access without owning the endpoint

Control surface

Hosted sessions
Policy applied around the virtual device
  • Reassigned access without moving a physical phone
  • Supported iOS, Android, and desktop endpoints
  • Kept app data inside the hosted Android session
  • Applied policy at the app and virtual-device boundary