FREE: capabilities and limits
Start at 0 UZS. No cash bonus, card requirement, or 14-day web expiry.
750 web hours per month
Shared per workspace. Two services use two hours in one hour. Sleeping time, static sites, Postgres, and Redis are excluded. Resets on the 1st UTC without rollover. Only quota-suspended services resume; manual stops remain stopped.
Sleep after 15 idle minutes
FREE web services sleep after 15 minutes without inbound requests. HTTP or a new WebSocket wakes the service. Cold requests wait; an unready app returns 503 with Retry-After. Open HTTP streams and WebSockets keep services active. /robots.txt does not wake a sleeping service. Requests never override manual stop.
Free PostgreSQL
One per workspace. 256 MB RAM, 20 connections, a monitored 1 GB disk allowance and 30 days from creation. The database pauses at expiry or the disk limit. Disk checks run approximately every 15 seconds; usage can exceed 1 GB between checks. Data is not automatically deleted. Choose paid compute and redeploy to continue. No production SLA or backup guarantees.
Free Redis
One per workspace. 128 MB for Redis data, password authentication, no disk persistence. Full memory rejects new writes. Every restart and redeploy loses data. Intended for caches and experiments.
Transfer enforcement
Monthly outbound allowance: FREE 10 GB, HOBBY 100 GB, PRO 1000 GB. The gateway checks HTTP/WebSocket bytes before forwarding. Other outbound container traffic is sampled across all nodes approximately every 15 seconds; exceeding the limit suspends services. Internal outbound traffic is included. Usage is the larger of gateway and container counters, without adding the same traffic twice. No automatic paid overages until payments are enabled. Only bandwidth-suspended services resume next month.
Other limits
FREE workspace: 500 build minutes/month, 2 web/static services, 2 projects, 1 member. Free Postgres/Redis have separate quotas. FREE web: 0.1 CPU, 256 MB RAM. Build exhaustion blocks new builds while existing services keep running.
Differences from Render
A similar free-resource model. Lixev treats open WebSockets as activity and does not automatically delete expired Postgres data. Traffic includes internal networking. Full feature or SLA parity is not claimed.