Share an app built with AI (OpenCode, Claude Code, Cursor) with clients

Your app is ready in OpenCode (or Claude Code, Cursor, Bolt) and runs at http://127.0.0.1:5173. That address cannot be shared: 127.0.0.1 means this computer itself, so when your client opens it, their browser looks for the app on their own computer. This guide gives three ways to let your client open it.

Pick a way

Suggestion: use A for the demo, then B once the client agrees. Want OpenCode to do everything, from an empty server to online? See From an empty VM to online.

A. Preview from your computer (tunnel)

Saka opens an outbound connection from your computer to the internet, so you need no public IP and no router ports.

1. Install the Saka agent on the computer running the app. Linux: see Add a server. Windows: run OpenCode and the app in WSL2, then install the agent in WSL2 (WSL2 guide). Mac: see the Mac section below.
2. Allow the tunnel address in Vite. Recent Vite versions reject hosts other than localhost ("Blocked request. This host is not allowed"). Add to vite.config:
   vite.config.ts

   export default defineConfig({
     // ...other settings unchanged
     server: { allowedHosts: ['.hack.id'] },
     preview: { allowedHosts: ['.hack.id'] },
   })

3. Serve the build, not dev mode (faster and lighter for your client):
   Terminal

   npm run build
   npx vite preview --port 4173

   Dev mode (npm run dev, port 5173) works too, but every page loads slower from far away.
4. In the panel, Tunnel menu: enter a name (e.g. demo-shop), pick your computer's server, choose another web app, enter port 4173, then Create address.
5. Send https://demo-shop-app.hack.id to your client. New addresses are reviewed by the Saka team first (usually quickly) and you are notified on Telegram.

Let OpenCode do it. Once Saka is connected to OpenCode, just write:

Allow the .hack.id host in the server and preview sections of vite.config, run npm run build then vite preview on port 4173, then create a Saka tunnel named demo-shop to port 4173 on my laptop server and tell me the address.

Using a Mac?

The Saka agent only runs on Linux, so on a Mac way A needs a virtual machine first. Two options:

• Easiest: skip your Mac and use way B. Create a small server from your DigitalOcean, Vultr, or IDCloudHost account right from Saka (Create servers from a cloud account, about US$6 a month), then deploy the app from Git. Your Mac does not need to stay on and no virtual machine is needed; clients can open it any time.
• Still from your Mac (way A):
  1. Create an Ubuntu virtual machine and install the Saka agent in it: Path C: Mac through Multipass.
  2. Run Vite on the Mac with --host so the virtual machine can reach it (if macOS asks to allow incoming connections for node, choose Allow):
     Mac terminal

     npm run build
     npx vite preview --host --port 4173

  3. Find the Mac's address as seen from the virtual machine:
     Mac terminal

     multipass exec saka -- sh -c "ip route | awk '/default/ {print \$3}'"

     The result is usually 192.168.64.1.
  4. In the Tunnel menu: choose another web app, port 4173, and fill On another device on the network with the address from step 3.
  I have not tested this directly on a Mac, so if it fails, tell us with the Request a feature button in the panel. The Mac and the virtual machine must stay on and awake while clients open the address.

B. Always online from Git

1. Put the code on GitHub/GitLab/Gitea. Ask OpenCode: "initialize git, add a .gitignore, commit, and push to a new repo". Private repos work too (Saka gives you a deploy key).
2. In the panel: Sites, Create site, App from Git, enter the repo address and branch, pick a server and domain. Vite, Next.js, Express, and more are detected automatically via Railpack; a Dockerfile is used when present.
3. Point the domain's A record to the server IP. HTTPS is set up automatically. No domain yet? Use a name.IP-with-dashes.sslip.io address as the site's domain, e.g. shop.159-223-87-126.sslip.io: automatic HTTPS with no DNS setup, good for demos (use your own domain for production). Or a tunnel for a name-app.hack.id address.
4. API keys and other secrets go in the Environment variables card, not in the code.
5. Add the webhook (instructions on the app page): every push deploys with no downtime, and a bad release can be rolled back with one click.

Revisions with your client: turn on Pull request previews. Every change you propose in a pull request gets its own address for the client to check before it is merged.

C. Static site

For apps without their own backend (everything runs in the browser):

1. Run npm run build. The result is the dist folder.
2. In the panel: Sites, Create site, choose Static, enter the domain.
3. Upload the contents of dist to the www folder over SFTP (login details on the site page, e.g. with FileZilla).

Single-page apps (React Router and similar) that open deep addresses like /products/12 are safer with way B, because a static server answers 404 for addresses that are not files.

From an empty VM to online: hand it to OpenCode

Once Saka is connected to OpenCode, the whole road from an empty server to an HTTPS address can be done by OpenCode. You only do the few things that must come from you:

An opening message you can paste into OpenCode:

Call Saka's panduan_deploy tool first and follow its steps. Put the project in this folder online on a Saka server so my client can open it at an HTTPS address. Ask me about the repo, domain, and server first. Never write keys or passwords in the chat.

The panduan_deploy tool gives OpenCode the same steps and rules as this page.

If you create an Ubuntu VM yourself

1. Create an Ubuntu 22.04 or 24.04 VM at any provider: at least 1 vCPU and 2 GB RAM, with a public IPv4. In the provider's firewall, open ports 22, 80, and 443.
2. Ask OpenCode to call server_tambah, or open the panel: Servers, + Add server. You get a one-line command.
3. Log in to the VM (ssh root@SERVER-IP or the provider's web console), paste the command, and press Enter. The server shows up in Saka within seconds, and from then on OpenCode manages it through Saka with no more SSH. New servers are protected by Saka Shield right away.

What to watch in the app

• No persistent disk. Files the app writes (SQLite databases, uploads) are lost on every deploy. Use a managed database (a Saka cluster or an external one) and S3 object storage for uploads. AI-built apps often default to SQLite: ask OpenCode to switch to PostgreSQL.
• Port and address. The app listens on the PORT variable and on 0.0.0.0, not only 127.0.0.1.
• Production build, not the dev server (npm run dev). Without a Dockerfile, the app type is detected automatically.
• Secrets (API keys, database passwords) go in the Environment variables card or situs_env, not in code or the repo.

Connect Saka to OpenCode

Create a token in the panel (Settings, API tokens), then add it to your project's opencode.json (or ~/.config/opencode/opencode.json):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saka": {
      "type": "remote",
      "url": "https://app.saka.work/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

OpenCode can then create tunnels, deploy apps from Git, and watch deploys through Saka, with your approval for actions that change a server. Do not commit a file containing the token to a public repo. Full tool list: Connect AI (MCP).