Your app. Your code. Deploy anywhere.
Own every app you build with WeWeb. Go live in one click or download your code and run it on your own servers. No lock-in.
Trusted by Fortune 500 companies & scaleups
Ready to ship? Choose how

Path A
One click deploy on WeWeb's infrastructure
Ship on your custom domain from day one.
Test on staging, push to production, roll back any version in one click.
Fire webhooks, CI jobs, or integrations automatically after every publish.
No servers, no config, no DevOps. We handle the infrastructure so your app loads fast everywhere.
Best for: Teams that want to move fast and not think about infrastructure.

Path B
Export and self-host a standalone Vue.js SPA
Export your complete app: pages, components, workflows, styles, and assets in one production-ready build.
Run independently on any infrastructure with zero WeWeb dependencies.
Self-host on AWS, GCP, Azure, Cloudflare, or on-premise. Follow step-by-step guides for every major provider.
Push to GitHub and plug into your existing CI/CD pipeline.
Best for: Teams that need infrastructure control and data sovereignty.
" We knew this project would require a top-tier tool (like WeWeb) to handle the scale of a nationwide broadcast and meet TF1’s strict requirements. They wanted full control over hosting and infrastructure, with no dependency on proprietary platform servers."
Maxime Brunet
Founder @ Shunpo
Founder @ Shunpo

Built for builders who want control from build to deployment
" I kinda expected that I could only build a MVP using no-code, and then switch to developers and a fully-coded solution. But with WeWeb, I think I can scale endlessly. "
Kyan Lynch
CEO @ Aloe Digital
CEO @ Aloe Digital

FAQs
Which plans include code export and self-hosting?
Every paid plan, starting at $20/month.
Code export isn't gated behind an enterprise tier or paid as an add-on. Once you have an active seat subscription, you get unlimited exports.
Your hosting plan's visitor and bandwidth limits (50,000 monthly visits, 200 GB) only apply to WeWeb's CDN. Once you self-host, those limits are irrelevant because your app runs on your own infrastructure.
Code export isn't gated behind an enterprise tier or paid as an add-on. Once you have an active seat subscription, you get unlimited exports.
Your hosting plan's visitor and bandwidth limits (50,000 monthly visits, 200 GB) only apply to WeWeb's CDN. Once you self-host, those limits are irrelevant because your app runs on your own infrastructure.
Can I start on WeWeb's CDN and self-host later?
Yes. Many teams publish to WeWeb's CDN while iterating, then export and self-host when they need infrastructure control, data sovereignty, or to fit into an existing deployment pipeline.
A few things to know before you switch: files uploaded to WeWeb's CDN are not preserved when you self-host, so set up your own storage (S3, Supabase Storage, Cloudflare R2) before transitioning. And review your plugins for microservice dependencies so nothing breaks on the other side.
A few things to know before you switch: files uploaded to WeWeb's CDN are not preserved when you self-host, so set up your own storage (S3, Supabase Storage, Cloudflare R2) before transitioning. And review your plugins for microservice dependencies so nothing breaks on the other side.
Does my exported app depend on WeWeb to run?
No. Zero runtime dependencies.
Once exported, your app runs independently on whatever infrastructure you choose. Custom domains are configured through your hosting provider, not through WeWeb.
You can host the root domain, a subdomain, or multiple white-labeled domains from the same export. If WeWeb disappeared tomorrow, your deployed app would keep running.
Once exported, your app runs independently on whatever infrastructure you choose. Custom domains are configured through your hosting provider, not through WeWeb.
You can host the root domain, a subdomain, or multiple white-labeled domains from the same export. If WeWeb disappeared tomorrow, your deployed app would keep running.
Where can I self-host?
Anywhere that serves static web content. AWS, GCP, Azure, Cloudflare, Digital Ocean, Netlify, Vercel, on-premise servers, or air-gapped environments with no internet access.
Step-by-step guides are available for the most common providers. Headers and redirects are configurable in your project settings and travel with the export, so custom routing and security headers follow your app to any host.
Step-by-step guides are available for the most common providers. Headers and redirects are configurable in your project settings and travel with the export, so custom routing and security headers follow your app to any host.
Can I use GitHub and my own CI/CD pipeline?
Yes. Export your app, push to GitHub, and plug into your existing deployment workflow.
Every re-export generates a fresh build you can commit, review, and deploy through the same CI/CD process you use for the rest of your stack.
Monitoring and observability are up to you: WeWeb doesn't provide built-in monitoring for self-hosted apps, but any standard frontend tooling (Sentry, Datadog, your own logging) works with the exported app.
Every re-export generates a fresh build you can commit, review, and deploy through the same CI/CD process you use for the rest of your stack.
Monitoring and observability are up to you: WeWeb doesn't provide built-in monitoring for self-hosted apps, but any standard frontend tooling (Sentry, Datadog, your own logging) works with the exported app.