Easily deploy your project.
Deploy from your project, a Git repository, or a ready-to-run image. Publish updates through the same workflow as your project evolves.
$ shpyrd deploy==> Archiving HEAD (654f4925638e)==> Uploading source (2.6 KiB)==> Building===> detect4 of 9 buildpacks participating===> export==> Releasing Running: web 3/3 · worker 1/1Released v3: Deploy 654f4925638ehttps://shop.acme.shpyrd.appPublish it. Open it. Publish the next version.
An existing site or app, from the first deployment to the next change.
- 1
Deploy the project
From your project folder, a Git repository, or a container image. The build runs as part of the deployment.
- 2
Open it
The app gets its address, and you can use your domain.
- 3
Publish the next version
Make a change and deploy again. Each deployment is recorded as a release.
What makes it work
Code, Git, or an image
Deploy local project code, a Git repository, or a container image.
Build in the workflow
Supported projects are detected and built as part of the deployment, with build configuration when you need it.
Every deployment a release
Later deployments are recorded as releases you can review.
CLI and API
The same workflow works from the CLI and the API, for developers, scripts, and agents.
Use your domain
Every app gets an address. Use your domain, such as acme.com or app.acme.com.
Ask your agent
An agent can deploy through the authenticated CLI. Tell it: "Publish this app."
Practical questions
Does every project deploy without configuration?
Supported projects are detected and built for you. Some projects need build configuration; the deployment guide explains the options.
Can my AI agent deploy for me?
Yes, through the authenticated CLI or API. The workspace MCP connection is for inspecting projects, logs, and metrics, not for deploying.
Can I use my domain?
Use your domain.
Which project should we put online?
Deploy it, open it, and publish the next version from the same workflow.