What standalone services are
Most real apps need more than just their own code to run — somewhere to store data, somewhere to keep files, a way to send email. In The Deployer these are called services: managed building blocks you create once and then attach to any project you like.
What a "service" is here
A service is a piece of cloud infrastructure that your app talks to. You create it on its own — separate from any project — in the Services area, and it lives there until you attach it to one or more projects. Think of them as reusable Lego bricks: build the brick once, snap it onto whichever projects need it.
There are five categories:
| Category | In plain words | You'd use it for |
|---|---|---|
| Database | An organized, permanent store for your app's data | User accounts, orders, posts — anything that must be remembered |
| Cache | A fast, temporary store that speeds your app up | Remembering results so your app doesn't recalculate them every time |
| Queue | A waiting line for background jobs | Sending emails or processing uploads without making the user wait |
| Storage bucket | Cloud file storage | Images, PDFs, user uploads, backups |
| A verified sender so your app can send mail | Sign-up confirmations, password resets, notifications |
If a word like "cache" or "queue" is new to you, that's fine — you rarely need to pick one yourself. Your project's code already expects certain services, and when you attach one, an AI agent checks whether it's the right fit (see attaching a service to a project).
Why create a service separately from a project
- Reuse. One database can back several projects, or several parts of the same project.
- Clarity. Each service has its own page showing its status, cost, connection details, and which projects use it.
- Safety. An agent reads your project's code before wiring anything in, so you don't accidentally connect the wrong kind of service.
Each service belongs to one cloud provider
When you create a service you pick which of your connected clouds it lives on — AWS, Google Cloud, Azure, or DigitalOcean. The available categories and engines differ slightly by provider (for example, DigitalOcean has no built-in queue), and The Deployer only ever shows you what that provider genuinely offers. You'll need at least one cloud connection before you can create anything.
Services cost money
A service is a real, billable resource in your cloud account, so your cloud provider bills you for it — every service page shows an estimated monthly cost (for example ~$15/mo) before and after you create it, so you always know what you're committing to. Deleting a service tears down the underlying cloud resource, so you stop paying for it.
What's next
- Create a service — the step-by-step wizard.
- Attach a service to a project — how the compatibility check and wiring work.
- Sending email — the special setup for email services.