Base44 · Export to ship
Publish App is where you proved the prompt-to-app boots — not where strangers should live without an owned tree. Own a ZIP or GitHub export, move secrets out of the panel, and put a start path on paper so someone else can ship with the editor closed. First useful cut on a real address — not cancel-the-project.
30 min · senior team · leave with a clear next step
Company-level evidence
Review methodologyIn plain words
To-production here means the export becomes the thing you ship from. Auth checks live where they matter, panel secrets rotate out, you can name which version is live, and you know how to undo a bad Publish App. Built-in hosting stays a studio option — not an unexamined finish line. A short note that people can trust the app is.
What living on Publish App still hides
That is the right first job. The second job is what users feel when Auth fails or the SDK still owns data — whether you wrote it down or not.
If a row is only hidden on the screen, someone can still ask for it another way. Production checks every read and write where it counts.
Keys that only exist in Base44 settings are not a safe home. Rotate anything that lived there.
Production answers: what changed, which export is live, what checks passed, and how to undo.
Reviewed export builds beat panel publish when uptime and second-engineer deploys matter.
The handoff we actually run
Keep the screens. Stop relying on untested Publish App to run the app.
01
Document VITE_BASE44_* and connectors you will keep vs replace.
02
Fresh values. Named in a vault. Fail closed when missing.
03
Second person can release a known Vite/React tree.
04
Signup → session → write. Prior version ready.
How to
Own export, secrets, and start. First useful ship — not a full exit.
Step 01
Panel secrets, App Visibility, SDK Auth.
Step 02
Lockfiles pinned.
Step 03
Production domain only.
Step 04
Logs tag the release.
Step 05
Document which model production uses.
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
Verified on Clutch · 29 reviews
“What impressed us most about CodeCross was their ability to deeply understand our vision and translate it into a complete digital solution. Unlike many agencies that just focus on technical delivery, CodeCross approached our project like true partners.”
Harris Edelmam
CEO · Ombligo, Inc.
Read on Clutch“Their project management was top-notch.”
Greg Moreno Earle
Technology Executive · Driven Brands Inc.
Read on Clutch“Their eye for clean, modern design combined with technical excellence was very impressive.”
Robert Valentino
Founder · Lean Coach
Read on Clutch“We appreciated Codecross's practiced approach to development.”
Brice Wiley
Marketing Director · Lex Mundi
Read on Clutch“On the development side, everything has gone quite smoothly and perfectly.”
Brandon Patterson
Co-Owner · Cap Tech Services, LLC.
Read on Clutch“They are very thorough in their approach to the project.”
Lukas Haynes
Member Board of Directors · Protect Our Winters Action Fund
Read on ClutchInternals
Stay inside the vibe-coding cluster, or open booking and the Austin money page.
Continue
Shared guides and the rest of the Base44 pages.
Continue
Move one part while Publish App still answers.
Continue
Tighten before strangers hit the URL.
Continue
Bring the export and how you Publish App today. We will say ship vs exit.
Continue
Studio page if you want a partner for the first ship.
Before you book
Prefer writing? Send project details and we reply within one business day.
It proves the prompt-to-app is live on built-in hosting. It does not prove you own a ZIP/GitHub export, can rotate secrets without every editor opening the panel, or can roll back without republishing from the UI. If the export still requires Base44 backends for Auth and data, you have a convenient host — not full ownership.
Pull ZIP or GitHub sync (and eject when you need local backend resources). Pin lockfiles; map env names; document which entities and connectors still call Base44. Auth redirects and App Visibility must list only the production origin. Code export is not row export — plan data moves separately.
Use built-in hosting while prompt iteration risk is acceptable — and budget SDK lock-in. Prefer org Git from ZIP/GitHub plus a destination host when rollback and second-engineer deploys matter. Document which model production uses.
Run signup → session → write on the custom domain with production secrets after export. Confirm Auth fails closed when env is wrong, and closing the editor does not stop the destination host — or that Base44-hosted prod is an explicit choice.
Bring entity schemas, Auth paths that still call Base44, and who can Publish App today. We put owned ship first — and we leave the panel as a studio until evidence says leave.
Prefer writing? Send project details on the contact page.