Having credentials to a cloud account is not the same as being ready to use it. Providers expect certain things to be in place before an account is operated in earnest, and skipping them leads to suspended services, failed launches or a lockout at the worst possible moment. This checklist covers what to have ready, using Linode (now part of Akamai Cloud) and Vultr as working examples because both are simple enough to see the requirements clearly.
Accurate contact details
Every provider ties an account to an email address, and most also want a name, an organization where relevant and a physical address for tax and invoicing. These details are not decorative. They are where password resets, billing notices, abuse reports and security alerts go.
Before deploying anything, confirm that the email on the account is one your team monitors, that recovery options point to people who will still be around next year, and that the address information is correct for your billing region. On Linode this lives in the Cloud Manager profile and account settings; on Vultr it is in the account section of the customer portal.
A valid payment method
Credits and trial balances are temporary. When they run out, the account continues under standard rates only if a valid payment method is attached. The Linode fact page is explicit that services continue once credits are exhausted only when a payment method is in place, and the same logic applies on Vultr.
The listed options on the marketplace show why this matters. The Buy Linode Account page lists a “Linode $100 Credit Account”, and the Buy Vultr Account page lists “Vultr $200 Credit Account”, “Vultr $250 Credit Account” and “Vultr $300 Credit Account”. A balance is a buffer, not a plan. Attach a payment method early, understand any spending limits or holds on the account, and know when the balance expires.
Secured credentials
Whether you created the account yourself or took control of it legitimately, the first session should be about security rather than servers. The steps are the same on both providers:
- Change the password to one that is unique to this account.
- Enable two-factor or multi-factor authentication on the root identity.
- Review every user, grant and team member, and remove anyone you do not recognize.
- Rotate existing API tokens and SSH keys, since anyone who previously held them can still act.
- Inspect all existing instances, volumes and services and remove unknown resources.
The security baseline after receiving credentials goes through each of these in more detail, and rotating API keys and access tokens covers the rotation procedure step by step.
Clear ownership and the provider’s terms
Ownership is a requirement, not a formality. Providers write their terms of service around the party that holds and operates the account, and both Linode and Vultr reserve the right to act on accounts that breach those terms or eligibility rules. Promotional credits in particular are often restricted to new customers and may be non-transferable.
Practically, this means you should be able to answer three questions in writing: who is the responsible owner of this account, which entity is paying for it, and what terms govern its use. Keep that record with your other infrastructure documentation. If control of an account changes within the provider’s rules, the cloud account handover checklist lists what to update.
Verified limits that match your plan
New and low-spend accounts typically carry service-creation limits. On Linode, larger plans and GPU instances may be gated until limits increase; Vultr similarly restricts certain configurations early on. Check the actual limits in the console or through the API before promising a client a particular deployment.
| Requirement | Where to confirm on Linode | Where to confirm on Vultr |
|---|---|---|
| Contact and billing details | Cloud Manager account settings | Customer portal account section |
| Payment method | Billing pages | Billing pages |
| Two-factor authentication | Profile security settings | Account security settings |
| API tokens and SSH keys | Profile tokens and keys | Account API and SSH keys |
| Creation limits | Console or API | Console or API |
Operational capacity
The final requirement is about your team rather than the account. Both providers are largely self-managed: you hold root on the machines, so operating-system updates, firewalling, backups and monitoring are yours to handle. If nobody on the team has time for that, a managed service may fit better than raw virtual machines.
Once contacts, payment, security, ownership and limits are all confirmed, the account is genuinely ready. Everything after that is normal cloud operations. Further provider-specific questions are answered in the Linode and Vultr sections of the cloud FAQ.
