Stop deploying just to show someone your app.
ssh -R 80:localhost:3000 tinyfi.sh
The easiest way is to send to your agent
or add tinyfi.sh as a skill
mkdir -p ~/.claude/skills/tinyfish && curl -o ~/.claude/skills/tinyfish/SKILL.md https://tinyfi.sh/skill.md
Then just tell Claude: "share my app" or "make my app public"
Downloadmkdir -p .cursor/rules && curl -o .cursor/rules/tinyfish.mdc https://tinyfi.sh/cursor.md
Then just tell Cursor: "share my app" or "make my app public"
Downloadmkdir -p .github && curl https://tinyfi.sh/copilot.md >> .github/copilot-instructions.md
Then just tell Copilot: "share my app" or "make my app public"
Downloadcurl https://tinyfi.sh/windsurf.md >> .windsurfrules
Then just tell Windsurf: "share my app" or "make my app public"
Downloadcurl https://tinyfi.sh/cline.md >> .clinerules
Then just tell Cline: "share my app" or "make my app public"
Downloadmkdir -p ~/.openclaw/workspace/skills/tinyfish && curl -o ~/.openclaw/workspace/skills/tinyfish/SKILL.md https://tinyfi.sh/skill.md
Then just tell Clawdbot: "share my app" or "make my app public"
DownloadAI generated your app? Share it instantly without deploying.
Get quick feedback from teammates without deployment ceremony.
Get feedback on your side project before it's finished.
Check mobile responsiveness without deploying to staging.
Test webhook integrations on your local development server.
Validate ideas fast without infrastructure overhead.
SSH creates a secure tunnel from your laptop to tinyfi.sh server and generates a unique random URL like abc123.tinyfi.sh. When someone visits this link, we forward the traffic through the tunnel to your local app. No installation needed—just SSH, which is already available in every system.
Yes. No premium tier.
No.
Any port on your machine. Port 3000 is common for web dev servers, but you can use any port your app runs on.
Uses SSH tunneling. Your links are unguessable random subdomains. The connection between you and tinyfi.sh is encrypted via SSH.
The tunnel closes and your link stops working. Your app needs to be running locally for the link to work.
Designed for dev and demo workflows. For production apps, we recommend proper hosting with monitoring, backups, and SLAs.
Want a specific subdomain instead of a random one? Use this format (works only if the name isn't already taken):
ssh -R custom:80:localhost:3000 tinyfi.sh
This gives you https://custom.tinyfi.sh instead of a random URL.
By default, your link dies when you close the terminal. To keep it running and maintain the same URL:
screen -S tunnel
ssh -R 80:localhost:3000 tinyfi.sh
Detach with Ctrl+A then D. Reattach later with screen -r tunnel
nohup ssh -R 80:localhost:3000 tinyfi.sh &
Runs in background. Your link stays active even after closing the terminal.
ssh -R 80:localhost:3000 tinyfi.sh