Policy
Fair Usage Policy
Last updated: November 2025
VaultScope provides a generous free tier and shared resource pools to help builders experiment without a credit card. This Fair Usage Policy explains how we balance that flexibility with the responsibility to keep the platform stable for everyone. It applies to every workload, whether it runs on the free tier, paid Minecraft servers, or bespoke infrastructure.
These guidelines complement the Terms of Service and Acceptable Use Policy. If there is a conflict, those documents take precedence.
Resource expectations
Use resources within the limits of your plan. Sustained consumption that degrades neighbouring workloads may be throttled or migrated without notice.
Compute & memory
- Free tier workloads are capped at 40% shared vCPU and 512 MiB RAM. Bursts above 80% sustained for more than 10 minutes may be throttled.
- Paid workloads are entitled to the resources purchased for their tier. Bursting above 125% of the included CPU for longer than 15 minutes may trigger throttling.
- Cryptomining or synthetic load generation to monopolize CPU is prohibited on every plan.
Storage & backups
- Free tier storage is limited to 5 GiB per container. Long-lived artifacts, ISO images, or backup archives are not permitted on the free tier.
- Paid plans must keep utilization under 90% of the provisioned SSD quota to maintain snapshot reliability.
- Backups older than 30 days may be pruned if they exceed the number of guaranteed backup slots on your tier.
Network & bandwidth
- All tiers include unmetered transfer on a shared 1 Gbps uplink. Sustained traffic above 250 Mbps per container may be rate limited to protect other tenants.
- Free tier workloads cannot be used as CDN nodes, VPN relays, or public download mirrors.
- Traffic that triggers repeated abuse complaints (spam, reflection attacks, etc.) may be suspended immediately.
Panel & automation
- API polling must stay below 120 requests per minute per project.
- Automated deployment loops should include exponential backoff; tight retry loops that degrade panel performance will be blocked.
- Do not share panel credentials. Use sub-users with scoped permissions instead.
Temporary bursts
We allow short bursts for deployments, backups, or major content drops. Please open a ticket in advance if you expect a burst that will exceed your plan for more than 30 minutes so we can allocate capacity proactively.
- Paid tiers may request a scheduled burst with at least 24 hours’ notice.
- Free tier workloads cannot exceed 2 simultaneous containers per account.
- Minecraft servers may not run more than one intensive world reset per hour without prior approval.
Enforcement process
Our goal is to nudge rather than surprise. Most issues are resolved with a quick conversation, but we reserve the right to act immediately when the platform is at risk.
1. Notification
We email the account owner with details about the policy breach and steps to resolve it.
2. Mitigation
If the breach creates immediate risk to other tenants, we may throttle or suspend the workload while we await your response.
3. Remediation
You will have 72 hours to reduce usage, migrate, or upgrade. Repeated violations can result in account termination per our Terms of Service.
Need an exception?
If your workload requires sustained usage beyond these limits, reach out so we can scope a dedicated or higher tier environment.
- Email support@vaultscope.dev with your expected CPU, memory, storage, and bandwidth profile.
- Provide at least 3 business days for us to review bespoke or burst requests.
- We may offer alternative architectures (queue workers, dedicated nodes, etc.) where appropriate.
Questions
Need clarification? Join the VaultScope Discord or open a support ticket via the panel.