Deploy VitePress in India
The docs:build script and the nested output directory, both detected. DataDack detects VitePress from your repository and deploys it to Mumbai, Pune and Noida edge PoPs — sub-15ms for Indian users, with DPDP data residency by default.
What we detect for VitePress
These are the exact defaults a VitePress repository with no configuration receives. Every one is overridable per project and per environment.
- Install command
- bun install --frozen-lockfile
- Build command
- bun run docs:build
- Output directory
- .vitepress/dist
- Toolchain
- Node 22
- Request handling
- Static · nothing runs per request
One real file per route, pre-rendered at build time and frozen at the edge. An unpublished path returns a true 404 instead of quietly serving the home page.
Three steps, no configuration
- 1
Connect the repository
Authorise GitHub once and pick your VitePress repo. Nothing to install locally, no CLI to log into.
- 2
VitePress is detected
We read the repository, identify VitePress, and pre-fill the build: bun run docs:build, publishing .vitepress/dist. Override any of it if your project differs.
- 3
Live on the Indian edge
Your Static workload is packaged, uploaded to Mumbai, Pune and Noida PoPs, and served over HTTPS with a certificate we issue and renew for you.
Included on every VitePress project
- A preview URL for every pull request
- Instant rollback to any build, no rebuild
- Automatic HTTPS with renewal handled
- Per-environment variables and secrets
- Custom domains with wildcard SSL
- Streaming build and runtime logs
- Build cache across deploys
- Monorepo support with a project root
VitePress deployment FAQ
Do I need to configure the build command for VitePress?
No. DataDack detects VitePress and runs bun run docs:build, publishing the .vitepress/dist directory on the Node 22 toolchain. You can override the install command, build command and output directory per project and per environment if your repository differs from the convention.
Where is my VitePress app hosted?
In India. Builds run in ap-south-3 and your app is served from Mumbai, Pune and Noida edge PoPs, giving sub-15ms latency to Indian users. Data never leaves Indian jurisdiction, which is what makes DataDack DPDP-compliant by default rather than by configuration.
How are unmatched routes handled for VitePress?
VitePress is a site generator, so it emits a real file per route and an unpublished path returns a genuine 404. We deliberately do not fall back to the index — that would return 200 and your home page for every typo and dead link.
Can I run preview deployments for VitePress pull requests?
Yes. Every pull request gets its own isolated preview URL with its own environment variables, and previews can be password-protected or SSO-gated. Instant rollback to any previous build is one click, with no rebuild.
Other site generators we deploy
VitePress official documentationDeploy on sovereign Indian cloud in minutes.
Pick a region, pick an image, hit deploy. No sales call, no lock-in - just sovereign infrastructure at half the AWS price.
🇮🇳 Crafted in India · Trusted Globally · Noida region live