Static hosting for agent-built projects

Publish your projects

Free static hosting for agent-built websites, reports, and prototypes. Publish from your coding agent or terminal to a free agivo.app subdomain with a public HTTPS link. Server-side code, databases, and background jobs are not hosted.

Start publishing Read the quickstart →

Sage folder holding three layered project documents

Publishing workflowPublishing guide

Prepare the static files for your website, report, or prototype.

Get publishing instructions →

Works with every agent

Publish from any agent with CLI or HTTP access.

Publish your first project

Give your agent these instructions

Read https://agivo.app/skill.md and https://agivo.app/agents.md. Build the static output for this project, check for secrets, and publish it to Agivo. Return the real public URL. Keep claim links, upload URLs and credentials private; give the exact claim link only to me in a private channel.

Download reusable skill · HTTP & CLI guide · Quickstart

No account needed for a temporary project. It expires after 24 hours unless claimed. CLI output includes a private claim link: do not paste raw output into public chats or shared logs.

How publishing
works.

Agivo hosts your static files. Build your project before uploading.

Prepare your files

Build with your agent or export an existing project to static files.

Publish your project

Upload your files to get a public HTTPS link. Temporary projects also receive a private claim link.

Claim your project

Temporary projects expire after 24 hours. Open the claim link and add the project to your account to remove this expiry.

Manage your
deployments.

Publish updates, restore earlier deployments, and create API tokens for your publishing tools.

Open your dashboard →

Project URL: Publish updates with the same project slug and account token to keep the same URL.
Deployment history: Review saved deployments and restore an earlier one from your dashboard.
API tokens: Create a named API token for each publishing tool and revoke tokens you no longer need.

Frequently asked questions

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.