Your app, database, and background processes. In one place.
Deploy your application or API, connect PostgreSQL, and add the background processes and persistent storage your project needs. Keep the application's resources together as it grows.
project: purchase-requestsprocesses: web: port: 8080 worker: command: ["node", "worker.js"]A booking app, its data, and its background work.
Each part does a job the app needs.
Step 1
The app takes a booking
A web app or API serves the request.
Step 2
PostgreSQL keeps it
The booking is saved and read back later.
Step 3
A worker does the rest
A background process handles a task, such as sending a document to an external AI service.
What a project can run
Web apps and APIs
Your application, with or without a browser interface.
Background workers
Processes that do work outside a request.
PostgreSQL
A database for the information your app saves.
Redis or Valkey
For compatible caching and queue use cases.
Persistent storage
Volumes for the files your application keeps.
Adjustable capacity
Connections, configuration, and sizes managed with the project.
Practical questions
Does a simple website need a database?
No. Add a database when your app needs to save information.
Does capacity grow with traffic on its own?
Capacity is adjustable: you set the process counts and resource sizes your project needs.
Does Shpyrd provide the booking or payment logic?
No. Shpyrd runs your application and its supported resources. Your code and the services you choose provide the business functionality.
A place for your app and its data.
Deploy the application, connect PostgreSQL, and add the worker it needs.