Skip to main content
Once your Plan Cast is complete and all quality checks have passed, it is time to go live. Deploying your product means making it available to real users on the internet.

​
Before you deploy

Make sure you have:
  • Completed the Plan Cast (status shows “Ready to Deploy”)
  • Reviewed the audit reports (security, accessibility, performance, code quality)
  • All cloud accounts connected (GitHub, Vercel, Convex)
Transmuter will not let you deploy until all required quality checks pass. This ensures your product meets production standards before going live.

​
One-click deployment

1

Open the deployment screen

Navigate to your project and click the Deploy tab. You will see a summary of your product’s readiness, including audit scores.
2

Review the deployment summary

The summary shows: - Where your code will be pushed (GitHub repository) - Where your product will be hosted (Vercel) - Where your data will be stored (Convex) - Your product’s initial URL
3

Click Deploy

Click the Deploy button. Transmuter handles everything:
  1. Pushes your code to GitHub
  2. Deploys to Vercel
  3. Sets up your Convex database
  4. Configures environment variables
  5. Runs a final health check
This process typically takes 2-5 minutes. A progress indicator shows each step.
4

Your product is live

Once deployment is complete, you will see your product’s live URL. Click it to visit your newly launched product.
Bookmark your product’s URL, and share it with early users or testers to start getting feedback.

​
After deployment

Once your product is live, you can:
  • Visit the Post-Launch Hub to monitor health and submit feedback
  • Set up a custom domain for a professional URL
  • Share your product with users

​
Rollback

If something goes wrong after deployment, Transmuter supports rolling back to the previous version. Navigate to the Deploy tab and click Rollback to restore the previous deployment.
Rolling back replaces the current live version with the previous one. Any data changes made by real users between deployments are preserved in the database — only the application code is reverted.