Skip to main content
A personal website can start with static hosting and a domain. Add a server, database, or email provider when a feature requires one. Each extra service introduces another account, limit, outage mode, and export format. This shortlist is for evaluation; it is not a statement that every AVRXT deployment uses these plans.

​
Services to evaluate

​
Free is a budget

A free plan can fit an experiment while being unsuitable for a critical inbox or an always-available feature. A domain, maintenance time, and optional paid services remain separate costs. Understand whether usage stops at a cap or can generate charges after a plan change. Do not assume that an account without a current invoice has unlimited capacity.

​
Evaluate before connecting

Create a separate project, protect the account, and store API credentials as server-side secrets. Check alerts and spending controls where available. Test an entire flow, including a provider failure. Export important data and record how to move it elsewhere. A service is easier to replace when its data format and responsibilities are clear.

​
Current sources

Reviewed 6 November 2026. Offers change; use these official pages for current quotas and eligibility rather than treating copied limits as permanent promises. Next: host a static website or set up domain email routing.