claudetohost
validatebuilddeploylive
claudetohost > dist.zip 412 kB validate ok 38 files, no symlinks, root `dist/` stripped deploy ok nginx · tenant-4f7a20c91e3b live https://4f7a20c91e3b.apps.bastiencantet.com

A folder in. A URL out.

You built something with Claude and it works on your machine. This is the part that turns it into an address you can send someone — on real Kubernetes, with HTTPS, in about a minute.

How it works

1
Drop it
A zip or a tarball. We unpack it in memory, reject anything that escapes its own folder, and re-pack it into one canonical archive.
2
We place it
A namespace of your own, a deployment, a service, an ingress, and a certificate issued for your hostname.
3
It answers
Your URL serves over HTTPS and keeps serving — through restarts, reschedules and node drains.

What it can host

Static site

A built front end — Next export, Vite, Astro, or plain HTML. Nothing runs, so nothing can misbehave: the files are simply served.

Packaging →

HTTP service

A Node or Python API that listens on a port and answers a health check. Gets a service, an ingress and readiness probes.

Packaging →

Worker or bot

A Discord bot or a queue consumer: no port, no public surface. It gets a deployment and nothing else, and is restarted if it dies.

Packaging →
3
workload profiles: static, service, worker
HTTPS
a certificate issued per hostname
non-root
containers, with no cluster credentials