HTML, images and ZIP uploads
Build a draft from text, files or supported native attachments. Review it before publication.
THE TOOLBOX / PUBLISH
Publish a public website from your agent.
Give your agent somewhere to publish the things it creates. Upload HTML, images or a ZIP, publish a release, and share the result over HTTPS.
WHAT IT DOES
Make it.
Publish it.
Change your mind.
Versions you can return to
Publish an immutable release. Update it later or roll back to a retained earlier release.
Hosting under your control
Hosting is funded by UTC day from your shared balance. Pause it explicitly, or resume retained content after adding credit.
Pay for the work and hosting
Creation, accepted uploads and retained hosting are metered. Publishing or rolling back adds no separate fee. Development uses test credit. Production tariffs are published on the production service pages.
Public static content, with a clear publishing workflow
Good fits include landing pages, documentation, portfolios, reports and small browser-based tools using HTML, CSS, browser JavaScript and images. Server-side applications, databases, private visitor authentication and customer-owned domains are not included.
Ask: “Publish this HTML as a public website. Show me the initial and ongoing hosting costs first.” Current upload limits are 100 files, 2 MiB per file and 4 MiB total expanded content; a ZIP is at most 2 MiB. Upload a complete draft, then publish its revision to obtain a public HTTPS URL. Uploading a draft alone does not change the live site.
Updates, rollback and pausing
Roll back only to a retained revision. Pausing takes the site offline and stops renewal. The site identity remains, but the selected publication is retained for seven days; other revisions keep their existing expiry times. Cleanup can delete expired files and revision records. Resume before expiry, or upload and publish again later using the same site identity. Keep your own source files.
Need an external HTTP event inbox for the task? Explore Webhooks. Connect it separately using the same selected account and balance.
Development sites currently use temporary AWS addresses. This environment is for development and evaluation; its addresses and limits can change. Checkout uses test payments, not real money.