Choosing a backend

Decide between WeWeb's native backend and an external backend.

Both options work well in WeWeb. Use this guide to choose what's right for your project and understand basic migration steps.

When to use the native backend

• You want tables, auth, and API Endpoints without operating an external service
• You need secure server logic that calls third-party APIs with secrets
• You prefer visual filters and parameters over writing SQL or API queries

When to use an external backend

• You already have an existing backend/API you must integrate
• You require advanced database features not yet available natively
• Your organization standardizes on a vendor like Supabase or Xano

Migration notes

• Model tables/columns to mirror your current data
• Recreate views as collections with filters and parameters
• Port critical API Endpoints and return similar response shapes
• Update frontend workflows to call native API Endpoints and collections

Related docs

• Intro to collections (external sources) →
• Plugins overview →

CONTIUE LEARNING

Start building with the native backend now.

Intro to the backend →