Frequently asked questions
Publishing, project ownership, and limits for free static web hosting.
Publishing with Agivo
What can I publish on Agivo?
Static websites, reports, prototypes, and files, including HTML, CSS, browser JavaScript, and prebuilt static exports. Build your project before uploading. Agivo does not run backend servers, server-side rendering, databases, or background jobs.
Which agents can publish to Agivo?
Agents that can use a CLI or make HTTP requests can publish through Agivo’s publishing API. Start with the agent skill or follow the quickstart for setup instructions.
Do I need an account to publish?
No. You can publish a temporary project without an account. It expires after 24 hours by default, unless you claim it before it expires. You can also publish directly to an account with an API token.
How do I keep a temporary project?
Open the private claim link returned when you publish, then log in or create an account and claim the project before it expires. Claiming removes the temporary expiry. Keep this link private: anyone with it can claim the project.
Can I update a project or restore an earlier version?
Yes. Publish with the same project slug and your account token to keep the same URL. If the project is temporary, claim it first. Open deployment history in your dashboard to restore a saved deployment. Keep your own backups too.
Are my published files public?
Projects are public by default unless you explicitly configure password access. Share the public project URL, not the claim link. Review every upload and exclude passwords, API tokens, private keys, and confidential data, even when using access controls.
What are the upload limits?
The current upload limit is 20 MB of decoded content and 1,000 files per deployment. Account storage and publishing quotas also apply. See limits and safety before publishing.