Upload the site you built
Sunrose accepts a folder or ZIP containing HTML, CSS, JavaScript, and assets. Include index.html at the site root. For a framework project, upload its static build output rather than its source code.
Sunrose serves your files; it does not run a build pipeline, a database, or server-side code. Your upload must fit your workspace’s file and storage allowances.
To share designs rather than a website, drop images or PDFs instead. Sunrose lays them out page by page for on-page comments and approval.
Collect on-page feedback
Create a client review link when you want comments alongside the website. Your reviewer opens the link without creating an account and confirms they are a person before their first comment or approval.
Use a plain preview address when you only want to show the site. Review controls are optional.
Record approval of a version
Each upload creates a version. A review stays attached to its original version, so an approval does not silently apply to later changes.
An approval records the reviewer’s entered name, the date, and a receipt code. Sunrose does not verify that person’s identity, and the record is not a legal signature.
Control preview access
Review previews are unlisted and ask search engines not to index them. A site published as Static hosting starts listed on paid plans. An owner can switch either one between listed and unlisted in project settings. Anyone with a preview address can open it unless you set a password.
A review link bypasses the preview password and grants access to its review. Share it only with intended reviewers. Turning off a review link does not turn off the separate preview address.