For developers

Easily deploy your project.

Keep deployments, databases, and operation in one workflow, so you can focus on developing the project. Whether it is for you, a client, or your company.

Deploy a projectRead the getting-started guide
Terminal~/projects/shop
$ 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.app

The first deployment, the next change, the release history.

Try it with a project you are already developing.

  1. Step 1

    Deploy

    From local code, Git, or a container image.

  2. Step 2

    Connect what it needs

    PostgreSQL, Valkey, workers, and volumes in the same project.

  3. Step 3

    Release, inspect, roll back

    Follow the logs, review releases, and roll back code and configuration.

What comes with it

  • Web and worker processes. Keep web processes, workers, and connected resources in the same project.
  • Logs and metrics. Build and application logs, resource and traffic metrics.
  • CLI and API. Script it, or let your agent drive the CLI.
shpyrd.yaml
project: purchase-requestsprocesses:  web:    port: 8080  worker:    command: ["node", "worker.js"]

Practical questions

This is a client project.

That fits. Shpyrd can support the publication and updates of applications you build for clients.

I already have hosting.

Try Shpyrd with one project and compare the workflow from the first deployment through the next update.

Does rollback undo database migrations?

No. Rollback returns application code and configuration; it does not reverse migrations or saved data.

Which project should we put online?

Deploy it, then publish a second version and evaluate the workflow.

Deploy a project

Web Apps & APIsEasy DeploymentApps & Databases TogetherProject Management & Visibility