Tools
Automated Linux and cloud server setup
Cloud-init configuration generator
Every new VM or cloud instance usually needs the same handful of steps right after boot - a user account, an SSH key, some packages, network settings. Doing that by hand is easy to skip and hard to repeat identically on the tenth machine the way you did on the first. This generator builds a correct cloud-init file (user-data) for you, locally in your browser, and suggests a safer approach where it applies - SSH-key-only access instead of a password, for instance.
Everything runs in your browser. Nothing you enter is sent to a server.
How it works
- Describe how this machine should look. User account, SSH key, packages, network.
- See the user-data file before you download it. The preview updates as you go.
- Download it and attach it to your VM or cloud instance. cloud-init takes care of the rest on first boot.
Step 1 of 8
Step 1 of 8
System identity
The machine's hostname, locale and time zone.
You already have a working file - tune it below
Machine
System hostname written to meta-data and used for /etc/hostname via cloud-init.
Sets the keyboard layout and time zone. You can change either below.
Set from your language
XKB keyboard layout code, e.g. us, pl, de.
IANA timezone name, e.g. Europe/Warsaw, UTC.
Unknown time zone
For AI agents / automation
This tool is 100% client-side and free to use - it runs entirely in the browser, no sign-up, no server calls.
The full input schema is published at a stable URL: /tools/cloud-init-schema.json
How to use it programmatically: build a JSON object matching that schema. Then either open the page and paste it into the "Import JSON config" box to get user-data/meta-data/network-config, or reimplement the pure, dependency-free functions generateUserData(config) / generateMetaData(config) / generateNetworkConfig(config) from src/lib/cloud-init/generate.ts directly in your own code.
Minimal example:
{
"hostname": "web-01",
"locale": "en_US.UTF-8",
"timezone": "UTC",
"userNames": [
"ubuntu"
],
"userSudoNopasswd": [
"true"
],
"userSshKeys": [
"ssh-ed25519 AAAA..."
]
}Alternative for MCP-capable agents: instead of pasting JSON, an agent can call the "generate_linux_cloud_init" tool on our MCP server (Streamable HTTP) at /mcp directly. Unlike the JSON workflow above, the "nothing is sent to a server" promise does NOT hold here - an MCP tool call necessarily reaches our server to generate the files. Nothing is logged or stored, but do not send real SSH keys, password hashes, or secrets this way unless you are comfortable with that.