Version Publishing / Staged Rollouts / Beta Releases

urrent Issue:
Right now, whenever updates are published, they immediately go live to all app users. This makes it difficult to safely test major updates, new features, UI changes, workflows, automations, or backend functionality before exposing them to everyone.

Requested Feature:
Please add a full Version Publishing & Release Management system similar to staged deployments used by modern SaaS platforms and mobile app ecosystems.

Core Features Requested:

  1. Environment-Based Publishing

  • Development Environment

  • Staging Environment

  • Production Environment

  • Ability to test changes privately before production release

  1. Beta User Access / Feature Flags
    Allow app owners to:

  • Select specific users/accounts as “Beta Testers”

  • Release updates ONLY to those users

  • Keep the current stable version live for all other users

  • Toggle features on/off for specific user groups

  • Create internal staff-only testing access

Example:

  • Public users stay on Version 1.0

  • Beta testers access Version 1.1 with new features

  • Bugs/issues can be tested before global release

  1. Version Control & Rollbacks

  • Create named app versions/releases

  • View release history

  • Roll back instantly to previous stable versions

  • Compare changes between versions

  • Restore backups from previous releases

  1. Gradual Rollout Controls
    Allow:

  • Release to 5%, 10%, 25%, 50%, or 100% of users

  • Region-based rollouts

  • User tag/group rollouts

  • Invite-only releases

  1. Publishing Options
    When clicking Publish:

  • Publish to Everyone

  • Publish to Beta Users Only

  • Publish to Internal Team Only

  • Schedule Publish Date/Time

  • Save as Draft Version

  1. Separate Database / API Testing Mode
    Ability to:

  • Use sandbox/test databases for beta environments

  • Prevent beta testing from affecting production/live customer data

  • Test automations, CRM actions, notifications, and workflows safely

  1. In-App Version Management Dashboard
    Dashboard should include:

  • Current live version

  • Active beta version

  • Release notes

  • Rollback button

  • User groups assigned to versions

  • Deployment logs/errors

  • Feature flag management

  1. User-Level Feature Toggles
    Ability to:

  • Turn on features for specific users

  • Unlock features for premium plans only

  • Test UI redesigns with select users

  • A/B test features and layouts

Why This Matters:
This would massively improve app stability, reduce bugs reaching production users, and allow agencies/platform builders to safely innovate without risking their live customer base every time an update is published.

This is especially important for platforms managing:

  • Client portals

  • CRM systems

  • Booking systems

  • Social/community apps

  • AI tools

  • Automation workflows

  • Payment systems

  • Large user bases

This feature would make Base44 significantly more scalable and enterprise-ready.

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board
💡

Feature Request

Date

3 days ago

Author

Socially Versed

Subscribe to post

Get notified by email when there are changes.