Docs

Create an account with an email address and a password. We send a verification link; your 7-day trial starts the moment the account is created, so there is nothing to wait for and no card to enter.

Before the agent can do anything useful it needs an inference key. Add one under Settings → API key. OpenRouter has a free tier that needs no card, so you can try this without spending anything.

Each app lives in its own folder with its own workspace, so nothing from one project can leak into another. Five starters are available:

• Blank — just a README, for when you want to decide the structure yourself.
• Website — plain HTML and CSS, served from nginx.
• Node service — an HTTP server with no dependencies, the fastest thing to deploy.
• React — Vite with React 19, built and served as static output.
• Python — a Python 3.12 script.

The starter only decides what exists on day one. Ask for anything afterwards — Go, Rust, Ruby, PHP — and the agent will write it, though running something other than Node needs Docker on your target.

Type what you want in plain language. The agent writes real files, and you can open any of them in the file tree while it works. There is a Stop button beside Build if a turn is taking too long.

Prompts that work well are specific about three things:

• What it is — “a pricing page with three tiers” beats “make a website”.
• What it should do — where data comes from, what happens on submit.
• What it should look like — or ask it to follow a reference.

Keep asking for changes in the same conversation. The agent remembers the project, so “make the buttons bigger” works without re-explaining what you built.

Open an app, then the Servers panel at the bottom and choose + add destination. The provider does not matter — an AWS EC2 instance, an Azure VM, a Google Cloud, Alibaba Cloud or Oracle Cloud instance, a VPS from DigitalOcean or Hetzner, or bare metal are all the same two things. You need:

• Public IP address — the address you would type to SSH in.
• Private key — the .pem file from your cloud provider. Use the file picker rather than pasting it.

We never ask for a password, because we cannot store one safely and a key is better anyway.

Saving connects once and tells you what it found: the login name that worked, the operating system, whether Docker is present, and whether Node is. If there is no Docker you get the exact commands to install it, for that server’s distribution — paste them into your own SSH session. Vokong never installs software on your machine.

Anything else — a different port, an unusual username, a remote path — is behind Advanced, and the defaults work on most servers.

No server? Use a free static host. For an app that is browser-only — the Website and React starters — the same panel can publish to Cloudflare Pages or Netlify with no server of yours at all: pick that kind, paste an API token, and Vokong verifies it and creates the project in the same step. Deploys then land on a public URL that serves your files from their worldwide network. Server apps — anything with a backend or database — still need your own machine, because those services only serve files.

There is no Deploy button, on purpose. Once your server is registered you say so in the chat:

• “deploy it” — publish to the server you registered.
• “deploy it as yearly” — pick a specific server when you have more than one.
• “push the update” — redeploy after a change.

The agent builds the app, uploads it, starts it and reports back with an HTTPS URL and a free certificate. Ask again after any change and it ships the update over the top.

If your server has Docker the app runs as a Compose stack. If it does not, the agent runs it as a plain Node service instead and restarts it automatically if it dies.

To a static host instead, the agent uploads the built app — a Vite project is built first, the workspace itself is published for a plain site — and answers with the versioned URL. Ask “push the update” again after changes; only files that changed are uploaded twice.

You need ports 22, 80 and 443 open in your cloud provider’s firewall, not just on the machine. Nothing outside your provider’s control panel can do that for you. Static hosting needs none of that — only the API token.

Just ask: “add PostgreSQL to this app”. A real database comes up alongside it and stays put across redeploys.

The password is generated on your server at deploy time and written into an environment file there, never into your workspace or your code. Your agent cannot read it.

Add your provider key under Settings → API key. It is encrypted before it is stored and never shown to you again.

Choose which model the agent uses from AI Settings, grouped by provider. On the free plan the agent may only use models that cost nothing, which is a working catalogue rather than an empty one. That is the free plan as designed, not a countdown: it never expires, and publishing to Netlify or Cloudflare Pages costs nothing there either.

Scroll to Pricing and pick a plan. You are sent to PayPal, approve there, and come straight back. The card details never touch this site — we are told a subscription id and a status, and nothing else.

• Monthly — $6 a month.
• Yearly — $60 a year, two months cheaper than paying monthly.

If you cancel at PayPal’s approval page, nothing was charged and your trial is untouched.

Settings → Billing shows what you are on, when your trial or period ends, and a cancel button.

Cancelling stops the next charge immediately. It does not remove the period you have already paid for, so you keep everything until that runs out.

When the trial ends the account drops to the free plan — and the free plan never expires. Your apps, files and anything already deployed stay exactly as they are; the agent keeps working on the free models, and publishing to Netlify or Cloudflare Pages remains available. Subscribing adds your own SSH servers, PostgreSQL and the full model catalogue.

Almost every problem is one of these four:

• “Permission denied (publickey)” — that key is not in the server’s authorized_keys. Confirm the file you uploaded belongs to the instance you typed — a .pem is specific to one machine, and reusing one from a deleted instance is the usual cause.
• The deploy succeeded but the URL does not resolve — ports 80 and 443 are closed in your cloud firewall.
• “No servers are configured” — add one in this app’s Servers panel first.
• “Add an API key in Settings first” — the agent has nothing to run on until you add one.

Still stuck? Email janith@vokong.com with what you asked for and what came back.