Export code & self-host

In this article, you'll learn:

• How to export a project
• How to self-host a project

TIP

Code export and self-hosting is available on all paid plans with a yearly commitment.

Export a project

Once the export project feature has been added to your workspace, go to any published project's Settings > Deployments tab.

Click on the version of the app for which you'd like to export the code:

What if the download button is disabled?

Publish your project at least once to make it clickable.

Once downloaded, you'll find a zip file containing all your project's files (HTML, CSS and JS) ready to host anywhere you want.

Code export example

You can download an example project here with both raw and built files.

Self-host a project

You can self-host WeWeb projects anywhere you like!

Simply download the static files of your app as described above (i.e. the HTML, CSS and JS files of your WeWeb frontend), fire up a server and host the static files of your frontend there.

As an example, we've documented how you might self-host a WeWeb project on Cloudflare.

Frequently Asked Questions

How many projects can I export with one subscription plan?

One. Every project needs its own subscription plan.

I have a Starter plan, will the self-host option still be limited to 50,000 monthly app visits and 200 GB of bandwidth?

No. The exported code will run on your infrastructure, so none of the project plan limits apply.

How many times can I export my code?

You can export your code as many times as you want, for as long as you have an active yearly subscription.

Where can I self-host the exported application from WeWeb?

You can host the app on cloud hosting platforms like Amazon Web Services, Google Cloud Platform, Microsoft Azure, Cloudflare or Digital Ocean, as well as on managed hosting services platforms like Netlify.

Or you can self-host on your on-premise infrastructure—basically anything that can run a web server; an internet connection is not mandatory.

Will my backend still work after I export the code and self-host the app?

Yes. WeWeb is a frontend-only tool. Your backend remains separate and is not affected by exporting or self-hosting your WeWeb project.

When you self-host the exported app, the frontend will continue to make API calls to your backend, wherever it's hosted, just as it did before exporting.

How do I know which plugins have dependencies on WeWeb and which ones don't and can be fully self-hosted?

There are two self-hosting scenarios to consider:

A- Exporting your code and hosting it elsewhere (Recommended):

• Some plugins require communication with WeWeb microservices (Airtable, Google, Notion, OpenAI, SmartSuite, SQL, Stripe, SOAP)
• Direct connections to backends (e.g., Supabase, Xano, standard REST/GraphQL APIs) work independently of WeWeb.

B- Using the WeWeb server as a service (Deprecated):

• The plugins listed above may not function properly in this scenario.

• WeWeb no longer supports this option.

• We don't recommend using this method for new projects.

  Microservices

  What causes the plugins to not work in these scenarios is due to how WeWeb uses microservices.

WeWeb is a front-end app builder that runs in users' browsers. Some backend services (e.g., Xano, Supabase, Rest API) are designed to be accessed directly from browsers, while others (Airtable, Open AI, etc.) are meant for server-to-server communication and require more security.

To make it easier for users to integrate with services such as OpenAI or Airtable (which aren't typically accessed directly from browsers), WeWeb created microservices.

A microservice is a small, specialized server component that handles specific tasks like securely connecting to external services.

These act as intermediaries, allowing WeWeb users to securely connect to these services without exposing sensitive information like API keys in the frontend.

We have two separate servers:

• WeWeb-Plugins: This microservice acts as a proxy for plugins that need to keep API keys secure (like Airtable and OpenAI).

• WeWeb-Preview (or WeWeb-Server): This server runs your app and handles plugin requests in production.

  WARNING

  In Scenario B (using the deprecated WeWeb-Server), if you host the WeWeb-Server yourself, you won’t have access to WeWeb-Plugins. As a result, plugins like Airtable and OpenAI won’t work because your server can’t securely send requests to these services.

For projects that use plugins that rely on microservices, such as WeWeb Auth, how does this affect data storage and processing locations?

Plugins using WeWeb microservices, like WeWeb Auth, store and process data in the US (using AWS Cognito). This has an effect on EU data residency compliance as data leaves the EU.

What files are included in the code export?

When you export code from WeWeb, you have two options:

Project files:

• This is a Vue.js application ready for deployment.
• The app has been compiled and optimized for production use.
• It includes all necessary components and dependencies.
• Can be immediately deployed to a web server or hosting platform.

Raw project files:

• These are static HTML/CSS/JS files.
• They represent the basic structure and content of your project.
• Useful if you want to run your build process or perform code analysis.
• Can be modified or integrated into custom development workflows.
• They do not contain Vue.js components or framework-specific code.

Raw files that need a build step and built files that are ready to host immediately.

Can I make edits to my exported code outside WeWeb?

While it's technically possible to edit the exported code from WeWeb, it's not easy or recommended.

The code is structured by a machine for a machine and is not organized like a human developer would organize it.

Editing these files safely requires in-depth knowledge of WeWeb's internal logic. This approach isn't feasible if you're planning to build a project in WeWeb and then maintain it independently outside the platform.

Can I host my application in an air-gapped environment?

Yes, WeWeb applications can be hosted in networks with no internet access. You can export the code and host it in your network alongside your own backend.

Can I still use WeWeb's CDN when self-hosting?

No. Files uploaded to WeWeb's CDN before self-hosting will not be preserved when you self-host.

For self-hosting scenarios, it's best to set up file uploads to your own storage solution from the beginning to ensure continuity when you transition to self-hosting.

Files that are part of your app's structure (like images embedded in the design) will be included in the export.

Can I export my WeWeb project if it's not published?

No, you need to publish your project at least once to enable the export feature.

Can I export only part of my WeWeb project?

No, the export includes the entire project.

Can I import my exported code back into WeWeb?

No, this feature is currently not available.

Does WeWeb provide server requirements for self-hosting?

With WeWeb, you can self-host your project in any standard web server.

How does WeWeb handle custom domains for self-hosted projects?

The setup of a custom domain is handled through your hosting provider, not WeWeb.

Can I host my application on a root domain and do white label hosting?

Yes, all of that is possible when you self-host.

Can I still use WeWeb's UI components library in a self-hosted project?

Yes, WeWeb's UI components will be included in the exported files.

What's WeWeb's approach to version control for exported projects?

WeWeb itself doesn't provide version control for exported projects. However, once you have exported your project, you can implement version control yourself using systems like Git.

Does WeWeb provide tools for monitoring self-hosted projects?

No. You'll need to use third-party solutions for that.

Is it possible to add multiple subdomains to a self-hosted project?

Yes. You can deploy to multiple domains if you self-host.