exe.dev

Run OpenClaw on an exe.dev VM with HTTPS proxy. Shelley agent can auto-install, or use manual SSH setup.

exe.dev is a managed VM platform that provides instant cloud development environments with built-in HTTPS proxying. For OpenClaw, it offers two paths: an automated install via exe.dev's Shelley AI agent at https://exe.new/openclaw, or manual SSH setup using the standard installer script. Either way, you get a persistent VM with a public HTTPS URL in minutes. The Shelley auto-install is the frictionless path. Visit https://exe.new/openclaw and exe.dev's built-in AI agent provisions a VM, installs OpenClaw, and configures the HTTPS proxy — you don't touch a terminal. The resulting instance is accessible at https://<vm-name>.exe.xyz with automatic SSL, ready for the web setup wizard. This is arguably the fastest path from zero to a running OpenClaw instance in the cloud. For manual setup, SSH into your exe.dev VM and run the standard curl installer. exe.dev's VMs run exeuntu (a customized Ubuntu), so all standard Linux tooling works. The key advantage over a raw VPS is the built-in HTTPS proxy — exe.dev automatically routes traffic from your <vm-name>.exe.xyz domain to the gateway port, handling SSL certificates without any nginx or certbot configuration. This eliminates one of the most common pain points in self-hosted deployments. exe.dev VMs are persistent — your data and configuration survive reboots and stay available across sessions. The platform is designed for development workflows but works well as a lightweight hosting environment for always-on services like OpenClaw. The VMs provide SSH access for full control, which distinguishes exe.dev from PaaS options like Railway or Render that restrict terminal access. Pricing varies by VM configuration and is usage-based through exe.dev's subscription model. It's positioned between the simplicity of PaaS platforms and the control of raw VPS providers — you get SSH access and system-level control without managing the underlying infrastructure, OS updates, or SSL certificates yourself.

Tags: vps, managed, https, easy

Use Cases

  • Fastest possible cloud deployment via Shelley auto-install — zero terminal knowledge required
  • Developers who want a managed VM with SSH access and built-in HTTPS without reverse proxy configuration
  • Quick evaluation or demo of OpenClaw with a public HTTPS URL ready in minutes
  • Remote development environments where you need cloud-hosted OpenClaw alongside other dev tools
  • Users who want the control of a VPS with the convenience of managed HTTPS and SSL

Tips

  • Use https://exe.new/openclaw for the fastest possible cloud deployment — Shelley handles everything automatically
  • After auto-install, SSH in to verify the configuration and customize your SOUL.md and workspace
  • The built-in HTTPS proxy means you can skip all SSL/nginx setup — access the Control UI directly at https://<vm-name>.exe.xyz
  • Use SSH for manual configuration: exe.dev provides standard SSH access for full system control
  • Set up your messaging channels (Telegram, Discord, WhatsApp) through the web setup wizard at /setup
  • Keep backups of your ~/.openclaw/ directory in case of VM issues — standard rsync or scp works

Known Issues & Gotchas

  • exe.dev's HTTPS proxy routes through their infrastructure — all gateway traffic passes through exe.dev's servers
  • VM pricing and available configurations may change — check exe.dev's current plans before committing
  • The Shelley auto-install may configure defaults that differ from your preferences — review the setup after completion
  • exeuntu is Ubuntu-based but may have custom packages or configurations that differ from standard Ubuntu
  • VM persistence depends on your exe.dev plan — check whether VMs survive account inactivity periods
  • The .exe.xyz domain is managed by exe.dev — you can't use it with external DNS. Custom domains may require additional configuration

Alternatives

  • Railway
  • Fly.io
  • Hetzner VPS
  • DigitalOcean Droplet
  • Installer Script (local)

Community Feedback

exe.dev's auto-install with Shelley is wild. Visit a URL, an AI sets up OpenClaw for you, and you get HTTPS out of the box. The future is here.

— Reddit r/selfhosted

The HTTPS proxy on exe.dev removes the biggest self-hosting headache. No nginx, no certbot, no reverse proxy config. Just deploy and it works.

— Reddit r/AI_Agents

exe.dev is convenient but you're trusting their proxy with all your gateway traffic. For personal use it's fine. For anything sensitive, self-host behind Tailscale instead.

— Reddit r/selfhosted

Frequently Asked Questions

What is Shelley auto-install?

Shelley is exe.dev's built-in AI agent. When you visit https://exe.new/openclaw, Shelley provisions a VM, installs OpenClaw, and configures the HTTPS proxy automatically. You don't need to touch a terminal — it's the fastest path to a running cloud instance.

Do I get SSH access?

Yes. Unlike PaaS platforms (Railway, Render, Northflank), exe.dev provides full SSH access to your VM. You can install system packages, run custom scripts, and manage OpenClaw just like a regular VPS.

How does the HTTPS proxy work?

exe.dev routes HTTPS traffic from your <vm-name>.exe.xyz domain to the gateway port on your VM. SSL certificates are managed automatically. You don't need nginx, certbot, or any reverse proxy configuration.

Can I use a custom domain?

The default .exe.xyz domain works out of the box. Custom domain support depends on exe.dev's current features — check their documentation for the latest options.

How much does exe.dev cost?

Pricing varies by VM configuration and exe.dev's subscription model. Check their current plans at exe.dev for up-to-date pricing. It's generally positioned between raw VPS cost and full PaaS pricing.

Is my data persistent?

Yes, exe.dev VMs are persistent — your files, configuration, and OpenClaw state survive reboots and sessions. Check your plan's terms for inactivity policies.