What I like best about VEXXHOST Inc is the huge flexibility of its OpenStack‑native platform, which works really well for our custom customer‑insight research workflows here at our Frankfurt IT consulting firm. We source most of our study participants through Respondent for win‑loss interviews, churn analysis and pricing research, and we constantly deal with gigabytes of interview audio and confidential participant data. Last quarter we ran a large churn‑prediction study with over 70 B2B respondents. I was able to spin up multiple lightweight VMs just for this single project to run our in‑house Python transcript processing scripts. Once we finished all analysis and delivered reports to internal stakeholders, I could fully tear down those instances instead of leaving idle resources running and wasting budget. This on‑demand provisioning fits our GDPR data‑retention rules perfectly, because we can wipe project‑specific compute environments completely once we are legally required to delete respondent personal data. I also value the fine‑grained network and storage controls inside the OpenStack dashboard. Our IT team built fully isolated network segments dedicated only to our research datasets. We keep Respondent‑sourced participant transcripts and recordings quarantined away from our regular corporate Microsoft 365 systems, and we can adjust bucket encryption settings on our own instead of being locked into fixed SaaS configurations. We don’t need to reshape our research processes to match the platform; we tailor the infrastructure around our actual research timelines. That said, this high degree of freedom comes with responsibility. You cannot treat it as a hands‑off managed cloud, and our team still needs to stay vigilant on every compliance‑related setting. Review collected by and hosted on G2.com.

There are several frustrating pain points with VEXXHOST Inc that created real near‑miss incidents for our GDPR‑bound research work. First, the entire OpenStack dashboard and official documentation exist only in English. A few months ago, our junior IT colleague whose English is conversational but not advanced was configuring object‑storage retention policies for our Respondent‑recruited pricing study participants. He misread wording in the English‑only menu, and auto‑purge rules were not activated for participant transcript files. For nearly three weeks, personal respondent data was not getting scheduled for deletion. We only caught this mistake during our monthly compliance spot‑check; if we had missed it, we would have violated German GDPR retention requirements. Another big weakness is the lack of granular custom alerts for abnormal bucket access. Not long ago, a bug inside one of our own Python scripts repeatedly hammered our storage bucket holding interview audio files overnight. There were no platform‑generated notifications at all. We only found the flood of repeated access attempts when we manually pulled audit logs the following week. Had an unauthorized party gained access, we would have had zero timely warning of a potential data breach. To make things harder, there is no native Azure AD integration with our company‑wide Microsoft 365 tenant. Every time we bring on short‑term research contractors for large‑scale projects, IT has to create standalone local VEXXHOST accounts. When contractors leave, permissions must be revoked separately, which creates constant risk of forgotten orphaned accounts. All these issues force our small team to add multiple layers of manual checks to avoid security and compliance missteps. Review collected by and hosted on G2.com.