Agent
Deploy and live links
Put a project online at a velork.dev link anyone can open. The agent sets up the first deploy, and later updates take one click.
Deploy puts your project online at a public link on velork.dev, such as https://my-app-x1y2.velork.dev. Anyone with the link can open it. Velork builds and hosts it for you, so there's no server to set up.
The first deploy is the agent's job: it works out how to build and start your project, then saves what worked in a velork.deploy.json file. Every later deploy follows that file, with no AI needed.
You need to be signed in to Velork to deploy.
Open Share
Use either of these:
- In full-screen chat, click Share in the title bar. It shows when the project looks like something you can put online, for example it has a
package.json, anindex.html, aDockerfile, or avelork.deploy.json. - Run Share a Live Link (Deploy) from the Command Palette (Cmd + Shift + P)
The card deploys the folder of the chat you're in, or the window's first folder.
You can also ask in chat:
Deploy this project and give me the link.
Deploy for the first time
- Open Share and click Deploy
- The agent uploads the project to a build machine, finds the build and start commands, and publishes it
- When it's done, the agent gives you the link, and Share shows it
If the project already has a velork.deploy.json, Deploy builds it straight from the file instead of asking the agent.
While a deploy runs, Share shows each step with its time: Upload, Build, Start (or Publish for a static site), and Live. During the build you see the last lines of its output.
Share the link
| Action | What it does |
|---|---|
| Click the link, or Copy | Copies the link |
| Open button | Opens the link in a browser tab beside the chat |
| Update | Publishes the project as it is now. The link stays the same. |
| Change link | Picks the name in the link: [name].velork.dev |
| Turn off | Takes the link offline, after you confirm |
Status
| Status | Meaning |
|---|---|
| Live | Running, with when it was last updated |
| Asleep | An app that nobody used for a while. It wakes on the next visit. |
| Waking up… | Starting again after a visit |
| Not live yet | Hasn't finished a deploy |
| Turned off by Velork | Velork stopped it. The reason shows in its place when there is one. |
Static sites don't sleep. Opening Share or copying the link wakes a sleeping app, so it's ready when someone opens it.
Change the link
- Open Share and click Change link
- Type a name: lowercase letters, numbers, and dashes, at least 3 characters. Dashes go between letters or numbers, one at a time.
- Velork checks the name as you type. Click Save when it shows Available.
The old link redirects to the new one for 30 days. Choosing your own link is on Pro and Team. On Hobby, Velork shows Upgrade.
When a deploy fails
Share shows Deploy failed. or Update failed. with the first line of the error. Click Fix with AI: the agent reads the build output, fixes the problem, and deploys again.
velork.deploy.json
The file at the project's root says how to build and run it. The agent writes it on the first deploy, and you can edit it.
| Field | What it's for |
|---|---|
name | The app's name |
build | Build command, such as npm run build |
start | Command that starts the server |
port | Port the server listens on |
static | Folder to publish as a static site instead of running a server, such as dist |
spa | true for a single-page app, so every path serves the app |
envFile | A file inside the project with KEY=value lines, such as .env.production |
memoryMiB | Memory for the app |
{
"build": "npm run build",
"static": "dist",
"spa": true
}
Velork reads the envFile on your computer and sends the values with the deploy. They're never sent to the AI model. The file must be inside the project.
Velork uploads the project folder without its .velork folder.
Limits
Deployed apps count running time multiplied by memory, and traffic counts toward bandwidth. See Plans and usage for each plan's allowance.
Next steps
Preview
Run the app on this computer first
Built-in browser
Check the live site beside the chat
Plans and usage
Deployed app hours and bandwidth