Deploying

Ship to production on Calvin or deploy to your own infrastructure

Calvin provides two paths to production: deploy directly to Calvin's managed infrastructure for instant deployment, or connect your repository to your own CI/CD pipeline and deploy wherever you choose.

To deploy on Calvin, click the Deploy button in the workspace toolbar. A panel opens with the message "Ready to Deploy?" and offers to configure your project for instant deployment. Calvin optimizes your build and configures everything automatically, setting your application to run on port 8080. Click "Configure Project" to proceed, and Calvin handles the rest — building, optimizing, and deploying your application to Calvin's hosting infrastructure.

Deployed applications consume Runtime credits (as opposed to Builder credits, which are consumed during agent execution). Runtime costs cover the compute, database, storage, and other resources that keep your application running. You can monitor these costs in the Usage Analytics section.

Once deployed, the three-dot menu in the workspace toolbar provides access to runtime monitoring features. Open App launches your deployed application in a new tab. Traffic shows real-time traffic data for your application. Web Analytics provides visitor analytics and engagement metrics. Web Performance displays performance metrics to help you identify and resolve bottlenecks.

For teams that prefer to deploy to their own infrastructure, Calvin integrates seamlessly with external Git providers. By connecting your workspace to a GitHub, Bitbucket, or GitLab repository (configured in workspace settings), all code changes are pushed to your repository. From there, your existing CI/CD pipeline can pick up the changes and deploy them wherever you need — AWS, Google Cloud, Vercel, Netlify, or any other hosting provider.

When using the external deployment approach, configure your chat closing action to either "Merge and Push" (for automatic merges that trigger your CI/CD pipeline) or "Create Pull Request" (for a review step before deployment). This keeps Calvin's output flowing into your existing deployment workflow without requiring any changes to your infrastructure.