WeWeb Version Control: Git Sync and Collaboration Workflows

GitHub sync is configured per project. In the WeWeb editor, click the gear icon in the left navigation bar to open App Settings → scroll to find the Git Integration section (or look for a GitHub integration option). Click Connect to GitHub. A GitHub OAuth dialog opens — authorize WeWeb to access your GitHub account. Choose whether to give WeWeb access to all repositories or only specific ones (specific is safer). Back in WeWeb, you will be prompted to either connect to an existing repository or create a new one. For a new project, click Create new repository → name it → select your GitHub organization or personal account → click Create. WeWeb will push your current project state to the new repository immediately. The repo is created on GitHub with your compiled WeWeb code.

GitHub sync is tied to the WeWeb publish action — not to every save or auto-save in the editor. When you click Publish (top-right button) in the editor, two things happen in sequence: (1) WeWeb builds your app and deploys it to WeWeb Cloud hosting (if you have a hosting plan), and (2) WeWeb pushes the compiled code to your connected GitHub repository. This means GitHub always contains the last published version of your app, not necessarily the most recent changes you made in the editor. The branch that receives pushes is your repository's default branch (typically main). WeWeb never creates feature branches automatically — it always pushes to the default branch. Note: true Git branching within WeWeb (creating WeWeb editor branches) is on the roadmap for Q3-Q4 2026 but is not yet available.

With GitHub sync active, you can wire up a hosting platform to auto-deploy whenever WeWeb pushes. The most common setup is Vercel connected to your GitHub repository. In Vercel (vercel.com): click Add New → Project → Import Git Repository → select your WeWeb repository. Vercel auto-detects it as a static site. Set the output directory to the folder containing your index.html (typically the root or a built/ subdirectory — check your repository structure). Add a vercel.json file with the SPA rewrite rule in your repository root. Click Deploy. Now every time you Publish in WeWeb, GitHub receives the new code, which triggers Vercel to build and deploy automatically. The full cycle from clicking Publish to your live site updating takes approximately 2-3 minutes.

1// vercel.json — add to the root of your WeWeb GitHub repository
2// This configures SPA routing so all client-side routes work on Vercel
3{
4  "rewrites": [
5    {
6      "source": "/(.*)",
7      "destination": "/index.html"
8    }
9  ]
10}
11
12// Optional: GitHub Actions workflow for custom deployment logic
13// .github/workflows/deploy.yml
14name: Deploy WeWeb App
15on:
16  push:
17    branches: [main]
18jobs:
19  deploy:
20    runs-on: ubuntu-latest
21    steps:
22      - name: Trigger Vercel deployment
23        run: |
24          curl -X POST "${{ secrets.VERCEL_DEPLOY_HOOK_URL }}"

Backups in WeWeb capture a complete snapshot of your project configuration — all pages, components, workflows, variables, data sources, and settings — but NOT your live database data. To create a manual backup: open App Settings → Backups. Click Create Backup. WeWeb creates a timestamped snapshot immediately. Name it descriptively (e.g., 'Before adding payment flow', 'Stable version March 2026') — the name helps you identify what state the backup represents. Manual backup limits: Pro plan users get unlimited manual backups. Essential plan users have a limited number of manual backup slots (check your current plan limits in the Backups page). Creating a manual backup before attempting complex changes or major refactors is a critical habit for all WeWeb developers.

WeWeb automatically creates backups at regular intervals based on your seat plan, without any action required from you. On the Free plan: auto-backups may not be available or are limited. On the Essential plan: daily auto-backups are created automatically. WeWeb retains a rolling window of recent daily backups. On the Pro plan: hourly auto-backups are created automatically, giving you much finer recovery granularity — if something breaks, you can roll back to 1 hour ago rather than 24 hours ago. Navigate to App Settings → Backups to see all auto-backups listed chronologically alongside your manual backups. Auto-backups are labeled with their timestamp and type (auto). They function identically to manual backups for restore purposes.

If you publish a breaking change or make a mistake that is difficult to undo, you can restore your project to any backup state. Navigate to App Settings → Backups. You will see a list of all backups (manual and auto) sorted by date. Click on the backup you want to restore to — verify the timestamp matches the state you want to return to. Click Restore. WeWeb will ask you to confirm, as restoring overwrites your current project state. Click Confirm Restore. The restoration process takes 30-60 seconds. After restoration, your project is in the exact state it was in at backup time — all pages, workflows, variables, and settings revert. Note: restoration does NOT revert any database changes (Supabase/Xano data) — only WeWeb project configuration.

WeWeb Pro allows multiple users to edit the same project with individual accounts. Each team member needs a Pro seat. To invite team members: go to Workspace Settings → Team → Invite Member → enter their email. They receive an invitation to join your workspace. Once accepted, they appear in your team list. Important: WeWeb does not currently support simultaneous real-time collaborative editing in the same project at the same time (like Figma). Two developers editing the same project simultaneously may overwrite each other's changes. The recommended team workflow is: (1) Assign ownership of specific pages or sections to specific team members. (2) Communicate before editing — use Slack/Teams to announce when you are working on a project. (3) Publish and create a manual backup before handing off work. (4) The developer taking over pulls the latest state by refreshing the editor.

WeWeb has a built-in After Deploy Hook that sends an HTTP GET request to a URL you specify after every successful deployment. This is useful for triggering downstream actions: invalidating CDN caches, sending a Slack notification to your team, triggering a Lighthouse audit, or updating a deployment log. To configure it: App Settings → After Deploy Hook → enter the URL that should receive the GET request. WeWeb sends GET requests with query parameters including: type (deploy type), version (deployment version number), name (project name), env (environment: production or staging), built-zip (URL to the compiled built zip), and raw-zip (URL to the raw project zip). Use a Zapier or n8n webhook as the hook URL to trigger any downstream automation.

1// Example: n8n webhook node to receive WeWeb After Deploy Hook
2// WeWeb sends: GET https://your-hook-url?type=...&version=...&name=...&env=...&built-zip=...&raw-zip=...
3
4// Example Node.js Express endpoint to receive and process the hook
5// Deploy this to Vercel Functions or Supabase Edge Functions
6export default function handler(req, res) {
7  const { type, version, name, env, 'built-zip': builtZip } = req.query;
8  
9  console.log(`WeWeb deployed: ${name} v${version} to ${env}`);
10  
11  // Trigger Slack notification
12  fetch('https://hooks.slack.com/services/YOUR_WEBHOOK', {
13    method: 'POST',
14    headers: { 'Content-Type': 'application/json' },
15    body: JSON.stringify({
16      text: `WeWeb app deployed: ${name} v${version} (${env})`
17    })
18  });
19  
20  res.status(200).json({ received: true });
21}