Skip to main content
specific deploy takes your project from local development to a fully running production environment — provisioning infrastructure, building your code, and deploying your services with a single command.
specific deploy

Prerequisites

  • A specific.hcl file in your project (your coding agent creates this)
  • A Specific Cloud account (the command will prompt you to log in on first use)

First deploy

When you run specific deploy for the first time, the CLI walks you through a short setup flow:
  1. Login — Your browser opens to authenticate with Specific Cloud. You only need to do this once; the session is saved for future deploys.
  2. Project selection — Choose an existing project or create a new one. The project ID is saved to .specific/project.json so subsequent deploys skip this step.
  3. Deploy — Your project is built, infrastructure is provisioned, and services go live.
After the first deploy completes, future deploys are a single command with no prompts (unless new secrets or config values need to be set).

Public URLs

Services with endpoint { public = true } get a public HTTPS URL after deployment. The URLs are displayed in the terminal when the deploy completes. If you want to add a custom domain, you can do so in the Specific Dashboard. All public endpoints are served over HTTPS with TLS handled automatically. Services without a public endpoint are only accessible internally by other services.

Learn more