OFFSHORE VPS / SEED
Seed.
A small app, with room to learn.
A lightweight API, a personal tool or a staging environment. Measure memory before adding a database on the same instance.
Start with these resources.
- Compute
- 1 vCPU
- Memory
- 1 GB
- Storage
- 25 GB
- Transfer budget
- 1 TB
Adjust resources, image, network options and the service period in the configurator. Choose Malaysia, Romania or Switzerland as the server location, with no location surcharge. Backup countries remain unconfirmed.
Plan around the whole workload.
Memory is shared by every process on the instance. Include database caches, job queues and your deployment process, and test at an expected busy period.
Build a resource budget →Know what you own.
Plan for application security, updates, observability and an independent recovery process. If you select a backup option, review the restore procedure and test it against your application.
Prepare your first restore drill →A simple starting plan for a lightweight app.
A single lightweight API or personal tool is a useful candidate to measure against Seed. Write down whether its data lives in an embedded database, a local database process or an external service: those choices change the memory budget. An application that is idle most of the day can still need extra room during a dependency build or export.
A worked starting point
An illustrative bookmark API serves short responses and stores a small collection. Start by observing the runtime, data process and one export separately. Keep uploads, logs and old release folders visible in the disk budget. This example has no guaranteed visitor or request capacity.
When this starting point is a poor fit
Choose a larger memory budget if the runtime and database already consume most of the available RAM before real work starts. Do not assume swap will make an oversized stack comfortable. If your chosen image requires 2 GB in the configurator, add memory or select a compatible image; this does not happen silently.
Give every option a job.
The base configuration contains 1 vCPU, 1 GB RAM, 25 GB storage, a 1 TB transfer budget and 1 IPv4 address. IPv6 is requested separately and no backup option is selected by default. These are catalogue allocations; confirm the actual supplier’s hardware, counting and restore rules.
- Memory: leave room for the operating system, runtime, database and observed peaks. Adding 1 GB to Seed gives a monthly subtotal of $8.50 before term savings.
- CPU: compare the processes doing work and their concurrency. It does not describe a guaranteed processor model or requests per second.
- Storage and transfer: budget retained data separately from the bytes you move. Off-server exports may use both.
- Backups and networking: define the data you need back and the addresses your application uses. Selecting an option does not document the operating procedure for you.
Make the first review concrete.
Record a normal operating period, one heavier task and one release. Note memory available, the largest growing directories and the result of a local application check. Keep a small change log so an unexpected result has a starting point. Then compare the selected period’s whole upfront total in the configurator; a longer term changes the price, not the resources.
Explore a small tools workload → · Build a resource worksheet · Check catalogue facts and service boundaries