Build and deploy the release
Run the production build and deploy it to a host that supports the site's SSG, DSG or SSR requirements, then check every route in scope.
Paste a browser-accessible Gatsby deployment, send one review link, and collect comments on the pages and application states people will actually see. Every note keeps its page, browser, device and screenshot context.












Loved by1,250+Agenciesand companies in 100+ countries
gatsby build creates production-ready output and writes deployable files to the public directory. Gatsby also supports Static Site Generation (SSG), Deferred Static Generation (DSG) and Server-Side Rendering (SSR); SSR requires a running Node.js server.
Four boundaries keep the review representative:
The development command prioritizes rapid feedback and debugging. Use gatsby build and review the output or a deployment produced from it.
Gatsby documents gatsby serve as a way to test compiled output. A local server is not directly reachable by external reviewers without a secure tunnel.
DSG builds a page on its first request, while SSR renders on each request and requires a Node.js server. Confirm the chosen host supports the rendering features in use.
Pasting a URL does not bypass deployment access, application authentication, or hosting controls. Reviewers need permission to open protected routes and previews.
How it works
Run the production build and deploy it to a host that supports the site's SSG, DSG or SSR requirements, then check every route in scope.
Paste the accessible deployment URL into BugSmash and share the generated link. Reviewers comment on the rendered site without repository or hosting access.
Each item keeps the page URL, selected element, screenshot, browser and device so the team can reproduce the report.
Attach feedback to the visible page instead of translating it into a template or component description.
Check desktop, tablet and mobile views and retain the viewport with each report.
The page URL, browser, device and screenshot arrive with every comment.
Review each rendering mode on a host that supports its runtime behavior.
Preserve decisions independently of later builds, content changes or adapter and hosting updates.
Turn visual feedback into work for content, design, frontend or platform teams with its original context.
BugSmash reviews a browser-accessible Gatsby deployment. Rendering mode, hosting capabilities and access controls determine which routes reviewers can reach.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public Gatsby SSG deployment | Works | Paste the hosted production-build URL and review the generated pages. |
| Public DSG or SSR deployment | Works | Use a host that supports the selected rendering feature, then review the deployed routes. |
| Accessible deploy preview | Works | Share the preview URL after confirming its build and runtime match the release. |
| Preview protected by supported Basic Auth | Works | Provide the permitted Basic Auth credentials through the supported review flow. |
| gatsby develop or local gatsby serve | Not directly | Deploy the build or expose the local server through a secure HTTPS tunnel. |
| Routes behind application login or SSO | Use the Widget | Install the Feedback Widget in the site so reviewers can comment while remaining inside the authenticated browser session. |
Add the BugSmash script to the browser-facing Gatsby site when reviewers must remain inside authenticated, personalized or long-lived client state. Install it in the rendered UI used by the routes under review.
Keep content, design, engineering and QA reviewing the same production build and hosting behavior.

Review complete pages and responsive layouts on a deploy preview or release stakeholders can open.
See how
Receive visual reports with the route, selected element, browser, device and screenshot already attached.
See how
Validate SSG, DSG and SSR behavior on the intended host before release.
See howA comment on the deployed site becomes a task with its page, selected element, screenshot, browser and device context attached.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the site, campaign PDF, walkthrough video, launch images, email and presentation in one review project with one approval trail.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Use a deployment made from gatsby build for sign-off. Gatsby documents develop as optimized for rapid feedback and debugging, while build creates production-ready output.
Paste an accessible Gatsby deployment URL and send the first review link in under a minute.
