Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
An App is just the wrapper. Components do the work.
Inside an App you can have Web Services (APIs/backends), Static Sites (frontend builds), Workers, Scheduled Jobs, and Functions. The App groups them together for networking, env vars, deploys, and billing.
You always create an App, then add the components you need.
Make sure to check out the docs here:
https://docs.digitalocean.com/products/app-platform/how-to/manage-components/
Heya,
On App Platform, an “App” is basically a container for one or more components. If you add both your frontend and backend under the same App (same app spec / same create flow), it will show them as a single App Platform “instance” with two components (often a Static Site + a Web Service). That’s normal and usually recommended because deployments, domains, env vars, and internal routing are easier to manage together.
Regards