VeloxwardHelp
Frequently asked questions
Quick answers about Veloxward products, pilots, and infrastructure requirements.
What does Veloxward provide?
Veloxward builds two complementary products: Veloxward VDI (workspace catalog, session broker, desktop pools, and HTML5/RDP brokering) and Veloxward ADC (TLS termination, load balancing, VPN, and clientless access at the network edge).
Which hypervisors are supported?
Veloxward VDI integrates with Proxmox, VMware, and Hyper-V for template-based provisioning and desktop pool operations. Your team retains ownership of the hypervisor layer.
Is Veloxward cloud-only or on-premises?
Veloxward is designed for on-premises and private cloud deployments where you control the hypervisor, directory services, and network edge. Deployment topology is scoped during assessment and pilot planning.
Can we start with a pilot?
Yes. The VDI Pilot service package includes a controlled rollout for a pilot user group, session hosts, and go-live week support. See services for details.
What infrastructure is required?
A typical estate includes Active Directory or LDAP, session hosts, a supported hypervisor, and network connectivity for users to reach the Veloxward edge. Controllers use PostgreSQL and Redis. A readiness assessment reviews your environment before build-out. See also cloud foundations.
How do Veloxward ADC and VDI work together?
ADC sits at the network edge (TLS, load balancing, VPN, Internet Gateway). VDI runs the control plane (broker, portal, entitlements, gateway brokering). ADC fronts HA controller clusters in production deployments.
Can users access desktops via browser?
Yes. Veloxward VDI supports HTML5 gateway access in addition to standard RDP launch paths. The right option depends on your security policy and endpoint standards, scoped during pilot planning.
How do we get started?
Email support@veloxward.com or use the contact form. Tell us your approximate user count, hypervisor, and whether you are exploring a pilot, services engagement, or product overview.