Connect an existing GitHub repository
Work against the team's current repository; the documented workflow does not require migrating to a new stack.
A browser-based workspace for teams to build and review changes in an existing codebase.
Base Code is a browser-based development environment from Base44 for teams working on an existing GitHub codebase. It gives a team a shared cloud workspace to request, build, preview, and review product changes without requiring each contributor to set up a local development environment. Changes are made on isolated branches and returned as standard pull requests, keeping engineering review and merge decisions within the team's existing workflow.
Work against the team's current repository; the documented workflow does not require migrating to a new stack.
A team member can describe a requested change, which Base Code applies on an isolated branch in the existing codebase.
Each dedicated branch has a running preview so contributors can inspect and test the product change in context.
Team members can see active sessions, open live previews, and jump into branches to follow changes as they happen.
Completed changes come back as GitHub pull requests, with standard diffs and the team's existing review and merge process.
Contributors can work without cloning the repository, installing dependencies, or configuring a local development environment.
Product managers can turn copy edits, flow refinements, or product ideas into working changes and test them against the live product context before engineering review.
Designers can implement a change in the existing codebase and inspect how it behaves in context, rather than relying only on a static design or a ticket.
Marketing contributors can adjust product messaging or content and preview it in the product, then submit the change for the team's normal review.
QA can turn a reproducible issue into a proposed code change, such as improving an edge case or adding test IDs, instead of leaving the finding solely as a backlog item.
Engineering teams can let others prepare branch-level changes while retaining pull-request review, existing checks, branch protections, and final merge authority.
Yes. Base Code connects an existing GitHub repository. Projects must be web or full-stack apps; for a monorepo, the root project must meet those requirements. A branch preview is a development environment, not production hosting.
No. Base Code runs in the browser, so contributors can work without cloning the repository, installing dependencies, or setting up a local environment.
Changes are returned as standard GitHub pull requests. Existing branch protections, required checks, and review rules remain in place, and engineering decides what is merged.
Contributors need an Editor or higher workspace role. GitHub write access is required to change code, create branches, or open pull requests. Engineering retains review and merge control.
No. It works within the existing workflow by adding a shared way to prepare and preview changes; engineering retains control of review and merging.