THE SPINUP FIELD GUIDE/ PRACTICAL KNOW-HOW

Your first steps with SpinUpVPS.

A practical path from choosing a plan to making your new Linux environment ready for your application.

SpinUpVPS·2 min read

Before placing the order

Review the CPU, memory, NVMe storage and transfer allocation on the product page. Select a location. If you need a particular operating system, IP arrangement, delivery date or managed service, ask us to confirm it before paying.

These plans are self-managed. Decide who will install updates, manage access, monitor the application and maintain independent backups.

Review billing and complete checkout

Your cart shows the selected plan and location. Checkout shows the payable total, including any applicable taxes, and the available payment methods. Use an email address you can reliably access.

A standard monthly product covers one month and needs a separate renewal payment. A subscription is labelled explicitly and has its own recurring terms. Keep a copy of the order confirmation.

Know what happens after payment

A payment receipt confirms an order transaction, not a running VPS. Server access follows payment confirmation, any necessary order checks and provisioning. Your service arrangement confirms the activation and expiry dates.

We arrange access details through the agreed delivery method. Never send a private SSH key, an account password or full payment-card information by email.

Make the first login deliberate

Follow the instructions supplied for your chosen operating system and access method. Confirm the destination, account and connection details. Verify the server’s host identity through a trusted channel before accepting an unexpected SSH host-key change.

Check that you have a recovery route before you tighten access controls. Keep the existing working connection open while verifying a new user, SSH key or firewall rule.

Prepare the environment

Install operating-system updates, configure appropriate users and network rules, and restrict exposed services to the ones you need. Use the current documentation for your Linux distribution rather than copying settings from an unrelated system.

Record the application versions and deployment steps. Keep secrets out of repositories and restrict permissions to the people and processes that need them.

Plan for day two

Set up independent backups, test a restore and monitor disk space, memory and application health. Confirm the renewal process and keep account contact details current.

Keep going

A few decisions about access and recovery now can make the next month much easier.

Build your security baseline ↗

KEEP YOUR IDEAS MOVING

A little more reading.