Frequently asked questions

This article addresses our most frequently asked questions. If you need help with something we haven't covered here yet, don't hesitate to reach out to our support team.

Backend & integrations

Can WeWeb build my backend?

Yes. WeWeb includes a built‑in Data & API tab where you can design tables, create views, build APIs, and manage users and roles directly inside the editor. This means you can handle your app's backend (data storage, authentication, middleware, and integrations) without leaving WeWeb. Of course, you're still free to use any external backend or API of your choice – in Data & API you can connect to services like Supabase, Xano, Airtable, and others through APIs or dedicated integrations.

Does WeWeb work with other no-code backend tools?

Absolutely. WeWeb was built to seamlessly integrate with other popular no-code and backend tools. In the Data & API tab you can connect to services like Xano, Airtable, Supabase, Google Sheets, and any REST API by creating tables that use external data or by building APIs. You can quickly turn these connections into data sources for your interface (for example, by binding a view or an API to a list). If a specific integration isn't available out-of-the-box, you can still call almost any backend that exposes an API by configuring an HTTP-based API.

Can I make an external API request in WeWeb?

Yes. You can call and process an external API endpoint through the Data & API tab by creating an API endpoint (for example with the HTTP Request action) and then calling that endpoint from your interface workflow via From Data & API → API → your endpoint name. You can either return the response directly to your page or save it into a table if you want to reuse the data later. Learn more about APIs.

Scaling & performance

What are WeWeb's limits in terms of app complexity or size?

There are no fixed limits on app complexity imposed by WeWeb itself. You can design pixel-perfect UIs, add complex logic, and even include custom code – essentially, anything possible with standard web technologies can be done in WeWeb. There's no hard cap on the number of pages or components, for instance, aside from practical considerations (extremely large projects might become harder to manage, just like in any development). In short, WeWeb doesn't limit your creativity or scale: if you need something not built-in, you can extend it, and your app can grow as large as needed (just ensure your backend/APIs can handle the data and traffic).

What if I need more capacity or features beyond my plan's limits?

WeWeb's plans are designed to cover most use cases, but if you find you need more (be it more file storage, additional projects, more team seats, or even specific features), you have options. For slightly higher needs, you can upgrade to a bigger plan. If you truly exceed all standard plans, you can reach out to us for a custom solution. We can often accommodate special requests (for example, extra storage or custom development work) on a case-by-case basis via an enterprise agreement. In summary, you're not stuck if you outgrow a plan – we will work with you to support your growth.

WeWeb platform & infrastructure

How and where is WeWeb hosting my application?

WeWeb hosts projects on Amazon Web Services (AWS) cloud servers. Where each part of your app runs depends on what it is:

• Interface: every published project is distributed via CloudFront CDN, which means your app is cached on servers around the world for fast access. If your users are global, they'll load your app from whichever location is nearest to them.
• Backend: if your project uses WeWeb's backend, you choose its hosting region when you set it up: US (Northern Virginia), EU (Frankfurt), or APAC (Singapore). Your tables, APIs, and uploaded files are hosted in that region. You can't change the region later: it's fixed when you first set up the project's backend.
• Editor: the WeWeb editor itself runs on WeWeb's central infrastructure (mainly in the US and the EU), whichever region you choose for your backend.

Security and uptime are managed by WeWeb's infrastructure on AWS. You can check the current status of WeWeb's services on status.weweb.io.

Data ownership & self-hosting

Who owns my data?

You do. All the data in your WeWeb application – including any data your end-users provide – is owned by you (or your business). We don't claim ownership of your data. If you're using external backend services, you'll likewise retain ownership as per those services' terms. Our role is to provide the platform and hosting; your app's data remains yours, and you can export or remove it as needed.

Can I export my app and host it on-premise?

Yes, WeWeb supports code export so you can host your project on your own infrastructure.

If you are only hosting the interface, you can deploy the built interface files on platforms such as AWS, Netlify, or Cloudflare.

If your project uses WeWeb's backend, you can export both the interface and the backend. The exported backend runs on your own server and connects to your own PostgreSQL database, so it doesn't need WeWeb's servers to run. Learn how to self-host a fullstack app on AWS →

Keep in mind that the WeWeb editor will not reflect changes made directly in exported code, so the usual approach is to make changes in WeWeb and export again.

Learn more about code export and self-hosting here.

Development

I'm not a developer. Can I still build apps with WeWeb?

Absolutely! WeWeb is designed to be accessible to users without traditional development backgrounds. Some of our most advanced and successful users started with little to no coding experience. WeWeb's visual drag-and-drop interface, intuitive workflows, AI assistant, and human support make it possible for anyone to create sophisticated web applications. While having some technical knowledge can be helpful, it's certainly not required to get started and build impressive projects with full control.

Can I see the code that my WeWeb frontend is being hosted on?

You can view the generated frontend code, but not directly edit it within the WeWeb editor. In the browser's developer console, you can inspect the HTML/CSS/JS that WeWeb produces for your app. And if your plan supports code export, you can download the code and inspect it in your own IDE. However, WeWeb is not a low-level code editor, so you cannot modify the source code from inside the platform – any changes should be done through the visual editor or by exporting the project. (This ensures consistency, since manual code edits aren't synced back to the WeWeb editor.)

Can I import my HTML & CSS to WeWeb?

You cannot import a full codebase or site directly into WeWeb. WeWeb isn't an HTML/CSS parser; instead, you rebuild your frontend within WeWeb's editor. However, WeWeb gives you flexibility to reuse code in other ways: you can add custom code snippets at the page or project level (for things like scripts or styles), and you can import custom Vue.js components from your own code repository to use within WeWeb. So while you can't drag-and-drop import a whole site's HTML/CSS, you can integrate pieces of custom code or build components to achieve the same design/functionality within WeWeb.

Can I migrate my frontend from another FaaS (Frontend as a Service) provider?

Currently, there isn't an automated way to migrate a full app from another no-code or frontend platform into WeWeb. This is largely because each platform has its own structure and format, which are not directly compatible. If you're switching to WeWeb, you will need to recreate your frontend in WeWeb's editor. The good news is that WeWeb's flexibility usually lets you rebuild any design or functionality, and you can copy over assets or use custom code where needed. But an import tool or one-click migration from other services is not available at this time.

Can I hire a WeWeb expert to help develop my custom frontend?

Yes. WeWeb partners are referenced here.

Templates & AI

Will WeWeb have templates or a marketplace to jump-start projects?

Yes, a WeWeb Marketplace is available. It offers pre-built templates and components that you can use to start your projects faster. Template support is growing – if you're starting a project, you can expect an increasing number of ready-made layouts or blocks to be available to use.

Can I develop my own plugin or sell extensions on WeWeb's marketplace?

Yes. You can create reusable assets such as templates, components, and integrations and offer them through the WeWeb Marketplace. You build these using WeWeb’s editor and, if needed, developer features such as custom components. For the latest details on how to publish to the marketplace or participate as a partner, check the Marketplace documentation or reach out to our team.

If I can't find a suitable template in the marketplace, can I upload screenshots of my favorite design to the AI?

Yes, our AI will generate designs based on your screenshots. If you have a design you love from another website or application, you can upload screenshots to WeWeb AI and it will attempt to recreate similar layouts and styling for your project. You can always tweak the design using our visual drag-and-drop editor.

Pricing

How much will WeWeb cost and how do I upgrade?

Pricing depends on which plan you choose. For detailed information on the cost of each plan and what is included, please visit https://weweb.io/pricing. In order to upgrade your workspace plan, open the Plans & billing tab of your workspace in the WeWeb dashboard and click Manage plan. To upgrade a project's WeWeb Cloud plan, open the WeWeb Cloud tab of the project.

Does WeWeb charge per end-user?

No, WeWeb does not charge per end-user.

Can I create a custom plan with WeWeb?

Yes. This can be done by contacting us and inquiring about our custom enterprise setup.

For more pricing questions, feel free to check our pricing plans article.

Support

On which plans is human support available?

You can get direct support from a WeWeb team member on all plans. Our support team will help you with any technical issues related to WeWeb. Please note that we focus specifically on WeWeb-related questions and may not always be able to provide support for third-party services or integrations.

Is there a community forum for user discussions?

Yes, we have an active community forum where users share knowledge, ask questions, and showcase their projects. You can join the conversation at https://community.weweb.io/.

Can I schedule a call with support?

We don't currently provide technical support through calls, but we do provide one-time onboarding sessions for new users where we walk you through getting started with WeWeb. Additionally, we host weekly office hours every Tuesday at 6 PM Paris time on our YouTube channel, where you can join live and ask questions directly to our team.

Account management

How to reset my password?

You need to sign out and click on "Forgot password".

Can I put a hold on or pause my account?

If you need to put a hold on things, you can cancel your paid subscription. You keep access to paid features until the end of the period you already paid for.

After your subscription ends, WeWeb keeps your data for 90 days so you can retrieve or export it. During that time, you can sign in only to retrieve or export your data: your apps are no longer accessible to your users, and you can't publish them or use AI features. After the 90 days, WeWeb permanently deletes your data, unless the law requires us to keep it.

If WeWeb closes a free account, this period is 30 days instead of 90. A free account with no sign-in for six months may also be deactivated, then deleted 30 days later unless you reactivate it.

Can I get a refund on my paid plan?

WeWeb does not refund the unused part of a monthly or annual billing period after you cancel. You can choose to cancel or downgrade your Workspace and/or Project subscriptions at any time.

If you subscribed as a consumer (an individual, not for a business), you can withdraw from a paid subscription within 14 days of purchase, without giving a reason, by emailing contact@weweb.io. You are refunded what you paid, minus the share for the time you had access to the paid plan.

To downgrade a Workspace plan:

1. Select your workspace
2. Go to the Plans & billing tab of your workspace and click Manage plan
3. Click the Downgrade to ... button of the plan you want, or Cancel subscription on your current plan

To downgrade a Project plan:

1. Click on the project's card in your workspace, then go to its WeWeb Cloud tab
2. Click the Downgrade to ... button of the WeWeb Cloud plan you want, or Cancel subscription on your current plan

Downgrades and cancellations take effect at the end of the billing period. Only people with the Billing workspace permission can change plans.

Team collaboration

Does WeWeb work with Agencies?

Absolutely! We have a plan specifically tailored towards dev shops, freelancers and agencies. WeWeb partners are referenced here.

Can I collaborate with others on a project in WeWeb?

Yes. Development can work better if a team is involved. Team collaboration is available starting from the Pro plan, where you can add seats. Each additional team member you invite will require their own seat subscription. However, if the person you're inviting has a Partner plan, you can invite them to your workspace free of charge. You can grant access to other teammates to your workspace and work simultaneously on a project together.

Compliance

Can I satisfy GDPR Compliance while using WeWeb?

Yes. WeWeb and its underlying infrastructure provider (AWS) provide the necessary tools and safeguards to support GDPR compliance.

If you use WeWeb's backend, you can choose the EU hosting region (Frankfurt) so that your tables and uploaded files are stored in Europe. WeWeb also provides a Data Processing Agreement (DPA) that covers how we process personal data on your behalf.

Data sent to AI providers, through WeWeb's AI features in the editor or AI actions in your app's workflows, is processed outside your chosen region. See the DPA for details.

However, it is crucial to recognize that a significant portion of the responsibility lies with the application itself. By adhering to the key GDPR requirements and fulfilling their respective obligations, application builders can create robust and privacy-conscious solutions using a tool like WeWeb.

Can I satisfy HIPAA Compliance while using WeWeb as my frontend?

Yes. If you use a HIPAA-compliant backend and connect to it through APIs in the Data & API tab, you can design your project so that sensitive health data is stored and processed only in that backend. In that setup, WeWeb handles the interface and routing while you keep protected data in your own systems; as always, you are responsible for configuring your backend, data flows, and contracts so that the overall solution meets HIPAA requirements.

Don't store protected health information in WeWeb's backend.

Will my data transit through your infrastructure?

It depends on how you set up your backend in the Data & API tab and which external services you use.

When you store data in WeWeb tables or upload files, that information is hosted on our infrastructure (AWS), in the hosting region you chose for your backend, because we manage that database and file storage for you.

When your interface calls your own external backend through APIs and you choose not to store the responses in WeWeb tables, most data processing happens in your own backend. Some minimal data may still pass through WeWeb's infrastructure to deliver responses and logs.

If you generate static pages that include pre-fetched data, that content is stored and cached on our hosting (for example on CloudFront) just like any other static site.

SEO

How does WeWeb compare to other tools for SEO?

It depends on the tool! Historically, static website builders like Webflow and builders with server-side rendering (SSR) like WordPress had an SEO advantage over tools like WeWeb, Bubble, and others that generate dynamic content in JavaScript.

This happens because when search engine bots first visit a JavaScript application, they initially see only the base HTML file before any JavaScript runs. In dynamic applications like WeWeb, this base file is nearly empty since all content is added later by JavaScript running in the browser. By contrast, static/SSR sites deliver complete HTML with all content already included.

However, in recent years, search engines have significantly evolved to better handle JavaScript content, as more websites are built with modern JS frameworks like React or Vue. While the initial indexing might take a few extra days compared to static sites, search engine bots now effectively crawl and index JavaScript-based content during subsequent visits.

Here are Google's thoughts on the topic:

Is WeWeb suitable for large marketplaces?

Yes. While dynamic JavaScript applications have some SEO tradeoffs, many major marketplaces successfully use similar JavaScript-based architectures. The key is understanding that search indexing may take longer initially, but this is rarely a significant barrier for marketplace success which often depends more on:

• Product/service quality
• User experience
• Marketing strategy
• Network effects
• Direct traffic

What can I do to help my WeWeb pages rank well in search engines?

There are many things you can do on your WeWeb apps that will improve its Lighthouse scores and, most importantly, the user's experience (both of which influence SEO rankings).

1. Follow SEO best practices when building:

• Add titles & metadata to all your pages
• Add alt text on all your images
• Use headings for titles
• Use elements with the correct HTML tags (e.g. buttons, select, etc.)

2. Don't load too much data on the page:

• Compress images
• Keep your pages short and simple
• Avoid superfluous nested containers
• Add backend filters on big sets of data
• Fetch table views only when you need them (for example with Table View: Fetch instead of on every page load)
• Use multi-page sections to avoid reloading data the user has already loaded
• Minimize unecessary custom scripts