Which Docker VPS fits this illustrative shape?
For one API process with a modest worker and no local database, Dev 1 is a small planning candidate only if measured memory, storage and release overlap fit its 1 vCPU, 2 GB RAM and 30 GB storage. App 2 is the clearer starting comparison for one API process, one bounded worker and an optional compact database: 2 vCPU, 4 GB RAM and 60 GB storage. Scale 4 is a comparison point when observed memory or concurrent work needs more room. These allocations do not predict requests, jobs or availability.
| Profile | Resources | Monthly | Amount due | Amount due | Next step |
|---|---|---|---|---|---|
| Dev 1 | 1 vCPU · 2 GB RAM · 30 GB storage | $6.00 | $25.92 / 6 months | $36.00 / 12 months | Configure Dev 1 in Switzerland |
| App 2 | 2 vCPU · 4 GB RAM · 60 GB storage | $12.00 | $51.84 / 6 months | $72.00 / 12 months | Configure App 2 in Switzerland |
| Scale 4 | 4 vCPU · 8 GB RAM · 120 GB storage | $24.00 | $103.68 / 6 months | $144.00 / 12 months | Configure Scale 4 in Switzerland |
The six- and twelve-month columns are full amounts due upfront. They do not add resources, Docker, a database or a managed application service.
Budget the process shape before selecting a profile
Write down the API process, a worker only when asynchronous work is required, and a database only when it must run on this VPS. Add host overhead, an image pull or release overlap, volumes, logs and a reserve. Keep database memory and storage separate from the API’s quiet-state figures. If the worksheet does not fit with a reserve, reduce the shape, use a larger profile or separate a component after measuring the actual constraint.
Expose only the API path you intend to operate
A container port publish rule and host filtering are separate controls. Publish only the API port and interface your request path needs; keep database, administration and diagnostic ports off public interfaces unless you have a documented reason. Keep an administrator access path, deploy credentials and application secrets under your own control. The container exposure guide gives the procedural checks; this page does not configure them for you.
Treat volumes as state that needs a recovery decision
List database files, uploads, generated output and configuration references that live in or beside a volume. A volume backup is useful only after an isolated restore and application-level check prove it is compatible with the selected artifact and database version. Keep recovery material outside the host failure boundary when that is the failure you need to survive. Use the isolated database restore guide and application recovery checklist for the procedure.
Install, update and verify your own stack
You choose the Linux image in the configurator, install Docker and the application, manage images, updates, credentials, monitoring and recovery. PrivacyNodes does not preinstall Docker, expose an application panel, verify payment from this page or provision a VPS from a browser click. Select Switzerland or Panama, then review the explicit crypto asset/network and one-hour quote in the purchase flow.