Buy IBM Cloud Accounts

How an IBM Cloud account is organized

IBM Cloud combines the infrastructure business IBM acquired with SoftLayer, a newer VPC generation of compute and networking, managed Kubernetes and Red Hat OpenShift, a wide catalog of managed databases, and the Watson and watsonx families of AI services. When you Buy IBM Cloud Accounts on CloudAccountHub, the listing you receive is an IBM Cloud account described exactly by its variant label, and everything you create inside it is billed by IBM under IBM's own terms. This section explains the structure behind the login.

Account types: Lite or trial, Pay-As-You-Go, Subscription

The account type governs what you can create and how you are billed. For several years IBM offered a Lite account with no payment method and access to free Lite plans; IBM has since moved new sign-ups toward a trial model that explores the platform for a limited period under conditions IBM publishes and changes. Either way, the practical meaning for a buyer is the same: an entry level account with limits set by IBM, not a billing account with an open ended spending line.

A Pay-As-You-Go account has a payment method on file and is billed monthly for actual usage at IBM's published rates. It unlocks the full catalog, including Virtual Servers for VPC, bare metal, Kubernetes worker nodes, and paid Watson and watsonx plans. A Subscription account commits to a spending amount over a term in exchange for a discount. Upgrading from a trial to Pay-As-You-Go is done with IBM directly by adding your own billing details in the console, subject to IBM's checks and terms. Separately, many services carry a Lite or free plan that any account can use at no charge within its allowance. IBM lists those plans on its free tier page; the allowances are set by IBM and subject to change without notice.

Resource groups

Inside an account, resources are organized into resource groups: logical containers for service instances, clusters, virtual servers, buckets, and anything else created from the catalog. Every account starts with a Default resource group, and you can add more to separate projects, environments, or customers. A resource is placed in a group at creation and, for most services, cannot be moved afterwards, so decide on a scheme on day one. Resource groups are the boundary that IAM policies most often target, and billing reports can be filtered by them, so one group per client or cost center gives you both access separation and a cost breakdown without extra tooling.

IAM access groups and policies

IBM Cloud Identity and Access Management controls who can do what. Users are invited by email and authenticate with an IBMid. The recommended pattern is to create access groups, put users and service IDs in them, and attach access policies to the group. A policy names a subject (the access group), a target (the account, a resource group, a service, or a single instance), and one or more roles.

Roles come in two families. Platform roles, Viewer, Operator, Editor, and Administrator, govern management actions such as creating or deleting an instance. Service roles, Reader, Writer, and Manager, govern what an identity can do with a service's data or API. Service IDs are non-human identities for applications and pipelines, each with its own API keys, and trusted profiles let compute resources assume access without long lived keys. Administrators can enforce multifactor authentication account wide.

Console, CLI, and API

The IBM Cloud console at cloud.ibm.com is the web interface: the catalog, the resource list, IAM, billing, and per-service management pages. The same operations are exposed through the ibmcloud command line tool, which uses a plugin model: the core CLI handles login, targeting a region and resource group, and IAM, while plugins add commands for Kubernetes and OpenShift clusters, VPC infrastructure, Code Engine, Cloud Object Storage, and other services. Every service also has a REST API and SDKs in Python, Node.js, Java, and Go, and IBM maintains an official Terraform provider covering VPC, Kubernetes, IAM, and most catalog services. The IBM Cloud documentation is the reference for each plugin and API.

Regions and multizone regions

IBM Cloud deploys services into regions, and the key distinction is between a multizone region and a single zone region. A multizone region, or MZR, contains three availability zones in separate data centers close enough to act as one region but far enough apart to fail independently. Dallas, Washington DC, Toronto, São Paulo, London, Frankfurt, Madrid, Tokyo, Osaka, and Sydney are multizone regions, and VPC resources, Kubernetes clusters, regional buckets, and most managed databases are deployed at the region level with the option to spread across zones. Not every service is offered in every region, and moving a resource between regions generally means recreating it.

The catalog

The catalog is where every provisionable item lives: virtual servers and bare metal, Kubernetes and Code Engine, managed databases, AI services, developer tools, and third party software. Each entry lists plans, pricing, and available regions, and provisioning places the result in the resource group you pick. For a buyer of an entry level account, the catalog's free plan filter is the fastest way to see which services can be tried without a charge.

What IBM Cloud offers

These are the services that decide whether IBM Cloud fits a project, organized the way the console organizes them.

Virtual Servers for VPC and Classic

Virtual Servers for VPC are the current generation of IBM Cloud compute. They run inside a Virtual Private Cloud you define with subnets, security groups, and network ACLs, and are provisioned from profile families: balanced, compute, memory, and GPU. Instances are billed by the hour, boot from stock or custom images, and attach block storage volumes with a chosen IOPS tier; instance groups add autoscaling. Virtual Servers for Classic are the older SoftLayer heritage line, organized by data center with public and private VLANs. Classic remains for existing footprints, but VPC is where new features arrive.

Bare Metal Servers

Bare Metal Servers for Classic are single tenant physical servers with a wide choice of processors, memory, local disks, and GPU options, on hourly or monthly billing, and Bare Metal Servers for VPC bring the same model inside a VPC. Bare metal suits per-core licensing, VMware hosts, high throughput databases, and workloads that need consistent performance without a hypervisor. It is provisioned only on billed accounts.

IBM Cloud Kubernetes Service

IBM Cloud Kubernetes Service, usually abbreviated IKS, is IBM's managed Kubernetes. IBM operates the control plane and you pay for worker nodes, virtual servers in your VPC grouped into worker pools that can span the zones of a multizone region. The service updates the control plane, integrates with IBM Cloud Container Registry for images and vulnerability scanning, and ships an ingress controller backed by IBM Cloud load balancers. Persistent storage comes from block, file, or object storage through storage classes, and clusters authenticate through IAM, so the access groups that control the console also control kubectl.

Red Hat OpenShift on IBM Cloud

Because IBM owns Red Hat, OpenShift is a first class managed offering. Red Hat OpenShift on IBM Cloud provisions a full cluster with the OpenShift web console, integrated builds, operators, routes, and OpenShift's security defaults, on IBM managed control planes and worker nodes you size. Teams already on OpenShift on premises move workloads with the same tooling, and IBM Cloud Satellite extends cluster management to other clouds or your own data center. OpenShift workers carry an additional per-node entitlement charge, a cost line to include when comparing with plain Kubernetes.

Cloud Object Storage

IBM Cloud Object Storage is the S3 compatible object store. Buckets are created with a resiliency choice: cross region, spread across three regions in a geography; regional, kept across the zones of one multizone region; or single data center. Storage classes, Standard, Vault, Cold Vault, and Smart Tier, trade retrieval cost against storage cost, and Smart Tier moves objects between tiers automatically. Buckets support versioning, lifecycle rules, immutable retention, customer managed keys through Key Protect, and static website hosting. Because the API is S3 compatible, the AWS CLI, rclone, and most backup tools work with an endpoint change and HMAC credentials.

Databases for PostgreSQL, MongoDB, and Db2

IBM Cloud Databases is a family of managed open source databases sharing one operational model: high availability across zones, automated backups, point in time recovery, encryption at rest and in transit, scaling from the console or API, and IAM integration. It includes Databases for PostgreSQL, MongoDB, Redis, Elasticsearch, etcd, MySQL, and EnterpriseDB, each with private and public endpoints and service credentials that bind to applications and clusters. Cloudant, built on Apache CouchDB, covers the JSON document case. Db2 is IBM's own relational database, delivered as Db2 on Cloud for transactional workloads and Db2 Warehouse on Cloud for analytics, both fully managed and compatible with the on premises Db2 many enterprises still run. The catalog has historically carried a Lite plan of Db2 on Cloud with a small storage limit; the plan terms are IBM's and change over time.

Code Engine

IBM Cloud Code Engine is the serverless platform for containers. You give it a container image, a source repository, or a function, and it builds, deploys, scales to zero when idle, and bills only for the vCPU seconds and memory used while requests run. It runs HTTP applications, batch jobs, and functions in runtimes such as Node.js and Python, and it hides the underlying Kubernetes cluster entirely, which makes it the fastest route from a Dockerfile to a public URL on IBM Cloud. IBM Cloud Functions, the earlier Apache OpenWhisk based service that appears in older tutorials, has been deprecated in favor of Code Engine.

watsonx.ai and watsonx.data

The watsonx platform is IBM's current AI stack, offered on IBM Cloud as a set of services. watsonx.ai is the studio for working with foundation models: a Prompt Lab for testing prompts against IBM's Granite models and selected open models, tuning tools, notebooks and pipelines inherited from Watson Studio, and a deployment layer inherited from Watson Machine Learning. Inference is metered by tokens and compute by capacity unit hours. watsonx.data is the lakehouse component, a query engine over object storage and other sources using open table formats so Presto, Spark, and other engines share the same tables, and watsonx.governance tracks model lineage, bias, and drift. A trial account can typically reach watsonx.ai through a trial or Lite plan under conditions IBM sets, which is why buyers searching for a Buy IBM Cloud AI Account listing arrive at this page.

Watson services: Assistant, Discovery, and speech

Before watsonx, IBM's cloud AI was sold as individual Watson services, and the maintained ones remain in the catalog. Watson Assistant, now branded watsonx Assistant, is the conversational platform for chatbots and voice agents with dialog design, intent recognition, and web chat, phone, and messaging integrations. Watson Discovery ingests documents and exposes search, passage retrieval, and entity extraction, the usual foundation for a retrieval based question answering system. Speech to Text, Text to Speech, and Natural Language Understanding round out the set, and most Watson services offer a Lite plan with a monthly allowance, set by IBM and subject to change, which is what the Buy IBM Cloud Account for Watson search intent is usually after.

Security and Compliance Center, Key Protect, and related services

IBM Cloud Security and Compliance Center evaluates account resources against compliance profiles such as the CIS IBM Cloud Foundations benchmark, flags failing controls, and reports posture over time. Key Protect is the managed key management service, with keys held in cloud hardware security modules and a bring your own key model where imported root keys wrap the data encryption keys of object storage, block storage, databases, and Kubernetes secrets. Hyper Protect Crypto Services is the higher assurance option where you keep sole control of the master key. Secrets Manager stores API keys and certificates with rotation, and context based restrictions limit where a service can be reached from. These services are why IBM Cloud appears on shortlists in finance and healthcare.

VPC networking

A Virtual Private Cloud on IBM Cloud is a software defined network spanning the zones of a region. Inside it you create subnets per zone, attach security groups to instance interfaces for stateful rules, and attach network ACLs to subnets for stateless rules. A public gateway gives a subnet outbound internet access and floating IPs give instances inbound public addresses. Application and network load balancers, VPN gateways, Transit Gateway for connecting VPCs across regions, and Direct Link for private connectivity from your own facilities complete the picture, and IBM Cloud Internet Services adds global DNS, DDoS protection, a web application firewall, and caching in front of public endpoints.

Cost estimator and billing

Every catalog page has a cost estimator that turns a configuration into a projected monthly figure before you provision, and several planned resources can be collected into one estimate. Once resources exist, the Billing and usage section shows month to date usage, invoices, and a breakdown by service, resource group, and tag, and spending notifications email you when usage crosses a threshold. Trial and Lite accounts stop at the limits IBM sets rather than running a bill, which makes them a safe place to learn. For a provider neutral treatment, see our guide to billing alerts and budgets.

Who these IBM Cloud listings suit

The single variant on this page is an entry level account, and that shapes who it fits. People who Buy IBM Cloud Accounts here to learn, evaluate, or prototype are well served; anyone expecting to run a production fleet without first upgrading with IBM is not.

If you need bare metal, paid Kubernetes worker pools, or production database plans from day one, this listing is a starting point rather than the destination: those come after you add your own billing details with IBM, or through another provider on our Marketplace.

Variant guide: IBM Cloud Free Trial

This page lists one variant. The table below shows it exactly as it is priced on the product panel above.

Listed variant

IBM Cloud Free Trial

Listing price

$30

Account stage

Trial, as labeled

Usage billing

By IBM, under IBM's terms, once the account is upgraded

Console

cloud.ibm.com, with CLI and API access

What the IBM Cloud Free Trial label means

The label says two things and only two things: the account is on IBM Cloud, and it is at the trial stage. It does not say the account carries a credit balance, a number of days, a particular set of enabled services, or any age or verification status, and this page does not add those claims. What a trial account can do is defined entirely by IBM's current trial terms, published on its free tier page and revised without notice. Buyers who want to Buy IBM Cloud Free Trial Account listings should read that page on the day they order, because the allowances described there are the ones that apply.

How IBM Cloud trials and free tiers work in general

Providers use two mechanisms to let new customers try a platform: a time boxed trial that opens a defined set of services for a fixed period, sometimes with a promotional credit, and an always free tier that gives specific plans a monthly allowance that never expires while usage stays under the line. IBM Cloud has used both, through Lite accounts and Lite plans and more recently through a trial account model, and the free tier page describes the current mix. In practice a trial account is the place to explore the console, create resource groups and access groups, provision Lite plan services, and run the cost estimator, while bare metal and paid Kubernetes worker nodes wait until you upgrade with IBM. Everything built during the trial carries over.

What people build on IBM Cloud

Each use case below gives a concrete example so you can judge whether the trial stage covers your first steps.

Developer workflows

A backend developer who wants to Buy IBM Cloud Account for Developers listings usually has a specific integration in mind: a Node.js API deployed to Code Engine from a GitHub repository, reading a Lite plan Cloudant database, with secrets in Secrets Manager and an API key held in a service ID. Code Engine builds the image from source, gives the app a public URL with TLS, and scales to zero between requests, so the loop from push to running service can be exercised on a trial account within IBM's limits.

Business applications

A small business behind a Buy IBM Cloud Account for Business search typically cares about compliance tooling and managed databases more than raw compute. A representative project is a customer portal on OpenShift with Databases for PostgreSQL on a private endpoint, Key Protect wrapping the database keys, and Security and Compliance Center running the CIS profile nightly. On a trial account the business can model this in the cost estimator and provision the free plan components, then upgrade with IBM when it is ready for worker nodes and a paid database plan.

Startup infrastructure

Founders who search for Buy IBM Cloud Account for Startups listings are usually deciding whether IBM belongs in their stack alongside another hyperscaler. A realistic first build is a two zone VPC with a small virtual server group behind an application load balancer, Cloud Object Storage with Smart Tier for uploads, and Databases for Redis for sessions. The trial stage is where you validate that the Terraform provider covers what you need and that the IAM model fits your team. Our guide to choosing a cloud provider covers the questions to ask at this stage.

General cloud computing

The Buy IBM Cloud Account for Cloud Computing intent covers people who want a general purpose account to run virtual machines, store files, and host services. A typical example is a media agency that keeps its archive in a cross region Vault class bucket, runs a nightly Code Engine batch job to generate renditions, and serves them through IBM Cloud Internet Services with caching, paying for what it stores and processes rather than for idle servers.

Development environments

A team that wants to Buy IBM Cloud Account for Development purposes is often building an isolated environment per developer or feature branch. On IBM Cloud that maps to a resource group per environment, an access group per team, and Code Engine projects or Kubernetes namespaces per branch, with Container Registry holding the images. Because resource groups appear in the billing breakdown, the team lead can see what each environment costs.

Testing and QA

Buyers who search to Buy IBM Cloud Account for Testing usually need to run an application against real IBM services rather than mocks: a QA engineer validating that a product's Watson Assistant integration handles dialog updates, using the Assistant Lite plan, or confirming that an S3 client works against Cloud Object Storage with HMAC credentials and a regional endpoint. Both fit the trial stage under IBM's limits. Load testing and large data volumes belong on an upgraded account.

Research and academic projects

Researchers looking to Buy IBM Cloud Account for Research often want watsonx.ai notebooks, a place to keep datasets, and a way to run experiments without managing servers: a dataset in a regional bucket, a Jupyter notebook in watsonx.ai reading it through the SDK, and a Code Engine job running a parameter sweep overnight. Our article on using the cloud for research projects explains how to keep such work reproducible and within budget.

Personal and side projects

People who want to Buy IBM Cloud Account for Projects such as a portfolio, a hobby bot, or a home lab dashboard tend to use the free plans directly: a static site in a bucket with website hosting enabled, a Code Engine app for the API, and a Lite plan Cloudant database. These stay inside the allowances IBM publishes when traffic is small, which is exactly the stage a trial account is meant for.

Kubernetes and OpenShift

The Buy IBM Cloud Account for Kubernetes intent covers operators who want to learn IKS and OpenShift specifically. A useful exercise is deploying a three tier application with an ingress route, a block storage persistent volume, and IAM based kubectl access, then repeating it on OpenShift to compare the developer console and operator model. For a cross provider view, read our comparison of managed Kubernetes services including IKS.

Watson and AI development

The Buy IBM Cloud Account for AI Development intent is the most common reason people look for IBM Cloud listings today. A concrete project is a retrieval based assistant: documents ingested into Watson Discovery, a Granite model in watsonx.ai composing answers from retrieved passages, and Watson Assistant as the chat front end. Each service has a trial or Lite plan with limits IBM publishes, so the pattern can be prototyped end to end before paid capacity is needed. Token metered inference is where costs grow once the prototype becomes a product.

Choosing this listing versus alternatives

With one variant, the choice on this page is not between IBM Cloud options but between IBM Cloud and the other hyperscale listings on the Marketplace. The lists below sort out when to Buy IBM Cloud Accounts and when another provider is the better fit.

When the IBM Cloud Free Trial listing is the right pick

• You need watsonx, Watson Assistant, Watson Discovery, or Db2 specifically, since those are IBM services that other clouds do not run.
• You want managed OpenShift from the company that owns Red Hat, or you are comparing IKS with other managed Kubernetes services.
• Your client or employer is in a regulated industry and you need to evaluate Security and Compliance Center, Key Protect, and Hyper Protect services.
• You are at the learning or prototyping stage and IBM's trial allowances, as currently published, cover what you want to try.

When another listing fits better

• You need a billed account with a large service quota from day one. Our AWS account listings and Azure account listings carry variants labeled by stage and billing status that suit that requirement.
• You want an always free compute allowance for a small server that runs indefinitely. Our Oracle Cloud account listings are the usual comparison, and the Oracle Cloud vs IBM Cloud comparison walks through the two side by side.
• Your users are mainly in China or Southeast Asia and region coverage there matters more than AI services; see our Alibaba Cloud account listings.

Practical considerations after purchase

The first hour after you take over an account sets the pattern for everything that follows. Our cloud account handover checklist covers the generic steps; these are the IBM Cloud specifics.

Billing and the upgrade decision

Open the Billing and usage page first and decide early whether you will upgrade to Pay-As-You-Go. If you do, add payment details in your own or your company's name, review IBM's terms for billed accounts, and expect IBM to apply its checks. After upgrading, set spending notifications, tag resources by project, and run the cost estimator for every paid resource before creating it, because a forgotten cluster billed by the hour is the most common source of an unexpected invoice.

IAM users and multifactor authentication

Do not run the account from the owner identity day to day. Invite your working identity as a user, place it in an access group with the Administrator platform role on the resources you need, and keep the owner login for account level changes. Enforce multifactor authentication account wide from the IAM settings. Create service IDs for pipelines and applications, give each an API key, and keep those keys in Secrets Manager or your CI secret store rather than in code. Review the access policies that exist when you take over and remove anything you do not recognize. Our IAM basics guide explains how these concepts compare across providers.

Quotas and service limits

Trial accounts are limited by IBM's trial terms, and billed accounts still carry default quotas per service and region: numbers of VPCs, subnets, floating IPs, instances, clusters, and so on. Quotas are documented per service and many can be raised through a support case with IBM under its support plans. Plan against the published defaults and request increases before you need them. The general concepts are covered in our article on cloud service quotas and limits.

IBM Cloud terms and acceptable use

Using the account means accepting IBM's Cloud Services terms and acceptable use policy: no spam, no abuse of other systems, no cryptocurrency mining on trial or free resources, no unlawful content, and honest account details. IBM monitors for abuse and suspends accounts that breach its terms, and this marketplace cannot change a suspension IBM applies. Buyers who search to Buy IBM Cloud Account Online should treat these terms as part of the purchase: the listing is a starting point, and staying within IBM's rules is what keeps it usable.

Getting started checklist

Work through these steps in order after you Buy IBM Cloud Accounts here.

1. Sign in to the console, confirm the account type and any trial status on the account settings page, and read IBM's current free tier page for the allowances that apply today.
2. Update the contact and notification email to your own, then enable multifactor authentication.
3. Invite your working identity as a user and create an access group with the roles you need.
4. Create the resource groups you plan to use, with an access group and naming convention for each.
5. Install the ibmcloud CLI, log in with an API key, and add the plugins for the services you will use.
6. Provision one Lite or free plan service, such as Cloud Object Storage, to confirm provisioning works and see how service credentials are issued.
7. Model the paid resources you expect to need in the cost estimator so the upgrade decision is made with numbers.
8. Decide whether and when to upgrade to Pay-As-You-Go with your own billing details, and set spending notifications immediately afterwards if you do.
9. Read IBM's acceptable use policy in full and keep your usage inside it.

Common IBM Cloud search terms and what they map to here

Many buyers reach this page from searches that describe an account feature rather than a listing. This section maps those phrases honestly to the one variant on offer.

Buy Old IBM Cloud Account. Searchers using this phrase usually want an account created some time ago. No listing on this page is labeled by age. The variant is described only as IBM Cloud Free Trial, and that is all you should read into it. If account age matters to your plan, ask through the contact page before you order rather than assuming.

Buy Verified IBM Cloud Account. This phrase generally means an account that has completed a provider's identity or payment checks. The listing here is not labeled as verified, and we make no claim about verification beyond the label. IBM applies its own checks when an account is upgraded to a billed type, and those checks remain IBM's to apply.

Buy IBM Cloud Account with Credits. Providers sometimes attach a promotional credit to a new account, and IBM has done so at various times under terms it sets and changes. No variant on this page is listed with a credit balance, and the $30 price is the price of the listing, not a balance inside IBM Cloud. Whatever allowance IBM currently attaches to a trial is described on IBM's free tier page. Our Cloud Library article on how cloud credits work explains the general mechanics.

IBM Cloud Account with Credits for Sale. The same answer applies to this phrasing: this page offers an IBM Cloud Free Trial listing, and any trial allowance is IBM's to define.

Buy IBM Cloud AI Account and Buy IBM Cloud Account for Watson. These describe the same thing: an IBM Cloud account used to reach watsonx.ai, Watson Assistant, Watson Discovery, and the speech and language services. Every account can see those services in the catalog; what a trial account can provision is governed by IBM's plan and trial terms. There is no separate AI account type on IBM Cloud and none is listed here.

IBM Cloud Account for Sale. This phrase describes exactly what the page offers: one listed IBM Cloud account at the trial stage, priced at $30, with the console, CLI, and API available to the holder and all usage subject to IBM's terms.

Related listings and next steps

If IBM Cloud is one of several hyperscale providers you are weighing, the listings below are the ones most often bought alongside or instead of an IBM Cloud account.

• Buy Oracle Cloud Accounts: the closest comparison for buyers interested in free tier compute and a managed database, with an always free allowance that Oracle defines.
• Buy Alibaba Cloud Accounts: ECS based listings for teams whose users are in China and Southeast Asia.
• Buy Azure Accounts: subscriptions and resource groups in Microsoft's cloud, often compared with IBM for enterprise and compliance work.
• Buy AWS Accounts: the broadest service catalog, with variants labeled by account stage and billing status.

To compare before deciding, read Oracle Cloud vs IBM Cloud or browse the Compare hub. For background, the IBM Cloud overview in our Cloud Library explains accounts, resource groups, Watson, and Kubernetes from the ground up, and the rest of the Cloud Library covers IAM, billing, and security in provider neutral terms.

Ready to order? Add the IBM Cloud Free Trial variant to the cart above, or browse the full Marketplace. Ordering and delivery questions are answered on the FAQ page, and anything specific to your situation can go to the contact page. Whether you Buy IBM Cloud Accounts to evaluate watsonx, learn OpenShift, or prototype a compliance ready architecture, the label describes exactly what you get, IBM's terms govern what you do with it, and the rest is yours to build.