Skip to main content

autodeploy-web — a Docker web UI to build Veeam ISOs, deploy full topologies, and generate REST wiring scripts (beta testers wanted)

  • June 22, 2026
  • 6 comments
  • 94 views

Baptiste Tellier
Forum|alt.badge.img+4

Hi all,

Edit 10/09/2026 : it’s now live with 13.1 :) !

I've been working on a community side-project, autodeploy-web, and I'd love feedback from people who run Veeam labs.

It's a single Docker container (the only host dependency) that bundles three workflows behind one web UI:

1. Customise a Veeam Software Appliance ISO — a web form on top of the autodeploy PowerShell script (kickstart/GRUB/MFA/license baked in). No PowerShell or WSL needed on your machine; the form's JSON round-trips with the script. 

2. Deploy a whole topology — pick a layout (VSA, VSA + VIA proxy, VSA + hardened repo, HA pairs…), point it at a hypervisor, and it provisions the VMs and wires everything into the VSA over the B&R REST API: adds managed servers, registers proxies, creates hardened repositories, installs the license, builds the HA cluster, and can add S3 / node_exporter / syslog. Two boot modes: pre-customised ISO, or remote kickstart (it injects the GRUB command over the hypervisor console). Back-ends: Proxmox VE, Workstation & Hyper-V are validated; vSphere almost, Nutanix AHV and XCP-ng are implemented but need real-world testing.

3. Craft API — fill the same kind of form and it generates the exact, runnable REST wiring sequence as a PowerShell or curl script (token handling, session waits, certificate/fingerprint, license, S3, HA — auto-refreshing the token on expiry). Handy if you deploy appliances by hand but want the wiring scripted, or just to learn the VBR REST API.

 

What I'm after: beta testers — especially for the experimental hypervisors and the Deploy / Craft API flows — plus any feedback on real environments and edge cases.

It only work with VSA & VIA 13.1

Caveats: it's a lab tool with no authentication by design (so it must stay on a trusted LAN — never expose it to the internet), and it builds on top of autodeploy for all the ISO logic.

Open source under MIT.

Repo + docs: https://github.com/BaptisteTellier/autodeploy-web

Happy to answer questions here — and PRs / issues / "it broke on my setup" reports are very welcome. Thanks!

6 comments

Chris.Childerhose
Forum|alt.badge.img+22

I have read about your project and hope to test it out in my lab on VMware.  Will provide some feedback.


MateuszPawlinski
Forum|alt.badge.img

Hi ​@Baptiste Tellier, this caught my attention because I have recently used unattended VIA 13.1 deployment on Proxmox for a VCC environment.

I know VCC itself is still Windows-based, but have you considered using autodeploy-web to deploy VIA appliances and register them with an existing VCC server, especially as Cloud Gateways or WAN Accelerators?


Baptiste Tellier
Forum|alt.badge.img+4

Hi ​@MateuszPawlinski,

 

So far it is possible to deploy Proxy / HR repository role and wire them to a VSA already deployed.

you can then use the target VBR to enter your own VCC server : 
 

 

But it will wire it as proxy and not CGW our Wan Accelerator but you can do it yourself afterward

I don’t think i will find time to deploy a VCC windows based to build the correct Rest for CGW anytime soon


Baptiste Tellier
Forum|alt.badge.img+4

to make the matter worse, there is no RestAPI to add CloudGateway so nothing i can do :)


Stabz
Forum|alt.badge.img+9
  • Veeam Legend
  • September 8, 2026

 Hey ​@Baptiste Tellier 
 

Here is my feedback.

The ISO creation process works smoothly, which was expected since the non-web version was already performing very well.

Suggested improvement:

  • Provide the ability to edit the hosts file directly.

I also tested deployment to a vCenter environment. So far, I have tested the deployment VSA + Proxy deployment. It works!

Suggested improvements:

  • The current vCenter connection method only supports a local account. Adding support for VCF SSO authentication would be a valuable enhancement.
  • Add an option to select the destination datastore when uploading ISO files.
  • Display the available remaining storage capacity when selecting a datastore.
  • Sort network entries in alphabetical order.

Additional note:

  • For VSA + Proxy wiring/deployment, a valid license key is required. The deployment does not work in Community Edition mode, so this requirement should be clearly indicated in the workflow.
     

     

 


Baptiste Tellier
Forum|alt.badge.img+4

Thanks Philippe,

the deployment does not work in Community Edition

Well… VSA doesn’t work in Community Edition 🙄

 

What do you mean by  “Provide the ability to edit the hosts file directly.” ?

You want to alter dns host resolution of the VSA ?

if so, i’ll have to do that in the autodeploy powershell, will see thanks

 

Thanks for the vCenter feedback