Kamatera is built around a different idea from most fixed-plan providers: you assemble a server from components rather than picking a tier. CPU type, core count, memory, storage and location are chosen separately, and you can bill the result by the hour or by the month. This article explains how that model works in practice and what the two options on the Buy Kamatera Account page, the Kamatera 5 Limit with $100 Credit Account ($30) and the Kamatera Open 25 Port Account ($50), actually describe.
Component pricing instead of fixed plans
On a plan-based provider you choose between a handful of bundles and accept whatever ratio of CPU to memory they carry. Kamatera prices each component independently. A memory-hungry cache can be given a lot of RAM and few cores; a build runner can go the other way. Additional disks and traffic are billed at published rates on top of the base configuration.
The practical benefit is that you stop paying for the part of a bundle you never use. The practical cost is that you must know your workload well enough to size it, which is where matching CPU, memory and storage to a workload becomes a real skill rather than a checkbox.
The four CPU types
Kamatera groups its processors into types, each suited to a different tolerance for shared resources:
- Type A (Availability): budget-friendly shared resources for development, staging and light services.
- Type B (General Purpose): dedicated threads with reserved resources for everyday production.
- Type D (Dedicated): dedicated physical cores for databases and anything that needs consistent performance.
- Type T (Burstable): a baseline allocation you can temporarily exceed, useful for spiky traffic.
Choosing the type is the single biggest lever on both cost and behavior. Start with Type A for anything that tolerates variable performance and reserve Type D for the services whose latency you actually measure.
Hourly or monthly: picking the billing mode
Every configuration can run on hourly or monthly billing. Hourly suits anything short-lived: a load test, a temporary staging copy, a migration host, a weekend experiment. Monthly suits servers that will run continuously, where a predictable line item is worth more than the flexibility to delete on a whim. The vocabulary behind these choices is covered in cloud billing concepts explained.
A sensible pattern is to start every new server hourly, watch it for a couple of weeks, and switch the survivors to monthly once you are confident they are permanent.
What the two listed options mean
| Listed option | Price | What the name describes |
|---|---|---|
| Kamatera 5 Limit with $100 Credit Account | $30 | A server limit of five plus a $100 credit balance |
| Kamatera Open 25 Port Account | $50 | An account where outbound port 25 is open for mail delivery |
The first option combines two attributes. The “5 Limit” is the number of servers the account can run at once, and the “$100 Credit” is a promotional balance that is drawn down before a payment method is charged. Confirm the remaining balance, its validity window and the services it applies to before relying on it; the general mechanics are in how cloud credits work across providers.
The second option is defined by networking rather than compute. Many providers block outbound port 25 on new accounts to limit abuse, so an account with the port open is relevant only if you run your own mail transfer agent for transactional or notification mail. Operate it responsibly: set up SPF, DKIM and DMARC, keep lists clean, and stay inside Kamatera’s acceptable-use terms.
Working inside a five-server limit
Five servers is enough for a typical small production stack: a web tier, a database, a worker, a monitoring host and one spare for staging. Because Kamatera lets you resize components, you often scale vertically before you need a sixth machine. If the limit does become a constraint, raising it goes through the provider’s own support process, which is far smoother on an account with a clean billing history and accurate contact details.
How Kamatera’s limit-based option compares with similar options elsewhere is laid out in server-limit accounts compared, and a direct comparison with a European price-performance provider is in Kamatera vs Hetzner accounts.
Keeping Kamatera costs predictable
Component pricing rewards attention. Delete disks that outlived their server, watch traffic and storage in the console so overage never surprises you, and use any remaining promotional credit before it expires. If you are new to the platform, the questions other buyers ask are collected in the Kamatera section of the Cloud FAQ.
