What is an app pod? Your frontend, backend and data together
Understand the App Cities pod: an isolated home for your Docker services, not an empty VPS or a database you have to buy separately.
App Cities · 2 min · Updated
A pod is the place where your app runs. It can hold your frontend, backend and database. Docker runs these parts as containers. Each container has a job. They share the pod's CPU, RAM and disk. You choose the size of the pod, not a separate server for every part.
The steps
- Think in services first. Identify which component receives web requests and which components should remain private.
- Use Compose service names for private connections. Your API can reach a database service without exposing that database to the public Internet.
- Choose capacity for the combined workload. All services share the pod's memory, CPU and disk, so the database is part of the sizing decision.
- Use the dashboard to follow deployments, inspect logs and control the pod. Review the current quote before changing its capacity.
A common question
Does App Cities choose my database?
No. Your project defines its stack. The platform validates the deployment against its supported configuration and safety rules.
Ready to try your project?
Prepare your project, check the prices and choose how you want to deploy.