Vibe VPS · unmanaged · IPv6 · KVM
Give the agent a machine of its own.
An AI agent with shell access does not work with the permissions of the task you gave it. It works with the permissions of the computer it is running on. A separate box narrows that to one project, and deploys it too.
Hosting infrastructure since 2003 · US / EU / India datacenters
Why this line exists
The agent inherits the machine, not the task.
Ask an agent to deploy one project and it acts with everything the computer can reach: every host in your SSH config, every token your CLIs have cached, every credential a sync client has copied somewhere for safekeeping. The instruction is scoped to one project. The access is not.
A key that opens ten servers opens ten servers
Reach is decided by what the machine holds, not by which server you meant. An agent that picks the wrong host is not misbehaving; it is using what it was given, and a development laptop is usually holding the keys to production as well.
One convenience can undo the isolation
Separate users and filesystem jails are real boundaries, and they hold right up until the same key gets added somewhere with more power to settle an unrelated problem. Nothing announces that the boundary is gone, and the setup still looks correct from the outside.
Deleting a key is not revoking it
A working machine keeps copies of things. Backups, synced folders, an old config from a laptop you replaced. Access removed in one place can be restored from another by anything thorough enough to go looking, which is a fair description of a capable agent.
A box you keep empty stays empty
The useful property of a separate machine is not that it is hardened. It is that your production keys were never copied onto it, your cloud tokens were never logged in on it, and no sync client is mirroring your home directory to it. The boundary holds because there is nothing on the other side of it.
Said plainly, because it is the part people get wrong: this is scope, not safety. An agent with root on a Vibe box can do anything on that box. The point is that the box holds one project, so that is all "anything" amounts to.
Working on it, day to day
Your laptop sleeps. The work does not have to.
The agent is a process. Processes want a machine that stays on, a connection they do not depend on, and an environment somebody can rebuild. A laptop is none of those things, through no fault of its own.
Always on
It keeps working when you stop
Close the lid, catch a train, go to sleep. A run started under systemd or tmux carries on without you, and the results are waiting. A laptop that suspends takes the agent down mid-task.
Connection
A dropped link ends the session, not the job
Wi-Fi drops, you switch to tethering, you move between buildings. The process is on the server, so you reattach to it. On a laptop the same interruption is a run you have to start again.
Headroom
Your machine stops competing with the build
Installs, test suites and container builds use the server's cores and disk rather than the ones running your editor, your browser and everything else you have open.
Rebuildable
An environment you can recreate
cloud-init brings a box back to a known state in minutes, so a broken experiment costs a rebuild rather than an evening. A laptop's setup is a one-off that nobody can reproduce exactly, including you.
Continuity
It outlives the laptop
Reimage the laptop, replace it, or leave it at home, and the box is untouched. You reconnect from whatever machine you have to hand and pick up where the agent left off.
Your backups
Somewhere a backup job can actually run
Backups are not included on this line, and that is part of why it is priced where it is. What a server gives you is a place to run your own: a nightly push to object storage happens whether or not you are at your desk, which is not true of a laptop that has to be awake to do anything.
¿Por qué no compartir alojamiento?
AI coding agents work over SSH, CLIs and APIs. cPanel-era shared hosting has no root, no systemd, no Docker, no Node. There is nothing for an agent to drive. A small VPS with root is the natural home for an AI-built app; the only question is what you pay for it.
Alojamiento compartido
Great for sites, wrong for apps
- Sin raíz, sin sistema, sin Docker
- Deploys by FTP or a file manager, not git push
- No SSH deploy path an agent can drive
- Lowest cost, if a managed website is what you need
- IPv4 included, and priced into every plan
Vibe VPS (this page)
Un servidor real en dinero compartido-hosting
- Arrastre completo, sistematizado, Docker, cualquier tiempo de ejecución
- SSH from second one: git push, rsync, scp
- Apto para el agente: 2 GB+ planes ejecutan el Código de Claude en el servidor
- From $3.49/mo, renewal price shown before you pay (plus GST where it applies)
- No IPv4 tax: IPv6-only, +$5/mo only if you need v4
Big cloud
Hetzner, DigitalOcean " co.
- Acceso a la raíz, igual que el nuestro
- Respetuoso con el agente, igual que el nuestro
- Entrada ~$4–7/mo, y IPv4 cuesta extra allí también
- Medidores de Egress y artículos de uso para ver
- Fine at scale, overkill for one small app
Cinco tamaños. Un precio plano cada uno.
Launch pricing, in USD. Promotional discounts apply to your first term; your renewal price is shown before you pay, with no surprise in year two. Every plan is IPv6-only; a dedicated IPv4 is an optional $5/mo on any of them. 18% GST applies at checkout for billing addresses in India.
Vibe Nano
$3.49/mo
Agentes de cron, bots de Telegram/Discord, una pequeña aplicación de Flask o Express.
- 1 vCPU · 1 GB de RAM
- 15 GB NVMe
- 1 transferencia de TB
- /64 IPv6 subnet
- Inicio completo · KVM
+ Dedicated IPv4: $5/mo (optional)
Despliegue ahoraVibe Micro
$4.99/mo
One production Node or Python app plus its database: the shared-hosting replacement. Meets the minimum spec for running Claude Code on-server.
- 1 vCPU · 2 GB de RAM
- 25 GB NVMe
- 2 TB transfer
- /64 IPv6 subnet
- Inicio completo · KVM
+ Dedicated IPv4: $5/mo (optional)
Despliegue ahoraVibe Dev
$9.99/mo
Docker, Next.js/Vite builds: run your app and your coding agent side by side.
- 2 vCPU · 4 GB de RAM
- 50 GB de NVMe
- 4 transferencia de TB
- /64 IPv6 subnet
- Inicio completo · KVM
+ Dedicated IPv4: $5/mo (optional)
Despliegue ahoraVibe Pro
$15.49/mo
Aplicaciones múltiples, empleos de CI, 2-3 agentes concurrentes.
- 3 vCPU · 6 GB de RAM
- 80 GB NVMe
- 6 transferencia de TB
- /64 IPv6 subnet
- Inicio completo · KVM
+ Dedicated IPv4: $5/mo (optional)
Despliegue ahoraVibe Max
$20.99/mo
Caja dev de equipo, orquestación multi-agente, construcciones pesadas.
- 4 vCPU · 8 GB de RAM
- 120 GB de NVMe
- 8 transferencia de TB
- /64 IPv6 subnet
- Inicio completo · KVM
+ Dedicated IPv4: $5/mo (optional)
Despliegue ahoraCada plan: KVM virtualization · NVMe storage · full root · /64 IPv6 subnet · SSH key injected at provisioning · cloud-init · 1 Gbps port · self-service reinstall & reboot · your choice of India, US West, US Central or Germany at no difference in price · 17 images: Ubuntu, Debian, AlmaLinux, Rocky, openSUSE, or Windows Server (bring your own licence) · optional AI-Ready image (Node.js 22, Python 3.12, Docker, git, tmux preinstalled).
You hold root: the OS and everything on it is yours to run. That is the point of this line, and part of why it costs what it does. Backups and application support are not bundled; add your own, or take a managed line and we run it for you.
IPv6-sólo, explicado honestamente
A public IPv4 address now costs real money every month; IPv6 costs practically nothing. We skip the IPv4 tax and pass the difference on; that is the cost secret behind these prices. Here is exactly what it means in practice.
Inbound · your visitors
Los visitantes de las redes IPv4 solo pueden llegar a su sitio: ponga el proxy Cloudflare libre delante de su origen IPv6 y respuestas Cloudflare en ambos protocolos mientras su servidor permanece v6 solo. Arréglalo una vez, olvídalo.
Outbound · your server
Your VPS reaches any IPv6-enabled service directly: npm, PyPI, the Anthropic API, most CDNs. Some services are still IPv4-only, most notably GitHub. Your options:(a) add a dedicated IPv4 for $5/mo (the recommended path),(b) utilizar un resolución NAT64 público, o(c) use alternativas IPv6-native como GitLab o Codeberg.
The $5 answer
If your workload needs SMTP, github.com, or a v4-only API every day, add the dedicated IPv4 and be done with it. You pay for the address only if you need one, which is why the plans start where they do. It is the clean fix, and the one we recommend.
Bring your own tool · Claude Code · Cursor · Codex · Copilot · Lovable
Funciona con lo que sea que vés código en
Build in your IDE, your terminal, or your browser; the VPS is the deploy target your tool drives over SSH. You talk to your agent; your agent talks to the server.
# once per server: takes a minute, works for every tool, any OS
# 1) order with your SSH public key; it is on the box at first boot
# 2) add these three lines to ~/.ssh/config (Windows: C:\Users\you\.ssh\config)
Host vibe
HostName 2001:db8:your:v6::1 # your /64 address, or the $5 dedicated IPv4
User root
# 3) you're in: any terminal, PowerShell included
ssh vibe uname -a
# or skip the typing: paste this card into your tool and tell it to set this upCódigo de Claude
Works from your laptop, or lives on the server. Either way it speaks SSH natively.
My server is "ssh vibe" (Ubuntu 24.04, root, IPv6-only).
Clone <repo-url> into /root/<your-app>, install production deps,
run it as a systemd service named <your-app> on port 3000,
and verify it survives a reboot.- Micro and up (2 GB+) meet Claude Code’s on-server minimum; Nano is fine while the agent stays on your laptop.
- Las imágenes de AI-Ready nodo 22, Python 3.12, Docker, git y tmux, por lo que la cadena de herramientas está allí antes de su primer impulso.
Or install it on the box
# first login: the AI-Ready image ships Node 22, Python 3.12, Docker, git, tmux
ssh root@your-vps
# put your coding agent on the box
npm install -g @anthropic-ai/claude-code
# pull your app (IPv6-native host, or add the $5 IPv4 for github.com)
git clone https://gitlab.com/you/your-app.git && cd your-app
npm install
# make it a service that survives reboots
cat >/etc/systemd/system/your-app.service <<'EOF'
[Unit]
Description=your-app
After=network.target
[Service]
WorkingDirectory=/root/your-app
ExecStart=/usr/bin/node server.js
Restart=always
[Install]
WantedBy=multi-user.target
EOF
systemctl enable --now your-appCorre claude there and your agent no longer needs your laptop; bots and crons keep working after you close the lid.
Cursor
Cursor’s agent runs terminal commands, SSH included. Deploys happen from the editor you already live in.
Deploy this project to my VPS: host "vibe", path /root/<your-app>.
rsync the repo, install production deps, create or restart the
<your-app> systemd service, then curl http://localhost:3000
and show me the output.- Approve the agent’s command execution when it asks; the SSH alias means it never touches credentials.
- Primer despliegue: añadir “crear la unidad sistematizada también” al impulso; después de eso , una redistribución es una frase.
Codex
Los mismos dos modos que Claude Code: conduzca la caja desde su máquina, o instale el CLI en el servidor.
My server is "ssh vibe" (Ubuntu 24.04, root, IPv6-only).
Clone <repo-url> into /root/<your-app>, install production deps,
run it as a systemd service named <your-app>,
and confirm it restarts after a reboot.- El Codex CLI instala en cualquier plan de 2 GB+ para la misma autonomía siempre en la caja que Claude Code.
Copiloto
VS Code’s Remote-SSH opens the VPS itself; Copilot agent mode edits and runs directly on the server. There is no deploy step.
(inside a Remote-SSH window connected to "vibe")
Set this app up to run as a systemd service on this machine,
start it, and show me the output of systemctl status.- Install the Remote-SSH extension, connect to “vibe”, open /root/<your-app>; the integrated terminal is the server’s own shell.
- Cloning from github.com needs the $5 IPv4 or a GitLab/Codeberg mirror, because github.com has no IPv6.
Lámpara
Your app can leave Lovable: the code it writes is a standard React/Vite app, and this is its own server.
Clone <repo-url> on my server "ssh vibe", build the Vite app,
and serve dist/ on port 80; set it up so it survives a reboot.- Activar GitHub sincron primero (pagado planes Lámparas; el plan libre exporta un ZIP que puede empujar a un repo usted mismo).
- The Supabase backend stays managed; only the frontend moves. Point your domain at the VPS and proxy through Cloudflare so IPv4 visitors reach it.
- github.com has no IPv6, so mirror the repo to GitLab/Codeberg or add the $5/mo dedicated IPv4.
The point stands on every tab: you never type the server commands yourself; your tool does.
¿Qué hay en la caja?
NVMe
Almacenamiento real NVMe
No “SSD-backed”, no caché la oxidación de la columna. Sus construcciones, instalaciones y bases de datos se sientan en NVMe.
KVM
virtualización de KVM
A real virtual machine with its own kernel. Run Docker, WireGuard, whatever needs more than a container.
IPv6 /64
Subnet de /64 por servidor
Billions of addresses to yourself. One per app, per container, per experiment. No port juggling.
cloud-init
soporte de inicio de nube
Traiga datos de usuario: scripts de primer arranque, usuarios, paquetes. Reconstruido a un estado conocido en minutos.
OS
Your choice of OS
Ubuntu 26.04 back to 18.04, Debian 13 back to 10, AlmaLinux 10 · 9 · 8, Rocky 9, openSUSE 16: clean images, no vendor bloat. Windows Server 2019–2025 is available on a bring-your-own-licence basis; the images are Microsoft evaluation builds that you activate with your own licence.
Region
Four regions, one price
India, US West, US Central or Germany, chosen at checkout. No region costs more than another. Put the box near your users, or near the APIs it talks to.
AI-Ready
Imagen opcional AI-Ready
Node.js 22, Python 3.12, Docker, git and tmux preinstalled, so your agent gets a working toolchain on first SSH.
Red
1 puerto Gbps
Cada plan, cada tamaño. Las prestaciones de transferencia son para el tráfico real, no tropezaron con trucos.
Instant
Suministro instantáneo
Order, pay, SSH in. Reinstall and reboot are self-service from the panel, no ticket.
SSH keys
Keys injected at provision
Tu llave pública está en la caja antes de la primera bota. No hay emails de contraseña para interceptar.
Preguntas
¿Qué es el alojamiento de aplicaciones codificadas por vibración?
Vibe coding is building software by directing an AI coding agent (Claude Code, OpenCode, Codex CLI) instead of typing every line yourself. What comes out of it is a real Node.js, Python or Go app that needs a real server: SSH, a process manager, a runtime you control. These plans are exactly that: small, cheap KVM servers with full root that your agent can deploy to directly. Shared hosting can’t take a git push; big-cloud setups are overkill for one app. This is the middle.
¿Qué herramientas de codificación AI funcionan con esto?
All of them that can run a shell command; SSH is the whole interface. Claude Code and the Codex CLI can deploy from your laptop or run on the server itself; Cursor’s agent deploys over SSH from the editor; GitHub Copilot works directly on the box through VS Code Remote-SSH; Lovable apps export to GitHub and build here like any Vite project. If your tool isn’t on that list it almost certainly still works: give it “ssh vibe” and tell it what you want running.
¿Qué significa "sin manejar" aquí?
We run the physical hosts, the network and the virtualization layer, and hand you a clean OS with your SSH key injected. Everything inside the VM (updates, hardening, your app, your data) is yours to run. Support on this line covers the machine and the network rather than the software you put on it; if you would rather we ran the whole box for you, that is our Managed Cloud VPS.
¿Están incluidos los respaldos?
Not on this line. These plans are priced without them, which is part of how they stay this cheap. Ship your data off the box yourself: restic, rsync or object storage, and your agent can set it up on day one. If you would rather it were handled for you, our managed lines include backups.
When do I need the $5/mo dedicated IPv4?
Three common reasons: sending mail directly over SMTP, pulling from github.com, and calling the shrinking set of APIs that never got IPv6. Inbound is already solved without it: put Cloudflare’s free proxy in front of your IPv6 origin and visitors on IPv4 networks reach your site fine. If none of those three apply to you, you may never need it.
¿GitHub trabaja desde un servidor IPv6 solo?
github.com is still IPv4-only, so a plain git clone won’t reach it from a v6-only box. Your options: add the dedicated IPv4 for $5/mo (the simplest fix, and our recommendation), route through a public NAT64 resolver, or keep your repos on an IPv6-native host like GitLab or Codeberg. We don’t run a NAT64 gateway, so that middle route is one you would set up yourself.
¿Cuál es la política de reembolso?
A 30-day money-back guarantee: if the server is not right for you, tell us within 30 days of signing up and we refund your fee. A dedicated IPv4 add-on and any third-party charges are excluded.
¿Hay una política de CPU de uso justo?
Yes; the exact wording is being finalised for launch. The intent: run real apps, bots, builds and agents around the clock without worry. What it exists to stop is pegging every core for days on end. That is dedicated-server territory, and we will point you there honestly.
Dale a tu agente un servidor real.
From $3.49/mo, provisioned in minutes. Not sure which size fits your app? Tell an engineer what you're running, and a human answers.