A Stronger Foundation for Deployments, Backups, Privacy, and Project Pages

This was a foundation sprint. Instead of one headline feature, we tightened the product around the workflows people hit first: signing in, creating a project, recovering broken deploys, showing a good public page, and trusting that the platform will not silently lose operational data.

Easier Access from Synth Cabal and Google

Telegram users coming from Synth Cabal can now open VibeNest without a separate account setup step. The flow provisions or resolves the owner automatically, creates a secure magic-link login, and treats Telegram-origin users as confirmed without granting the normal email-registration bonus twice.

Google OAuth is also ready for production use. The consent screen, privacy-policy references, and sign-in flow were aligned so Google login feels like a first-class path instead of a test integration.

Smarter Project Creation

New projects now default to automatic build-pack detection. VibeNest checks common project signals first, can fall back to an LLM when the repository is ambiguous, and still has a safe default when neither path gives a confident answer.

For monorepos, the single "New Project" flow now detects workspace structure and offers a clear choice: analyze as a group or deploy only the root. That keeps the first screen simpler while still supporting larger repositories.

Failed deployments now have a better recovery path. Instead of silently applying an AI-generated fix, VibeNest stores a diagnosis and shows it to the project owner with Apply and Ignore actions.

This matters because deployment fixes can change build commands, base directories, ports, branches, or environment settings. The platform can still help, but the user stays in control before anything is changed.

Admins also gained a rescue dashboard with spend, attempts, acceptance rate, pending fixes, CSV export, and alerts if daily rescue spend crosses the configured threshold.

Project Pages Became More Useful

The wiki improvement workflow was consolidated into one "Make it Nice" action with checkboxes. Instead of separate buttons for refresh, design, SEO, and real-data SEO, owners now choose the improvements they want in one modal and see progress in one place.

AI-generated CTA buttons on beautified pages now point to the live app when the app is running. They also receive tracking parameters so owners can see which calls to action actually drive traffic.

Later in the sprint, CTA tracking became more precise: duplicate button labels get unique utm_content values, project-subdomain visits are tracked correctly, and the stats page can separate wiki traffic from live-app traffic.

Better Backup and Operational Safety

Backups now have a watchdog. A daily service checks PostgreSQL, ClickHouse, environment backups, and restore-drill freshness, then notifies admins if anything is stale, failed, or suspiciously small.

This was added after discovering that a backup file could be "fresh" but only contain an error message. Freshness alone is not enough; the watchdog now checks size and restore-test recency too.

Deployments also became safer: the production deploy script can re-exec itself after pulling a newer version, preventing half-old shell runs when the deploy script changes during deployment.

Privacy, Account Deletion, and Admin Controls

The privacy policy was brought closer to the real product. Data categories, third-party services, retention windows, and GDPR rights are now more explicit.

Users can delete personal data through the account area, with billing records anonymized where tax retention requires keeping transaction history. Admins also gained safer controls for bulk user soft-delete and project blocking, including owner notifications and visible block history.

What This Enables

The sprint made VibeNest less fragile at the edges: fewer dead CTAs, fewer silent backup failures, fewer confusing first-deploy paths, and a clearer contract around AI fixes. That foundation matters before scaling up acquisition, because the first project experience now has more guardrails built in.