Overview
This Acceptable Usage Policy applies automatically to all clients upon service subscription. Customer agrees to use the Services only for lawful purposes, in compliance with all applicable law.
Review our acceptable usage policy that applies to all services.
Last updated: November 25, 2019
This Acceptable Usage Policy applies automatically to all clients upon service subscription. Customer agrees to use the Services only for lawful purposes, in compliance with all applicable law.
The following activities are strictly prohibited:
We will not search, sell, rent, lend, exchange, or give your email address or any personal information to any third party without your explicit permission.
Unsolicited email is explicitly prohibited, including opt-in lists. Customers cannot relay mail through other servers without permission or advertise external services pointing to our infrastructure. Violators face account restrictions, suspension, or termination.
Material published must comply with all applicable laws. We reserve discretion to determine what constitutes unlawful, indecent, or objectionable content.
Services cannot be used for file mirroring or distribution as a primary purpose.
It is strictly forbidden to publish adult content on shared web hosting, reseller web hosting, dedicated servers, and colocation servers.
Customers cannot compromise security or tamper with system resources. Any attempt to undermine or exploit system resources is prohibited.
Shared hosting accounts must stay below 15% total system resource usage and cannot provide public online services without authorization.
We have no obligation to provide warnings under any circumstances and can terminate accounts without prior notice for violations of this policy.
Insights, updates, and stories from our team
Most organizations waste 95% of their GPU spend without knowing it. Run this five minute audit to find the leaks and fix them before the next invoice.
The fix to platform team understaffing isn't hiring more — it's building on infrastructure where monitoring, security, and upgrades come built in.
Upstream contribution costs real engineering time. It also compounds over time in ways that internal fixes never do. What fifteen years of contributing to OpenStack, Kubernetes, and Ceph actually looks like.