Skip to main content
React · Node · Python · Static sites · Deploy anywhere

AI app builder · no local setup

Describe the app,
get the real code

Tell Vokong what to build in plain English. An agent writes it into a folder you can see, file by file — then hands you a Dockerfile so you can deploy it to your own AWS or Azure account. Nothing is hosted on our side, and nothing is locked in.

Bring your own API key · Free tier available · Deploy to your cloud

Live

my-app / agentBuilding
Build a pricing page
src/components/Pricing.tsx
src/styles.css
Dockerfile

What it actually looks like

Real files, not a chat log

The agent works in a folder you can open. Every file it writes is visible as it happens, and the whole tree is yours to keep, edit, or throw away.

App folders4 projects
  • Pricing pageReact · 12 files
  • Invoice toolNode · 8 files
  • Landing siteStatic · 6 files
  • Report scriptPython · 4 files
AgentWorking
Add a dark mode toggle
Editing src/components/Header.tsx
  • Added a state hook and class toggle
  • Updated the CSS variables
  • Kept the existing breakpoint intact
Your filesUpdated live
▾src/
▾components/
·Pricing.tsx
·Header.tsx
·styles.css
·Dockerfile
·deploy.md
Built
From a sentence

Describe it in plain English, get a working project

Yours
Every file

The whole folder is downloadable and yours to keep

Deployed
Your cloud

Dockerfile included — ship to AWS, Azure or anywhere

Private
Yours only

Every query is scoped to your account. Always.

Everything it does

From blank folder to deployed app

An agent that builds

Ask for a pricing page, a CSV parser, a whole dashboard. It writes real code into real files instead of pasting a snippet for you to assemble.

  • Runs on a real filesystem
  • Iterate — ask for changes
  • Remembers the project context

A folder per project

Every app gets its own folder, seeded with a starter that matches what you want to build — React, Node, Python, or a plain static site.

  • React · Node · Python · Static
  • Separate workspace each
  • Nothing bleeds between projects

See every file, live

A proper file tree, not a chat transcript. Expand it, open any file, and watch new ones appear the moment the agent writes them.

  • Expandable directory tree
  • Click any file to read it
  • Refreshes as the agent works

Ships with a Dockerfile

Each project is a real project root with a Dockerfile, .dockerignore and a deploy.md of real commands for AWS, Azure, GCP and Fly.

  • One image, any platform
  • ECS · App Runner · Container Apps
  • Health endpoint for probes

Your key, your bill

Bring your own OpenRouter or Plugsky key and the agent runs on your account. We never see the bill, and your key is stored encrypted.

  • AES-256-GCM at rest
  • Free tier available
  • Removed the moment you delete it

Sandboxed, properly

The agent runs as an unprivileged user in a bubblewrap sandbox. It can see its own project folder and nothing else — no database, no other users' work.

  • Isolated per project
  • No access to site settings
  • Secrets stripped from its environment

Your infrastructure, not ours

Deploy to your own cloud

Vokong hosts nothing publicly. Every project is a folder with a Dockerfile in it, which is the common denominator across all the platforms below — build the image once, run it wherever you like, billed to your account.

  • No vendor lock-in — it's a container, not a proprietary export
  • Secrets set on the platform, never baked into the image
  • A /health endpoint for load balancers to probe
  • deploy.md ships with the actual commands, not placeholders
Runs onAny OCI runtime
  • AWSECS Fargate · App Runner · ECR
  • AzureContainer Apps · App Service
  • Google CloudCloud Run · Vertex
  • Fly · Render · RailwayOne-command deploys

One line, from your project folder

docker build -t myapp . && docker run -p 8080:8080 myapp

How it works

Three steps to a deployed app

01

Make a folder

Pick a starter — React, Node, Python or a blank static site. Your project root, ready to build into.

02

Describe the app

Tell the agent what you want in plain English. Watch the files appear in the tree as it writes them.

03

Deploy it anywhere

The Dockerfile is already there. Build the image and run it on your own AWS or Azure account.

Questions

Frequently asked

Do I need a paid AI subscription?

No. OpenRouter has a free tier that needs no card, and adding a key from there costs you nothing. Vokong doesn't bundle or resell model access — you bring a key, you pay that provider directly.

Why can't I use OpenCode's own free models?

OpenCode restricts its free tier to its desktop and terminal apps. The agent here runs headless on a server, so those models refuse every request. That's why Vokong routes through providers that don't apply that restriction.

What can the agent see?

Only its own project folder. It runs as an unprivileged user inside a sandbox with no access to your database, other users' work, or the site's settings — and no secrets in its environment.

Who owns the code it writes?

You do. The files sit in a folder on a filesystem. Download them, edit them by hand, put them in git — there's no proprietary format and nothing to export.

Do you host my app?

No, and that's deliberate. Every project gets a Dockerfile, so you build the image and run it on your own AWS, Azure or any other account. We never see that bill.

Is this free?

Vokong itself is free while it's in beta. No card required. Model usage is separate and billed by whichever provider your key belongs to.

Describe it. Watch it get built.

Make a folder, tell the agent what you need, and get a real project you can read, edit and deploy. No card required to start.

Vokong — describe the app, get the code