Publish web apps with AI.
A working build is one step. Ghost helps prepare a managed web app, verify its runtime, expose the live route you asked for, and keep the publication record with the project.
Managed web apps · Verified live routes · Private beta for Mac
Atlas readiness dashboard
- App
- One managed app with a stable identity.
- Before publishing
- Build, runtime, and local health checks completed.
- After exposure
- Verify the returned live URL, then record the published version.
- Later updates
- Continue with the same app and its release history.
Follow a build through to a verified release.
A managed app has a continuing identity. Watch the Atlas dashboard move from its workspace through runtime checks, explicit publication, and a recorded version.
Keep the app and its source together.
Create or select the managed app, then continue implementation in its app-scoped coding workflow. Later changes return to that same project.
- App
- Stable managed-app identity
- Workspace
- Source and app-specific setup
- Brief
- Show the current rollout blockers
Check that the application is actually running.
A completed coding task is not enough. Build verification, process and listener checks, and local HTTP health establish whether the app is ready for exposure.
Use the route the service actually returns.
Publish when it is part of your request. ghost uses the returned live URL and checks the intended output before describing the application as live.
- Intent
- Publish this reviewed app
- Route
- Use the exact returned URL
- Check
- Verify the intended page at that URL
A project name is not evidence of a working public route.
Leave a record of what is live.
Save the verified route and version in Published. A later implementation change needs its own verification; changing metadata does not deploy new code.
- Version
- Confirmed release
- Live route
- Verified and associated with the app
- Next revision
- Continue the same managed project
Illustrative lifecycle. No app is created or published by this demo. A preview, exposed route, and saved publication record are different states.
What does AI app publishing mean in Ghost?
Ghost’s publishing workflow takes a managed web app from implementation to a confirmed live route and a saved publication record. Building code, exposing a URL, and recording a version are distinct steps. This feature concerns web apps—not automatic submission to the Apple App Store or Google Play.
One app. A durable place for its work.
Choose an existing managed app or create one for work you intend to keep. Its stable identity ties the source workspace, coding session, public route, and published record to the same application.
Implementation belongs in the app-scoped coding workflow. Ghost can continue that work for a later revision rather than treating every request as a new, unrelated project.
A temporary script or one-off experiment belongs in a sandbox. Making an experiment useful does not by itself authorize moving it to a public URL.
- Managed app
- A durable project with its own identity and workspace.
- Coding session
- Implementation, dependencies, build, and app-specific runtime setup.
- Publication record
- A confirmed release, kept separately from drafts and metadata edits.
Check the runtime before calling it live.
A completed coding task is not evidence that a public application is working. The managed-app workflow asks for build verification, process and listener checks, and local HTTP health before an app is considered ready for exposure.
Once the app is ready and publishing is within your request, Ghost can expose its route and use the exact returned URL. It should not invent a live address from a project name or report a preview as a published app.
Those checks establish readiness for this step, not a blanket security certification or uptime guarantee. The application still needs the testing, access controls, and review appropriate to the data it handles.
Build complete is not publication complete.
- Prepared
- The app build and runtime have been checked.
- Exposed
- The publishing service returns the actual live route.
- Verified
- The intended page or app is checked at the returned URL.
- Recorded
- The confirmed version is saved in Published.
Keep the live version connected to later changes.
After a verified publication, Ghost explicitly records the route and version in Published. Exposing a route alone does not save that catalog entry. Changing an app’s title or repository metadata does not deploy new code.
For a later update, continue with the same app, verify the revised live output, and record the confirmed version. If the route itself changes, the new route must be returned by the publishing service and checked before it is recorded.
A release note can keep the purpose, decisions, and known limitations close to the work. For file or host-side preparation, computer tools remain a separate capability with their own permissions.
- Metadata edit
- Changes a saved title or repository reference; it is not a deployment.
- App update
- Changes implementation and requires verification of the resulting app.
- Release record
- Keeps a confirmed live version associated with the same managed app.
Archive and unpublish are different decisions.
Archiving hides the record from the normal Published view. It does not turn off the live route. If the goal is to stop public access, ask to unpublish the exact app rather than relying on archive.
Permanent deletion in the managed-app workflow removes the app’s bound live routes and catalog history after an explicit request. If route removal fails, the workflow stops rather than pretending the app has disappeared.
The source workspace is retained for recovery. That distinction matters: taking an app offline, removing its catalog record, and erasing its source code are not interchangeable actions.
- Archive
- Hide the catalog record while keeping the URL live.
- Unpublish / delete
- Explicitly remove bound live routes and the managed catalog record.
- Source workspace
- Retained by this deletion workflow rather than silently erased.
Product details
Publishing, at a glance.
Supported work, useful outputs, and what to check before you start.
- App identity
- Create or select the managed app that owns the source, build, and deployment setup. Temporary experiments remain separate from durable published work.
- Release record
- A confirmed route and live URL identify a published version. Updating catalog metadata alone does not deploy an application.
- Control
- Publication is an external-facing action. Archiving a saved record only hides the record; it does not take its live route offline.
One assistant. Connected work.
Ghost is a personal AI assistant for Mac. Publishing is a capability of the same product as Meetings, Notes, To-dos, Browser, and Memory. Bring the relevant records into the next task without treating each capability as a separate app.
Start with a useful idea in Notes, build the managed app through the coding workflow, and publish only when its runtime is ready and sharing is intended. Later changes return to the same app rather than losing the connection to what is live.
- Coding agents
Implement and revise the managed app.
- Sandboxes
Keep experimentation separate from publication.
- Computer
Handle permitted host-side preparation and inspection.
Questions about publishing with Ghost.
Does publishing create the app too?
App implementation and publishing are connected but distinct. Ghost’s app-scoped coding workflow handles the code, dependencies, build, and runtime setup. Publishing exposes and records the verified result.
Will a finished coding task automatically go public?
No. Readiness is not public exposure. Publishing must be within your request, and Ghost must use the confirmed route returned by the publishing service.
Does this publish native iOS or Android apps?
This page describes managed web-app publishing. It does not promise native mobile packaging, app-store review, or submission to Apple or Google.
Can I update an app after it is published?
Yes. Continue with the same managed app, verify the updated live output, and record the confirmed version. A metadata-only change does not update its deployed code.
Does archiving take the app offline?
No. Archive hides a record but leaves its route live. Permanent unpublishing is a separate explicit action against the exact app.
Is hosting free or guaranteed to stay online?
This page does not make a free-hosting or uptime promise. Ghost is in private beta, and availability depends on the configured publishing runtime and the requirements of the app.
Keep the build and the live app connected.
Move from a working project to a verified publication with a clear record of what is live. Ghost is in private beta for macOS.
Request access