Skip to main content
Deploy a project when a release is ready to run in an environment.

​
Steps

  1. Confirm the target environment has the right variables and secrets.
  2. Create a release from project work.
  3. Deploy the release to an environment.
  4. Configure domains when the deployment needs public routing.
  5. Inspect deployment and server state.

​
Try it with REST

Create a release: POST /projects/{project_reference}/releases
Terminal
curl -X POST https://api.veryfront.com/projects/support-assistant/releases \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production release"
  }'
Deploy the release: POST /projects/{project_reference}/deployments
Terminal
curl -X POST https://api.veryfront.com/projects/support-assistant/deployments \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "release_id": "<RELEASE_ID>",
    "environment_id": "<ENVIRONMENT_ID>"
  }'

​
API surfaces

SurfaceStart here
RESTReleases, Deployments, Project Servers
GraphQLCreate Release, Create Deployment
MCPCreate Release, Create Deployment

​
Verify

List deployments and confirm the release is assigned to production. Check server state before sending production traffic to the deployment.

​
Deployment surfaces

SurfaceUse it for
EnvironmentRuntime configuration and deployment target.
ReleaseVersioned project work that can run.
DeploymentRelease assigned to an environment.
DomainPublic routing for deployed work.
ServerLong-running runtime capacity.

​
API reference

APIUse
RESTEnvironments, domains, deployments, releases, and servers.
GraphQLDeployment, domain, release, environment, and server views.
MCPDeployment, domain, release, environment, and server tools.