Managed hosting for full-stack apps
How V1 separates development, production and the platform.
Rollout status
The implementation has been merged for deployment and live testing. Managed hosting is enabled only for designated internal test workspaces. End-to-end acceptance checks are still in progress before customer launches. Static publishing remains a separate, available workflow.
Intended workflow
- Enable Vibeforce Cloud in the app's Backend dialog when available. Setup provisions a development database and installs the Master V1 runtime.
- Build and test in Daytona. Controllers and MasterRecord access the database through a restricted server login.
- Publish. Vibeforce saves a source revision, builds and tests an artifact, and validates it before deployment.
- A first production publication creates a separate database and applies a supported fresh schema baseline. Later updates use guarded migrations.
- Coolify runs the app in its own container at a subdomain of
vibeforceapps.com. Publication is complete only after deployment and HTTPS health checks succeed.
No customer GitHub account is required for managed source history. The existing optional GitHub connection and source export remain separate options. Publishing uses Coolify, not GitHub Actions.
Addresses have different jobs
vibeforce.work: company website and builder documentation.app.vibeforce.work: your builder and workspace.app.vibeforce.work/p/<slug>/: existing static publications.<app>.vibeforceapps.com: the domain reserved for managed customer apps.
The separate registered domain keeps customer app origins outside the platform's domain. DNS alone does not provide TLS, application health or tenant isolation.
Before calling a deployment ready
Verify real sign-in and two-user data isolation, HTTPS, persistence after restart, denied access to platform/private networks, additive updates without data loss, failure recovery, quotas, and backup restoration. Test with a new internal workspace rather than overwriting a sales demo.
Taking a managed app offline stops its runtime; it does not delete its database or source history. A source download is not a database backup. Managed source history also needs its own backup and restore policy.