1. Build or generate
Any static folder works: HTML, CSS, JS, images, fonts, and web manifests.
How it works
Push-to-deploy, you keep control.
Start with the open source wooven-publish CLI for instant static previews. Grow into Git-connected deployments, BYOS runners, and self-hosted control when the project needs sovereignty.
Current CLI flow
One command turns static output into a URL
The public CLI is intentionally boring: walk a folder, reserve a slug, upload files, finalize the publish.
2. Publish
The CLI uploads files over HTTPS and prints the exact live URL.
3. Iterate
Republish with a cached claim token to update the same slug.
curl -fsSL https://wooven.dev/skill/install.sh | bash
wooven-publish ./build
# ✓ live at https://meadow-aspen-x321fc.wooven.dev/Full platform direction
Same developer loop, more control over where work runs
The CLI is the wedge. The platform extends the same model to GitHub webhooks, preview URLs, custom domains, runners, and eventually heterogeneous compute.
Git-connected deployments
Push to a branch, get a preview URL. Push to main, promote the deployment. Git remains the source of truth.
BYOS runner pools
Bring your own VPS, Mac mini, Raspberry Pi, or hosted node. Wooven orchestrates; you own the compute boundary.
Sovereign edge
DNS, certificates, proxy labels, and routing keep the public URL stable while workloads can move across your own nodes.
Want the Vercel workflow without the Vercel dependency?
Join early access and help shape the runner, CLI, and BYOS flow before it hardens.
Join early access