Show the client before it ships.
"Can you put that somewhere I can look at it?" is most of client work. slew answers it three ways, none of which involve a staging server to maintain or an account for the client to create.
Preview URLs on every pull request
A project connected through the GitHub App gets a preview deployment for every pull request: its own URL, updated on each push, expiring by itself after 7 days. The link lands on the PR as a status check — review the actual site, not screenshots of it.
A link for anything: slew share
Not everything lives in a repository. A mockup, a report, a proposal — one command puts it on a temporary URL:
$ slew share report.html
Shared 1 file at https://quiet-harbor-lantern.slew.cloudNobody needs an account to open it, and it deletes itself after a week — throwaways stay throwaway. Coding agents can do this themselves: hand Claude Code or Cursor the slew-share skill and every plan or mockup it writes comes back as a link you can forward.
Password-protected sites
A launch that isn't public yet can sit behind a password: slew password set puts the whole site behind an unlock screen, and removing it makes the site public again. Enforced for every visitor, cached correctly at the CDN, no code changes in your project.
Frequently asked
- Do preview deployments count against my project limit?
- No — previews from pull requests and share links don't count as projects.
- Can a share link hold a whole directory?
- Yes: slew share accepts a file or a directory, so a built site can be shared as one expiring URL.
- How do I stop a share early?
- slew shares lists your live links and slew shares rm deletes one immediately.
- Is any of this extra-cost?
- No. Previews, shares and password protection are part of every plan, including free.