Knowledge
Cloud Library
Reference entries on cloud account structure, provider infrastructure, compute and storage concepts, networking, billing, security and migration. Each entry covers one subject and links to the listings and comparisons it relates to.
FundamentalsWhat a Cloud Account Actually IncludesAn account is an identity, a billing relationship and a container for resources. Separating the three explains most of the confusion around cloud accounts.FundamentalsRegions and Availability Zones: Why Placement MattersWhere a server physically sits affects latency, resilience, price and sometimes legal obligations. A short guide to choosing placement deliberately.FundamentalsVirtual Machines, VPS and Instances: The Differences That MatterThree words for roughly the same thing, with differences in billing, lifecycle and expectations that show up as soon as you run something real.FundamentalsHow Cloud Billing Models WorkOn-demand, committed, spot and promotional balances behave differently. Knowing which one is paying for a resource explains most unexpected invoices.FundamentalsQuotas and Service Limits ExplainedQuotas cap what an account may launch, vary by region and service, and change with account history. They explain most launch failures that are not billing failures.FundamentalsWhat “Upgraded” Means on a Cloud AccountUpgraded describes the billing side of an account rather than its hardware. It usually means verification is complete and trial ceilings no longer apply.FundamentalsTrial Accounts and Paid Accounts: What Actually ChangesA trial is not a discounted paid account. It behaves differently at the moment the balance runs out, and that difference decides what you can safely run.ReferenceA Plain-English Glossary of Cloud Infrastructure TermsShort, practical definitions of the terms that appear constantly in provider consoles and account listings, with the distinctions that actually matter.FundamentalsHow to Size Your First Cloud ServerStart smaller than feels comfortable, measure the right things, and resize once you have evidence. A practical method that avoids both extremes.Google CloudGoogle Cloud Accounts: Projects, Billing and Credit HeadroomGoogle Cloud separates the project from the billing account, which shapes how credit, quotas and ownership behave. A guide for teams evaluating a GCP profile.AWSAWS Account Anatomy: Root, IAM and Service LimitsAn AWS account is a hard security and billing boundary. Understanding root, IAM and per-region limits is most of what you need to use one safely.KamateraKamatera and the Configurable Server ModelKamatera lets you assemble CPU, memory and storage independently rather than choosing from fixed sizes. That changes how you plan capacity.AzureAzure Subscriptions, Tenants and Pay-As-You-GoAzure layers a directory, a subscription and resource groups. Knowing which layer holds identity, which holds billing and which holds resources prevents most confusion.DigitalOceanDigitalOcean Droplets and the Case for Simple ComputeDroplets are deliberately plain virtual machines. That simplicity is the product, and it suits a specific and fairly large set of workloads.Oracle CloudOracle Cloud: Tenancy, Compartments and the Upgrade PathOracle Cloud organises everything under a tenancy divided into compartments, and draws a sharp line between trial and upgraded state.OVHcloudOVHcloud: European Infrastructure and vCPU ProfilesOVHcloud operates its own European data centres and hardware, which shapes its pricing, its data-residency story and the way capacity is described.HetznerHetzner and the Price-to-Performance ArgumentHetzner is chosen mainly for how much compute a given budget buys in European data centres. Here is what that focus includes and what it leaves out.LinodeLinode: Control Panel, API and Developer ErgonomicsLinode built its following on a clear control panel and a predictable API. Those ergonomics are the product as much as the underlying compute.UpCloudUpCloud and Why Storage Performance Shows Up EverywhereUpCloud is known for fast block storage. Storage latency affects far more of an application than people expect, which is why it is worth understanding.HandoverThe First Hour After Taking Over a Cloud AccountAn ordered checklist for the first sixty minutes, arranged so that each step closes a door before the next one opens something.AccessRotating Credentials and API Keys Without Breaking DeploymentsRotation fails when it is done as one big-bang replacement. Overlapping credentials make it routine instead of risky.HandoverDocumenting a Cloud Account HandoverA short written record of what was received and what changed turns a vague inheritance into something a team can operate and audit.AgenciesManaging Multiple Cloud Accounts Across Client ProjectsSeparate accounts per client solve billing, access and handover problems that shared environments create. The overhead is real but manageable.AccessRecovery Options: The Access Path People ForgetRecovery email, phone numbers and codes are a second key to the account. Leaving them unchanged undoes every other security step.