What does a full-stack app need?
The browser preview lets you inspect the frontend at desktop, tablet and mobile sizes. Managed Workers projects can create a development release with real API routes and an isolated D1 database. Existing Node projects support container builds and temporary development previews.
Publish builds a saved version, runs its tests, verifies the frontend and backend using disposable test data, then checks the production deployment before making it public. Existing Node backends must be prepared for Workers hosting first. Configure any services your app requires before publishing.
Connect sign-in and email
Managed projects can use Google sign-in, email/password accounts, verification, password reset and magic links. The generated app uses the authentication methods enabled by its managed runtime. Development contact messages appear in the test inbox.
Production email requires a verified BrainHalf owner email and configured sending service. Google consent and actual inbox delivery require real provider testing. Custom credentials are encrypted and scoped to the project and environment.
Verify behavior and keep a recovery path
Publish runs verification against the saved source revision automatically. Checks can exercise API routes, database writes, user permissions and browser interactions. Failed checks prevent the new release from replacing the current live version. Later edits stay in your workspace until you publish again.
Use source checkpoints before experimenting with code. Database recovery points are separate: restoring source does not restore records. Request monitoring helps inspect server errors without recording request bodies or credentials.
Reference documentation
Download source with your own configuration
ZIP and GitHub exports omit private environment files and provide blank configuration examples. Keep private keys on the server; VITE_ and NEXT_PUBLIC_ variables are visible to browsers. New GitHub repositories default to private, and sync refuses to overwrite newer branch commits.
BrainHalf service bindings and hosted data are separate from the downloaded source. Standalone Workers deployment requires your own database resources and authentication, email and storage adapters. Follow BRAINHALF_EXPORT.md in the download; entering provider keys alone does not recreate the hosted services.