App Builder

Publishing

Publishing - Opulent documentation

Publishing

Deploy your application to production with a single instruction

Deploying Your App

When you're ready to go live:

"Deploy this to Vercel and give me the URL"
"Deploy to production"
"Push to GitHub and trigger a deployment"

Opulent handles the entire process:

  1. Builds the production bundle
  2. Pushes code to your GitHub repository
  3. Triggers the deployment to your configured host
  4. Returns the live URL

Deployment Targets

PlatformNotes
VercelRecommended for Next.js apps. Zero-config. Global CDN.
NetlifyGreat for static sites and JAMstack apps
RailwayFull-stack apps with a database
Fly.ioContainerized apps, global edge deployment
RenderFull-stack with background workers and databases
CustomSpecify your own server: "Deploy to our EC2 instance at [IP]"

Preview vs. Production Deployments

Preview deployment:

"Deploy to a preview URL so I can share it for review"

Gets a temporary URL for stakeholder review without replacing the production deployment.

Production deployment:

"Deploy to production"

Updates the live production URL.


Environment Variables

Before deploying, specify your secrets:

"Set the following environment variables for the Vercel deployment:
DATABASE_URL, STRIPE_SECRET_KEY, NEXT_PUBLIC_APP_URL"

Opulent configures these in your deployment platform — they are never stored in the repository.


Custom Domains

"Set up custom domain: app.yourcompany.com"

Opulent configures the domain in your deployment platform and provides DNS records to add. See Custom Domains.


Redeployment

After making changes:

"Redeploy with the latest changes"

Or changes can be deployed automatically after each edit session — configure this in Settings → App Builder → Auto-deploy.


Checking Deployment Status

"What's the status of the current deployment?"
"Did the last deployment succeed?"

Opulent queries the deployment platform and reports build logs, status, and any errors.