Cloud infrastructure built for agents and applications

Vibe Coding and Vibe Shipping

Start from an idea and Shipping writes the code on your server or Fleet machine; bring a repository or your code and it deploys it as is. It sets up the server and, when the domain is on a DNS provider connected to Leaflow, the DNS record too. Then it sends you the link once the site is live.

Get started

MMy projectSearch resources and features, or ask⌘ K

Make me a website at blog.example.com.

Sure. I’ll create a 2 vCPU, 4 GiB instance in Hong Kong, write the site, serve it with Caddy and point blog.example.com at it. I’ll wait for your approval at each step.

Created instanceweb-012 vCPU · 4 GiB · Hong Kong
Wrote filesweb-01/srv/blog/3 files
Ran commandweb-01apt-get install -y caddy
Set recordblog.example.comA 203.0.113.10

Your site is live.https://blog.example.com

What do you want to do?

Confirm each change

DeepSeek V4.1 Flash· medium

Shipping
Fleet
Elastic Compute Service
Model API
Monitoring
DNS

National AI Application Scenario Innovation Challenge · Seed Track Grand Prize
GBA Youth Entrepreneurship Scheme · 2025–2028
Infrastructure partners: Alibaba Cloud · Volcengine

From idea to live

Vibe Coding and Vibe Shipping

Start from an idea. Shipping writes the code right on your server or Fleet machine, and the code stays on that machine.

Once there’s code, or when you bring your own repository, Shipping sets up the server and the DNS, puts it online as is and sends you the link.

index.htmlweb-01

Files on web-01
/srv/blog
index.html
style.css
posts/

1<!doctype html>2<html lang="en">3  <head>4    <meta charset="utf-8">5    <title>Field Notes</title>6    <link rel="stylesheet" href="/style.css">7  </head>8  <body>9    <header><a href="/">Field Notes</a></header>10    <main>11      <time>November 2026</time>12      <h1>Moving the blog to a $3 server</h1>

Wrote file/srv/blog/index.html

Shipping

In the Console, and in your chat apps.

More about Shipping

Shipping · chat apps

Ask Shipping in WeChat, and get the file back in the chat.

Connect Shipping to WeChat, WeCom, Feishu, Telegram or Slack. It can find files, run commands and use graphical apps on your Fleet machines, then send the result back to the chat.

It reads and writes files, runs commands, and clicks, types and takes screenshots in graphical apps.
Before it changes anything, it follows your setting: automatic review, confirm each change, or run directly.

WeChat · Shipping

Send me this week’s report from the office computer.

Found it in Documents/Reports. Sent.

Find files on office-pcmachine.find
Send to WeChatnotify.send

week-45-report.pdf286 KB

EventBus · Shipping tasks

When an instance stops, Shipping looks into it.

Leaflow services such as Compute and Fleet publish their changes as events on EventBus. Give Shipping an event task with the events and the condition to watch for, and it starts when a matching event arrives.

Filter events with a CEL condition. A cooldown of at least 10 seconds spaces out runs, and events in between join the next run.
Tasks can also run now, at a set time, on an interval or on a cron schedule.
EventBus is free and comes with every project.

Investigate stopped instancesEnabled

Event: leaflow.compute.instance.updated
Condition: data.status == "stopped"
Cooldown: 60 seconds
Prompt: Find out why the instance stopped. Start it again if that’s safe, then tell me why on WeChat.

Last run

Event received: web-01 stopped03:12:08
Operation log: shut down at 03:11 by the API key deploy-bot03:12:11
Waiting for you: start web-0103:12:16
Started. The details were sent to WeChat03:13:02

Shipping · Computer Use

Shipping can use the apps on your machines.

On Fleet machines with a virtual desktop, Shipping reads windows, clicks, types and presses keys, and lists every step in the chat.

This is Computer Use: Shipping operating the apps on your machine.
Your own agent can call the same tools through the Fleet API.

Shipping working in graphical apps on office-pc: each window switch, click, text entry and key press is listed alongside.

Fleet

Use your own machines from a browser.

Install the Fleet agent on a Linux machine and its apps open in their own windows in your browser, with copy and paste, files dragged in from your computer, sound and microphone.

Peer-to-peer, relayed when needed. Session content is end-to-end encrypted.
A web terminal and file manager at the bottom of every Console page.
sudo asks for approval in the Console instead of a password.

More about Fleet

A Fleet desktop session: the machine’s browser, file manager and text editor, each in its own window.

Switch computers and carry on.

Sessions keep running with nobody connected. The spreadsheet you opened at the office is still there on your computer at home.

Desktop sessionoffice-pcRunning

Open apps

LibreOffice Calc
Mozilla Firefox

Participants

Office laptopDisconnected18:02
With nobody connected, the session and its apps keep running
Home desktopConnected · Direct 7 ms21:14

Everyone signs in as themselves. No more shared root.

Bring members into the project and grant sign-in and sudo per person. Revoke access and their sessions end at once.

Accessoffice-pcCommonAllSign-in only

Member	Account	Sign in	sudo
a[email protected]	alice_example_com
b[email protected]	bob_example_com
c[email protected]	carol_example_com

Accounts come from the user directory, with the same username and UID on every machine; home directories are created at first sign-in.

Products

Built for AI, and for you.

Six products in one project. You work in the Console, Shipping works in chat, and your own agent works through MCP, the CLI and SDKs, all on the same API and the same permissions.

All products

Coming soon: multi-cloud connections (Alibaba Cloud, Volcengine, AWS) · domain registration · Sandbox · Agent Runtime

Your own agent

Or hand it to your own agent.

Connect the agent you use in your terminal through MCP, the CLI or an SDK. It acts as you, in the same project, with your permissions. Start the MCP server in read-only mode when you only need to look.

14
services: 585
API operations

The Console, Shipping, the CLI, MCP and the SDKs call the same API operations.

Connect your agent API reference GitHub

claude · mcp: leaflow

> How is web-01 doing this week? Any alerts?

⏺ leaflow · call-operation monitoring/list-incidents

⏺ leaflow · call-operation compute/get-instance

⏺ leaflow · call-operation monitoring/get-server-metric

One alert in the past 7 days, now resolved. web-01 is 2 vCPU · 4 GiB, averaging 12% CPU and 46% memory.

Every step in view

You set what the agent may do, and see what it did.

Visible: An AI cursor and a thin line along the edge show where the agent is working, and every step is listed in the chat.
Approval before changes: Before changing resources or calling outside services, the agent follows your setting: automatic review, confirm each change, or run directly.
sudo approved in the Console: sudo and graphical admin prompts on Fleet machines appear at the top of every Console page. Someone with permission approves them, or automatic review decides.
Access per person and machine: Decide who can sign in to which machine, and whether they can use the terminal, files, clipboard and printing.
Members and roles: Grant project members roles, or permissions on a single resource.
Operation log and task runs: Compute changes are kept in the operation log, and every Shipping task run is recorded.