Fair Usage Policy (FUP)
Done 5 Technologies
Last Updated: April 2026
1. Purpose
This Fair Usage Policy defines how resources are allocated, monitored, and enforced across Done 5 Technologies services.
Done 5 does not sell “unlimited” resources.
We operate controlled infrastructure designed to remain stable under load, attack, and abuse.
Every account shares the same environment.
One abusive account can degrade performance for others — this policy exists to prevent that.
This policy operates alongside:
- Terms of Service (TOS)
- Acceptable Use Policy (AUP)
2. Core Principle — Controlled Sharing
All shared and reseller hosting environments operate under controlled resource allocation.
You are allowed to:
- Run normal business websites
- Operate CMS platforms (WordPress, Laravel, etc.)
- Serve real user traffic
You are NOT allowed to:
- Use disproportionate resources affecting other accounts
- Treat shared hosting as unlimited infrastructure
- Run workloads designed for VPS/dedicated environments
If your usage exceeds shared environment boundaries, you will be required to upgrade.
3. Disk Usage & Storage Policy
Hosting storage is strictly for active website data only.
Prohibited usage:
- Backup storage (local or remote dumps)
- Archive storage (ZIP, TAR, full backups stored long-term)
- Media dumping (videos, datasets, unrelated files)
- File distribution / mirror hosting
- Storing application backups inside public_html
Enforcement:
- If non-website files exceed 70% of disk usage, the account is flagged
- Immediate cleanup request issued
- Failure to comply → restriction or suspension
4. Inode (File Count) Limits
Each hosting plan has a defined inode limit.
High inode usage is one of the primary causes of:
- Backup failure
- Slow file operations
- Server load spikes
Common violations:
- Multiple WordPress staging copies
- Backup folders inside hosting
- Unused themes/plugins
- Mailbox abuse storing large files
Enforcement:
- 80% usage → warning issued
- 100% usage → file creation restricted
- Continued abuse → account limitation
(Inode enforcement is mandatory under Done 5 infrastructure control model)
5. CPU, RAM & Process Usage (LVE Limits)
All accounts are isolated using CloudLinux LVE.
Hard limits:
- No single process may continuously exceed 90% of a CPU core
- Sustained multi-core usage beyond plan allocation is not permitted
- Excessive concurrent processes (EP/NPROC abuse) will be limited
What counts as abuse:
- Poorly optimized WordPress or plugins
- Infinite loops / broken scripts
- High-frequency cron jobs
- Background daemons not allowed on shared hosting
Enforcement:
- Real-time throttling
- Temporary process kill
- Account suspension (repeat offenders)
6. Database Usage
Databases must be optimized and used within normal application behavior.
Not allowed:
- Excessive query loops
- Unindexed heavy queries
- Database misuse for logging/storage systems
Enforcement:
- Query monitoring enabled
- Slow queries flagged and restricted
- Database access limited if causing load
7. Bandwidth & Traffic Usage
Bandwidth is allocated based on realistic usage patterns.
Rules:
- 80% usage → notification issued
- 100% usage → service limitation may apply
- No automatic overage billing without consent
If traffic exceeds shared environment capacity:
→ Upgrade to VPS or dedicated required
8. Email Usage Policy
Email services are for transactional and business communication only.
Not allowed:
- Bulk email campaigns
- Cold outreach / spam activity
- Purchased email lists
Enforcement:
- Outbound rate limits per account
- Spam detection monitoring
- Immediate suspension if reputation risk detected
(Email reputation directly impacts entire server IP health)
9. Script & Application Behavior
All applications must be stable, optimized, and secure.
Prohibited:
- Null/unsafe scripts
- High-resource automation bots
- Cron abuse
- Background workers
Poorly coded applications that degrade server performance will be restricted.
10. Monitoring & Enforcement
Done 5 actively monitors:
- CPU / RAM usage
- Disk & inode usage
- Email activity
- Database load
- Process behavior
Enforcement model:
- Warning → Temporary limit → Suspension → Termination
Repeated violations are treated as intentional abuse.
11. Upgrade Requirement (Non-Negotiable)
Shared hosting is not designed for:
- High-traffic platforms
- SaaS systems
- Heavy WooCommerce stores
- API-driven applications
If your usage crosses shared limits, you must upgrade to:
- VPS
- Dedicated server
We will not degrade the platform to accommodate a single account.
12. No “Unlimited” Claims
Done 5 does not operate fake unlimited systems.
All resources are:
- Measured
- Enforced
- Controlled
This is required to maintain:
- Stability
- Security
- Predictable performance
(Aligned with Done 5 infrastructure philosophy — control over chaos)
13. Policy Updates
This policy may be updated at any time.
Continued use of services = acceptance of updated terms.
14. Contact
All usage concerns, violations, or upgrade requests must be handled via:
- Client portal
- Official support channels
Final Statement
Done 5 is built to keep systems running under pressure.
If one account breaks that stability, it will be controlled.
No exceptions.
