For enterprise security
Choose where your device farm runs, who can use it, and how it fits your organization’s access requirements.
Your device lab · Your network policies
A device farm within your organization’s infrastructure.
Exact network, identity, and operating scope are defined during evaluation.
The proposal and technical review establish the exact infrastructure boundary, ownership, access, and evidence requirements.
Bring Visium Farm into your own infrastructure and connect the real devices your teams depend on.
Security boundary: Your infrastructure, with access and network policies defined by your organization.
Give your organization a dedicated device-testing environment in a customer-specific private cloud.
Security boundary: A dedicated environment, with ownership and operating responsibilities agreed during evaluation.
Test on a shared device pool operated by Visium, without running your own device lab.
Security boundary: Visium operates the shared pool. Confirm device availability and access requirements for your team.
Compare deployment location, network access, and operating responsibilities across the three options. Your organization’s requirements determine the environment that fits.
Begin with where testing infrastructure operates and which controls need to remain inside the customer environment.
Bring the deployment facts and review questions that a security or procurement process needs to assess.
Clarify the responsibilities that matter to the proposed deployment instead of assuming a one-size-fits-all model.
Manage who can connect, what they can do, and which resources they can share. Explore the controls behind each decision.
Separate device access from administration, application deployment, and reporting. Give each role the permissions its work requires.
Connect your directory and apply account controls that fit your organization’s sign-in practices.
Organize users and resources by team. Coordinate shared capacity with group permissions and device reservations.
Bring colleagues into a session with a defined permission level and a link that can expire after use.
Choose which build reaches each device. Manage application and API access alongside your existing delivery workflow.
Review captured session files and farm activity, with separate permissions for reports and diagnostic downloads.
Explore how deployment, identity, permissions, and session evidence fit into your organization’s testing workflow.
Yes. Choose on-premise for your own infrastructure, a customer-specific private cloud for a dedicated environment, or Visium’s managed public-cloud pool. The technical review establishes network access, ownership, and operating responsibilities for your chosen model.
LDAP and Active Directory integration options sit alongside user and role management, password policies, account blocking, and two-step verification. Review directory configuration and account-management responsibilities with your identity team during setup.
Roles separate device connection, application installation, automation, reporting, and diagnostic downloads. Groups organize access to devices, applications, files, and reservations, including reservation permissions and concurrent-access limits.
Yes. Choose view, control, or inspect permissions for up to three participants. Optional expiry times and single-use links let you limit how a shared session is accessed.
Upload builds to the shared version library, select a version, and deploy it to chosen devices. Group access, application restrictions, and installation permissions control distribution; parallel deployment provides progress and per-device results.
Yes. Use any Appium-compatible automation tool. APIs connect application preparation, device availability, and reservations to CI/CD, while webhooks provide device-status notifications. API and automation keys work alongside integration-management permissions.
Preview and download collected video, screenshots, and logs. Reports cover users, devices, reservations, API usage, and alarms. Available files depend on session settings; agree capture, access, and retention requirements when planning the environment.
Bring your deployment boundary, identity setup, team roles, application-access rules, and evidence requirements. Agree operating responsibilities and assess any required certification documents, retention expectations, or compliance commitments against the proposed configuration.
Start with the control boundary, device-pool scope, identity requirements, and evidence your review process expects.
Explore case studies