Free Hosting Policy
Rules, resource boundaries, inactivity requirements, and security policies governing VisiHost's free bot hosting tier.
Free Tier Currently Unavailable: The VisiHost Free Tier hosting program is currently unavailable and closed to new registrations. We encourage developers to deploy on our high-performance paid containers starting at just ₹10/month at paid.visihost.in.
This policy outlines the archival rules, resource boundaries, and terms governing prior free tier allocations.
1. Account Eligibility & Fair Access#
To prevent capacity hoarding and ensure equitable access:
- One Account Per Person: Free tier hosting is strictly limited to one (1) account per individual.
- No Duplicate or Alternate Accounts: Creating alternate Discord accounts or multiple email registrations to claim multiple free servers is strictly prohibited. Our automated onboarding systems monitor registration telemetry and will automatically terminate duplicate accounts.
- Discord Community Verification: Provisioning a free container requires joining our official Discord Community and completing standard role verification.
2. Resource Allocation & Limits#
Each free container is provisioned with a standardized baseline specification:
| Resource | Allocation | Details |
|---|---|---|
| Memory (RAM) | 256 MB | Dedicated container memory allocation |
| Compute (CPU) | 20% vCPU | Shared burstable slice of an AMD EPYC processor |
| Storage | 1 GB NVMe SSD | Enterprise Gen4 NVMe storage |
| Control Panel | free.visihost.in | High-speed Pterodactyl container interface |
| Bandwidth | Fair-share unmetered | Optimized for Discord & Telegram API traffic |
| Supported Runtimes | Node.js, Python, Bun | Modern LTS versions available |
These resource boundaries are fixed. Adding extra RAM or storage to a free container is not supported; projects needing additional headroom should transition to our Paid Bot Hosting.
3. SLA & Support Exclusions#
- Best-Effort Availability: Free containers run on shared clusters without formal uptime guarantees or eligibility under our Service Level Agreement (SLA).
- No Financial Remedies: Free containers do not qualify for SLA service credits or cash compensation during downtime.
- Support Scope: Free tier assistance is handled exclusively on a community-to-community basis within our public Discord channels. Dedicated one-on-one billing tickets and technical engineering troubleshooting are reserved for paid hosting customers.
4. Inactivity & Server Reclaim Rules#
To ensure hardware capacity remains available for active projects rather than dormant or abandoned instances:
- Power Status Monitoring: Automated maintenance workers monitor container power states and uptime telemetry.
- Prolonged Inactivity: Containers that remain stopped or powered off for extended continuous periods (typically 7 to 14 days) will be flagged for reclamation.
- Reclaim & Data Deletion: When an inactive container is reclaimed, all files, environment variables, and configurations are permanently deleted.
- Local Backup Responsibility: Because free containers do not include automated offsite backup snapshots, you must keep local copies of your bot's source code on your personal computer or a GitHub repository. VisiHost cannot restore reclaimed or deleted free containers.
5. Prohibited Workloads on Free Tier#
Free containers are engineered strictly for lightweight conversational bots and event-driven automation. The following workloads are strictly prohibited:
- Audio Streaming & Lavalink Nodes: Free containers do not have sufficient memory or compute to handle audio decoding pipelines. Running Lavalink or music-streaming bots on the free tier is strictly forbidden.
- Web Scrapers & Mass Crawlers: Automated web crawlers that generate excessive outbound HTTP requests.
- Cryptocurrency Mining: Any mining scripts or cryptojacking binaries.
- Public Proxies & VPN Relays: Tunneling external network traffic through the container.
- Database Servers: Running resource-intensive standalone database instances inside a free container.
6. Automated Security & Abuse Scanning#
To protect parent host nodes and innocent community developers:
- Automated security monitors continuously inspect free container processes for known exploit signatures, stresser scripts, port scanners, and unauthorized binaries.
- Any container detected executing malicious tools, phishing scripts, or flood utilities will be terminated immediately without advance warning and the owner's account will be permanently banned.
7. When & How to Upgrade to Paid Hosting#
If your bot expands beyond the free tier limits (such as reaching 50+ Discord servers, needing more than 256 MB RAM, requiring custom databases, or needing 24/7 priority SLA backing), you can smoothly migrate to our Paid Discord Bot Hosting:
- Pricing: Plans start at just ₹10 per month for 512 MB to 1 GB RAM.
- Features: Dedicated resources, no inactivity reclaiming, daily automated backups, priority ticket support, and 99.5% SLA uptime protection.
- Control Panel: Paid services operate on our premium panel cluster at paid.visihost.in.
To upgrade, visit the Client Area or explore our Discord Bot Hosting page.
8. Frequently Asked Questions (FAQ)#
Is the free tier truly 100% free forever?#
Yes! Our Free Zero-Tier hosting requires no credit card and does not incur any hidden fees. As long as you keep your bot running and periodically log in to prevent inactivity cleanup, your free container remains active.
Can I create two free accounts to host two different bots?#
No. Free tier hosting is strictly limited to one (1) account per person. Creating alternate accounts to claim multiple free slots violates our fair-access rules and results in automated termination of all duplicate accounts.
Can I host a Lavalink music node on the free tier?#
No. Audio encoding, stream buffering, and YouTube audio decoding consume significant memory and CPU cycles that exceed free tier limits. For audio nodes, please use our dedicated Lavalink Hosting plans.
What happens if my free container is reclaimed due to inactivity?#
When a container is reclaimed, its files and configuration are permanently deleted to free up resources for active community members. Always keep copies of your bot's code stored in a GitHub repository or on your personal computer.
