Publish App

Go Live

Once you've previewed your application and everything looks correct, it's time to publish. Publishing makes your app accessible at its public URL: yourapp.obto.co.


How Publishing Works

OBTO applications are live the moment their artifacts are deployed. There is no separate "build" or "release" step. When the AI writes code using obto_upsert_record or obto_create_route, that code is immediately available on the platform.

What "publishing" means on OBTO:

  • Your application's pltf_page records are served when someone visits the host URL

  • Your API routes are active and callable

  • Your server scripts are running and available via xe.

If you've deployed all artifacts and the host is set correctly, your app is already live.


Your App URL

Every OBTO application gets a URL based on its host configuration:

https://{appName}.obto.co

The host field on your browser-facing artifacts (pltf_page, pltf_javascript, pltf_stylesheet) determines which URL serves them. All artifacts that belong to the same website must share the same host value.


Publishing Checklist

Before sharing your app URL, verify:

Check
How

✅ All server scripts deployed

AI used obto_upsert_record with pltf_script_server

✅ All routes deployed

AI used obto_create_route

✅ All stylesheets deployed

AI used obto_upsert_record with pltf_stylesheet

✅ All JavaScript modules deployed

AI used obto_upsert_record with pltf_javascript

✅ All pages deployed

AI used obto_upsert_record with pltf_page

✅ Host values are consistent

All browser-facing artifacts use the same host

✅ Preview looks correct

Generated and checked via obto_generate_preview


Deployment Order Matters

If your app has both frontend and backend, always ensure the AI deployed in the correct order:

If the AI deployed out of order, your page may fail to load. Ask the AI to redeploy the page:


Updating a Published App

Published apps are updated in real-time. When the AI modifies any artifact:

  • Changes are immediate — No build step, no deploy pipeline, no CI/CD

  • No downtime — The platform hot-swaps the updated artifact

  • Rollback — The AI can fetch the current version, restore it, and redeploy

To update, just continue the conversation:


Custom Domains

By default, your app is served at yourapp.obto.co. Custom domain configuration is available for production deployments. Contact [email protected] for custom domain setup.


Next Steps

  • App Preview — Preview changes before publishing

  • MCP Tools - OOB — Review the tools used for deployment

Last updated