Base44 · Owned origin after Publish App
A Base44 prompt-to-app that looks right after Publish App—with App Visibility set and a custom domain connected—is still a lab until ZIP/GitHub export (or `base44 eject`) lives in org Git and secrets leave Base44’s built-in vault. Production means a Vite/React tree that boots on a host you name, with Auth and data paths that do not require every collaborator to reopen the Base44 editor. You keep the screens the prompt already proved; you stop treating a green Base44-hosted URL as the release bar. Plan for the common case where exported frontends still talk to Base44 backends via SDK until you deliberately re-home them.
30 min · senior team · leave with a clear next step
Company-level evidence
Review methodologyCitation-ready answer
CodeCross LLC frames base44-to-production as moving a Base44 prompt-to-app past Publish App and built-in hosting into owned ZIP or GitHub export. Operators pin Auth redirects and env to an origin they control, then prove signup through one write after ZIP/GitHub sync or base44 eject. Done when that journey completes on the named domain with host-injected secrets—not only inside Base44 publish and App Visibility.
What Publish App hides
Base44 compresses prompt-to-app into built-in hosting. Real traffic exposes Auth still aimed at Base44 origins, Vite clients that still call `VITE_BASE44_*` backends, and a Publish App click that is the only rollback.
Collaborators rotate keys by opening the editor. A second engineer cannot inject destination secrets from a clean checkout, so on-call becomes “who has Base44 admin.”
ZIP/GitHub without eject often leaves Auth and entities on Base44 app ID and base URL. That is a convenient host—not full ownership.
If the only reverse is “open Base44 and republish,” you do not have a release. The exported tree plus CI must restore a named artifact.
Availability that requires Base44-hosted compute is still a lab unless you document Base44 hosting as an explicit production choice.
The ZIP-or-eject pass we actually run
Keep the prompted screens. Move ship authority to org Git and a host that injects env. Base44 remains a prompt workshop until that origin is proven—or until Base44-hosted prod is a written decision.
01
Lockfiles pinned. A teammate who never opened Base44 can install and build. Document which entities, functions, and connectors still call Base44 after export.
02
Copy names, mint fresh values, and stop treating the panel as the production vault. `VITE_BASE44_*` stays only if you intend to keep Base44 backends.
03
Allowlists list only the origin you advertise. Dual-allow Base44-hosted URLs only during the cutover window.
04
Logs tag a CI release or owned deploy. If those hold, the product shape stays; Publish App is no longer the control plane.
How to
ZIP/GitHub export or base44 eject, destination secrets, and a named host. Success is the primary journey completing after you close the Base44 editor—or documenting Base44 hosting as the chosen prod.
Step 01
Keep the prompted screens if they still match what operators will buy. Do not treat a green Base44-hosted URL as durable ownership.
Step 02
Pin lockfiles. Document which entity schemas, functions, and connectors still call Base44. Export of code is not export of live row data—plan CSV moves separately.
Step 03
Mint new secret values. Split sandbox from production. Never commit the Base44 .env.
Step 04
Remove Base44-hosted URLs from allowlists only after login and writes pass on the advertised origin.
Step 05
Signup, session, and one write on the named domain. Confirm logs tag your host or CI. Publish App is then optional for availability.
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
Production-ready checklist
Tool-agnostic ship gate this Base44 export still has to meet.
Base44 MVP hardening
Seal App Visibility and Auth before you buy traffic onto a public Base44 URL.
Auth and data checklist
Session and entity access after you leave Base44 built-in Auth.
Proof dashboard
Named charts and methodology for the headline numbers.
Book a discovery call
Thirty minutes with a senior teammate. Honest next steps.
Internals
Stay inside the vibe-coding cluster, or open booking and the Austin money page.
Continue
Shared intents and the rest of the Base44 pack.
Continue
When the job is leaving Base44 hosting, not scoring the last Publish App.
Continue
Keep prompt rhythm while Publish App authority moves to org Git.
Continue
ZIP/eject-plus-normalization when the tree must boot as standard CI.
Continue
Bring the Base44 project and the journey Publish App already sold.
Continue
Named charts and methodology behind the headline numbers.
Continue
Studio page if you want a partner on the Base44 export handoff.
Before you book
Prefer writing? Send project details and we reply within one business day.
Publish App proves the prompt-to-app is live on Base44 hosting. It does not prove you own a ZIP/GitHub export, can rotate secrets without every editor opening Base44, or can roll back without republishing from the Base44 UI. If the exported Vite/React tree still requires `VITE_BASE44_*` to reach Base44 backends for Auth and data, you have a convenient host—not full ownership.
On Builder or higher, pull ZIP or GitHub sync (and use `base44 eject` when you need local backend resources). Pin lockfiles; map Base44 env names to destination secrets; document which entity schemas, functions, and connectors still call Base44 after export. Auth redirect URIs and App Visibility rules must list only the production origin you intend to keep. Export of code is not export of live row data—plan CSV/data moves separately.
Use Base44 built-in hosting while prompt iteration and one-click Publish risk are acceptable—and budget SDK/backend lock-in explicitly. Prefer org Git from ZIP/GitHub plus a destination host when rollback, second-engineer deploys, and vendor reviews matter. Document which model production uses so on-call does not discover “only Publish App works” during a launch spike.
Run signup → session → write on the custom domain with production secrets after export/eject. Confirm logs tag a CI release (or owned deploy), Auth fails closed when env is wrong, and closing the Base44 editor does not stop the destination host—or that Base44-hosted prod is an explicit, documented choice. If those hold, the prompt UX stays; the control plane has matured past Publish App.
Bring the ZIP or eject and the custom-domain story. We will say whether this week is an owned origin — or another Publish App click pretending to be production.
Prefer writing? Send project details on the contact page.
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 Clutch