Buy Hetzner Accounts
Hetzner Developer Cloud & VPS
Hetzner runs one of the most cost efficient developer clouds in Europe, with shared and dedicated vCPU servers, Arm instances, Volumes, Load Balancers, private Networks and an API that works well with Terraform. Locations in Germany, Finland, the United States and Singapore let you keep data where your users and your regulations expect it.
When you Buy Hetzner Accounts on CloudAccountHub you choose between listings labeled by server limit, 5 or 10, and a variant listed with outbound port 25 available for compliant transactional email. Each label describes exactly what the account is; usage inside it is billed by Hetzner at its published rates. The guide below explains every variant and what to do after purchase.

What a Hetzner account covers
Hetzner is a German hosting company that runs two product lines under one customer login: Hetzner Cloud, the on-demand virtual server platform managed through the Cloud Console, and the dedicated root server business managed through a separate panel called Robot. When you Buy Hetzner Accounts on CloudAccountHub, the listing you receive is a Hetzner customer account with Cloud Console access, described exactly by the variant label you pick. This section explains what sits behind that login so you know what you are working with before you create your first server.
Hetzner Cloud Console and projects
The Cloud Console is the web interface for Hetzner Cloud. Everything inside it is organised into projects. A project is a container that holds its own servers, Volumes, Networks, Firewalls, Load Balancers, SSH keys, API tokens and its own resource limits. One account can hold several projects, which makes a project the natural boundary between clients, environments or teams. You can invite other Hetzner users into a project as members with different roles, so a freelancer can give a client read access to their own infrastructure without sharing the account password.
API tokens are created per project and can be issued with read or read and write permission. Because tokens are scoped to a project, a compromised token for a staging project cannot touch the servers in a production project. The Console also shows per-project usage and the current month's estimated cost, which is where most people watch spending.
Cloud server types
Hetzner Cloud servers are grouped into families by CPU model and by whether the vCPUs are shared or dedicated:
- CX (shared vCPU, Intel): the general purpose line. Shared vCPU means the physical core is shared with other tenants and is suited to web servers, small databases, CI runners and most everyday services.
- CPX (shared vCPU, AMD): the same shared model on AMD EPYC processors, often chosen when a workload benefits from higher single-thread performance.
- CCX (dedicated vCPU): each vCPU is reserved for your server alone. This is the line for databases under sustained load, build farms, game servers and anything that must not be affected by noisy neighbours.
- CAX (Arm64, Ampere): Arm-based servers, popular for cost sensitive workloads whose container images and runtimes ship arm64 builds.
Each server is billed by the hour up to a monthly cap, includes a traffic allowance that Hetzner publishes per server type, and comes with a primary IPv6 address. A primary IPv4 address is optional and carries its own charge, so IPv6-only servers are a real option when the service sits behind a Load Balancer or a proxy that has IPv4.
Locations
Hetzner Cloud currently offers locations in Germany (Falkenstein and Nuremberg), Finland (Helsinki), the United States (Ashburn on the east coast and Hillsboro on the west coast) and Singapore. Not every server type is offered in every location; the Console shows what is available when you create a server. Servers, Volumes and private Networks are tied to a location or a network zone, so plan where your data lives before you build. The European locations are the usual pick for teams that need data to stay inside the European Union, while the US and Singapore locations shorten the round trip for users on those continents.
Storage, networking and protection
Beyond the server itself, the Cloud Console exposes a set of building blocks that a practitioner will recognise:
- Volumes: block storage that attaches to a server in the same location and can be resized upwards. Use them for database files or any data that should outlive the server.
- Object Storage: S3 compatible bucket storage for backups, static assets, log archives and machine learning datasets, addressed with the same tools you would use against any S3 style endpoint.
- Load Balancers: managed layer 4 and layer 7 balancing with health checks, sticky sessions and certificate handling, targeting servers by label so new servers join automatically.
- Floating IPs: IPv4 or IPv6 addresses that can be moved between servers, which is how you fail over a public address without changing DNS.
- Networks: private networks with subnets and routes that keep database traffic off the public interface. Cloud Networks can also connect to Hetzner dedicated servers through a vSwitch.
- Firewalls: stateful inbound and outbound rules applied to servers directly or through labels, enforced before traffic reaches the server's own operating system firewall.
- Snapshots and Backups: Snapshots are manual full disk images you keep as long as you want and can use to create new servers. Backups are automated, kept on a rolling schedule and enabled per server at a surcharge that Hetzner lists on its pricing page.
hcloud CLI, API and infrastructure as code
Everything in the Console is also available through the Hetzner Cloud API. The official hcloud command line tool wraps that API, so creating a server, attaching a Volume or rotating a Firewall rule is a one line command. Hetzner maintains a Terraform provider, and community modules exist for Ansible, Pulumi and the Kubernetes cloud controller manager. Cloud-init user data is accepted at creation time, which is how most teams bootstrap packages and users before they ever log in.
Robot, dedicated root servers and Storage Boxes
The same customer account can order dedicated root servers from the Hetzner dedicated server catalogue. These are physical machines managed through the Robot panel rather than the Cloud Console, with their own ordering flow, their own review by Hetzner and their own billing. Hetzner also offers GPU dedicated servers in that line, which is the relevant product for training work. Storage Boxes are large, low cost storage volumes reachable over SFTP, SMB, rsync and BorgBackup, and they are a common off-site backup target for cloud servers. Dedicated products are not part of the variant labels on this page, so treat them as something you can order later from within the account, subject to Hetzner's own checks.
Per-project limits on new accounts
Every new Hetzner Cloud account starts with limits per project on how many servers, Volumes, Floating IPs, Load Balancers and other resources it can hold. Hetzner documents that these starting limits exist to protect the platform and that customers can request an increase from the Console, with Hetzner reviewing and raising the limit on request. This is the concept the "5 Server" and "10 Server" labels below refer to. To understand how quotas work across providers in general, read Cloud Service Quotas and Limits Explained.
Who these Hetzner listings suit
People who search for a Hetzner Account for Sale, or who simply type Buy Hetzner Accounts into a search engine, usually fall into a small number of groups, and the right variant depends on which group you belong to. Read the descriptions below and match yourself to one before you compare prices.
Solo developers and freelancers. You want a place to host client sites, a staging copy of an app, a CI runner and a personal project or two. A handful of CX servers with a Volume for the database covers this, and the smaller server limit is rarely a constraint.
Agencies and small businesses. You run several client environments and want each in its own project, with per-client API tokens and per-client cost visibility. Server count grows with every client, so the higher server limit variant is the sensible starting point.
Startups. You are building a product that must scale from one server to a small cluster without rewriting the deployment. Hetzner's Load Balancers, private Networks and Terraform provider make that path straightforward and keep the monthly bill predictable while you grow.
Teams that send email from their own servers. If your application sends transactional messages directly rather than through a third party API, outbound SMTP on port 25 matters. Hetzner restricts that port on new cloud accounts by default, which is why the Open 25 Port variant exists as a separate listing.
Researchers and students. You need short-lived compute for experiments, a dedicated vCPU server for a long simulation, or a GPU dedicated server for model training, billed by the hour with no long commitment.
If you are looking to Buy Hetzner Account Online for a reason not listed here, the FAQ near the end of this page and the contact page are the fastest way to check whether a variant fits.
Hetzner variant guide: every listing explained
Buyers who Buy Hetzner Accounts here choose from three variants in two groups. The table shows the exact names and prices as they appear in the cart. Below the table, each variant is explained by restating what its label says and then describing the underlying Hetzner concept. No variant includes anything beyond what its label states.
| Variant | Group | Price (USD) | What the label describes |
|---|---|---|---|
| Hetzner 5 Server Account | Server limits | $50 | A Hetzner Cloud account listed with a server limit of 5 |
| Hetzner 10 Server Account | Server limits | $90 | A Hetzner Cloud account listed with a server limit of 10 |
| Hetzner Open 25 Port Account | Open 25 Port | $250 | A Hetzner Cloud account listed with outbound port 25 available |
What the server limit describes
The number in the "Server limits" group refers to the Hetzner Cloud server limit, the maximum count of cloud servers a project can hold at one time. It is a ceiling, not an allocation: you are not paying for five or ten servers, you are buying an account whose limit is listed at that level, and each server you actually create is billed by Hetzner at its published hourly rate. When you delete a server the slot is freed again. Hetzner sets a starting limit on new accounts and raises it on request through the Console, as described in its documentation. Related limits on Volumes, Floating IPs and Load Balancers exist separately and are not part of these labels.
Hetzner 5 Server Account ($50)
This variant is listed as a Hetzner Cloud account with a server limit of 5. Five servers is enough for a typical small production layout: a web server, an application server, a database server, a worker and a staging copy, or a three node Kubernetes cluster with a bastion and a build runner. It suits individual developers, small client projects and anyone whose first question is "can I run a few servers without waiting for a limit review". Because Hetzner bills per server rather than per account, the low listing price does not imply low capacity per server: a single CCX dedicated vCPU server inside this account can still be a large machine.
Hetzner 10 Server Account ($90)
This variant is listed as a Hetzner Cloud account with a server limit of 10. It is the higher limit option among the listings on this page and the closest match for buyers whose search intent is to Buy Hetzner Account with Higher Limits. Ten servers covers an agency running separate environments for several clients, a startup with a production cluster plus preview environments for each pull request, or a research group that spins up short lived compute alongside a permanent data server. If your plan involves autoscaling, blue-green deployments or per branch preview servers, the extra headroom removes a bottleneck you would otherwise hit within weeks.
Hetzner Open 25 Port Account ($250)
This variant is listed as a Hetzner Cloud account with outbound port 25 available, as the label states. The context matters. Port 25 is the port mail servers use to talk to each other. Because compromised or throwaway servers are a common source of spam, Hetzner restricts outbound port 25 on new cloud accounts by default; its own Hetzner Cloud FAQ explains the policy and how Hetzner handles requests to lift it. The Open 25 Port variant is listed with that port available, which is the difference from the two server limit variants.
What this variant is for: legitimate transactional and notification email from your own application. Order confirmations, password resets, monitoring alerts, invoices and system notifications sent by a mail server you control, to recipients who expect them. What it is not for: bulk unsolicited mail. Any sending must follow Hetzner's terms of service and acceptable use policy and the anti-spam law that applies to you and your recipients, including consent, working unsubscribe handling and honest headers. Set up SPF, DKIM and DMARC and reverse DNS for the sending address before the first message leaves the server; without them, most receiving providers will reject or junk your mail regardless of which port is open. Our article on port 25 and cloud email sending goes through why providers restrict the port and how to set up a compliant sender.

Key Hetzner features at a glance
The features below are the ones buyers ask about most. Each is described briefly and accurately; the official Hetzner documentation has the full detail and the current specifications.
Hourly billing with a monthly cap
Every cloud server, Volume and Load Balancer is billed by the hour and stops accruing once it reaches the published monthly price. Delete a test server after an afternoon and you pay for an afternoon.
Shared, dedicated and Arm compute
Choose CX or CPX for shared vCPU value, CCX for dedicated vCPU consistency, or CAX for Arm64 workloads. All are created from the same Console and API and can live in the same private Network.
Projects with scoped tokens
Separate clients or environments into projects, each with its own API tokens, members, SSH keys and limits. A token for one project cannot act on another.
Managed Load Balancers
Distribute traffic across servers selected by label, with health checks and certificate management, so adding a server to the pool is a matter of applying a label.
Cloud Firewalls and private Networks
Filter traffic before it reaches the server and keep database and cache traffic on private addresses. Both are free of charge in Hetzner Cloud and both are managed through the same API.
Snapshots, Backups and Object Storage
Take manual Snapshots before risky changes, enable automated Backups on servers that matter, and ship long term archives to S3 compatible Object Storage.
Hetzner's Hetzner Cloud product page lists the current server types, locations and prices. Prices and specifications are set by Hetzner and change over time, so always confirm the current figures there before you size a deployment.
What people build on Hetzner: use cases by audience
The listings on this page are used for very different kinds of work. The examples below are concrete so you can see whether your own plan resembles one of them.
Developers
The typical reason to Buy Hetzner Account for Developers is that a developer wants real Linux servers with root access, predictable pricing and an API, without the surface area of a hyperscaler. A common layout is one CX server running Docker Compose with a reverse proxy, a Volume for persistent data, a Cloud Firewall that allows only ports 22, 80 and 443, and a Snapshot taken before each major upgrade. Developers also use Hetzner for self-hosted tools such as a Git server, a container registry or an uptime monitor, each on a small server.
Business
A company that decides to Buy Hetzner Account for Business is usually consolidating several hosted services under one bill. Examples include an internal wiki and ticketing system on a private Network reachable only through a VPN server, a customer facing web application behind a Load Balancer with two application servers and a CCX database server, and a nightly job server that pulls reports from a CRM and pushes them to Object Storage. European data residency is often the deciding factor: with servers in Falkenstein, Nuremberg or Helsinki, customer data stays inside the EU without additional configuration.
Startups
Founders who Buy Hetzner Account for Startups want to reach a production grade setup on a small budget and grow it without a migration. A realistic path is: launch on a single CPX server with a Volume; add a Load Balancer and a second application server when traffic justifies it; move the database to a CCX dedicated vCPU server inside a private Network; add a Placement Group so the two database nodes never share a host; and manage all of it with Terraform so preview environments can be created per feature branch and destroyed when merged. The 10 Server variant is the one that leaves room for that growth.
Cloud computing
Buyers who search to Buy Hetzner Account for Cloud Computing tend to mean general infrastructure rather than a single application: Kubernetes clusters, batch processing, distributed storage or a private platform for a team. Hetzner is popular for self-managed Kubernetes because the cloud controller manager integrates Load Balancers and private Networks, and because CCX servers give predictable CPU for control plane nodes. A three control plane, three worker layout fits within the 10 Server limit and leaves slots for a bastion and a build runner.
Development
Teams that Buy Hetzner Account for Development want an environment that mirrors production but can be rebuilt at will. Create a Snapshot of a configured application server, then create a fresh server from that Snapshot for each developer or each feature. Because billing is hourly, a development server that exists only during working hours costs a fraction of the monthly price. Cloud-init user data handles package installation and user creation at boot, so a rebuilt server is ready to use within minutes of creation.
Testing
To Buy Hetzner Account for Testing usually means load testing, integration testing or compatibility testing. Load tests benefit from creating several CPX servers in a location far from the target, running the test, then deleting them. Integration tests run on a CI runner that creates a temporary server via the hcloud CLI, provisions it, runs the suite and destroys it. Compatibility tests use the CAX Arm servers to confirm that a container image behaves the same on arm64 as on x86.
Research
Research groups that Buy Hetzner Account for Research value hourly billing and dedicated vCPU servers. A CCX server can run a week long simulation with consistent CPU throughput, then be deleted, while a small CX server keeps a Jupyter environment available for the whole term. Datasets live in Object Storage where any collaborator with a key can read them, and Snapshots record the exact software environment used for a published result so that it can be reproduced later.
Projects
People who Buy Hetzner Account for Projects are often running side projects, community services or open source infrastructure: a Mastodon or Matrix instance, a game server for a group of friends, a mirror for a Linux distribution, a Minecraft server with automated Backups, or a personal media server with a large Volume. The 5 Server variant covers most of these comfortably, and the account can hold several projects so a paid client project never shares a project or an API token with a hobby server.
AI development
The phrase Buy Hetzner Account for AI Development covers two distinct needs. For inference and application code, standard cloud servers are enough: a CCX server can host a vector database and an API that calls a hosted model, with embeddings stored on a Volume and documents in Object Storage. For training, Hetzner offers GPU dedicated servers through its dedicated root server line, ordered separately within the same customer account and subject to Hetzner's own ordering checks. The cloud account on this page is the starting point; the GPU server is a later order. Anyone looking to Buy Hetzner AI Account should read the account as a Hetzner Cloud login as labeled, not as a GPU allocation, and check current GPU availability with Hetzner before planning a training schedule.
Choosing the right variant
Three questions settle the choice for almost everyone who wants to Buy Hetzner Accounts.
- How many servers will exist at the same time within a month or two? Count production, staging, workers, monitoring and CI runners. If the honest answer is five or fewer, the Hetzner 5 Server Account is the economical pick. If it is between six and ten, or you expect per branch preview environments, choose the Hetzner 10 Server Account.
- Will your own servers send email over SMTP on port 25? If the application uses a third party email API over HTTPS or submits mail through an authenticated relay, you do not need the Open 25 Port variant. If you run your own mail transfer agent that delivers directly to recipient servers, the Hetzner Open 25 Port Account is the listing that matches.
- Do you need dedicated servers, GPUs or Storage Boxes on day one? None of the variants includes those. They are ordered from within the account after purchase and Hetzner reviews those orders itself.
- Best for a first production deployment
- Hetzner 5 Server Account, $50
- Best for agencies, clusters and preview environments
- Hetzner 10 Server Account, $90
- Best for self-hosted transactional email
- Hetzner Open 25 Port Account, $250
- Billing model for resources you create
- Hourly, capped at Hetzner's monthly price, billed by Hetzner
- Locations
- Germany, Finland, United States, Singapore
If you are comparing Hetzner with another provider before you decide, the Hetzner vs DigitalOcean comparison looks at pricing, locations and developer tooling side by side, and the Hetzner vs OVHcloud page compares the two European providers on cloud, VPS and dedicated servers.
Practical considerations after purchase
An account is only as useful as the habits you bring to it. The steps below are what an experienced operator does in the first hour with any new cloud account.
Billing and payment
Hetzner bills the account holder for every resource created, at Hetzner's published rates, on Hetzner's invoice schedule. The listing price on this page is a one time purchase of the account as described; it does not prepay Hetzner usage. Review the payment method on file, set up whatever billing details your company requires for invoices, and watch the Console's cost estimate during the first month. Many teams also export usage through the API into their own monitoring so that spending is visible outside the Console.
Two-factor authentication
Enable two-factor authentication on the Hetzner login immediately. The Console supports time based one time passwords and security keys. Store the recovery codes somewhere other than the account itself. If several people will use the account, invite them as project members with their own logins and their own 2FA rather than sharing one credential.
SSH keys
Upload your public SSH key to each project before creating servers so that new servers are created with key authentication from the start. Disable password login for root in the SSH daemon configuration on every server, or do it through cloud-init so no server is ever created without it. Rotate keys when a team member leaves.
Firewalls
Create a Cloud Firewall in each project with a default deny inbound policy and explicit allows for SSH from your own addresses and for the ports your application serves. Apply it by label so new servers inherit it. Keep the server's own firewall as a second layer; the Cloud Firewall protects the network edge and the host firewall protects against mistakes inside the server. Read Securing a VPS for the host side of that setup.
Backups and Snapshots
Enable automated Backups on any server whose loss would cost you more than the surcharge, and take a manual Snapshot before every operating system upgrade or major deployment. Backups protect against your own mistakes as well as hardware faults, and because Snapshots can be used to create new servers they double as golden images. For long retention, copy database dumps to Object Storage or a Storage Box on a schedule. The cloud backup strategy article gives a simple retention plan that works on Hetzner.
Terms and acceptable use
Read Hetzner's terms of service and acceptable use policy before you deploy. They cover the usual prohibitions on abuse, copyright infringement and spam, and they describe what Hetzner does when it receives an abuse report. Keep your account details accurate and respond promptly to any message from Hetzner support. If you use the Open 25 Port variant, treat compliance with anti-spam law as part of your deployment, not an afterthought: consent records, unsubscribe handling, rate limits on your mail transfer agent and monitoring of bounce rates protect both your reputation and your account standing.
Getting started checklist
Work through this list in order on the day you receive the account. It takes well under an hour and prevents most of the problems that new Hetzner users report.
- Log in to the Cloud Console, review the account and billing details, and enable two-factor authentication.
- Create a project for your first environment. Name it for its purpose, for example production or client-name-staging.
- Upload your SSH public key to the project.
- Create a Cloud Firewall with default deny inbound, allow SSH from your addresses, and allow the ports your service needs.
- Create a private Network if more than one server will talk to another server.
- Create your first server: pick the location, the server type (CX, CPX, CCX or CAX), an operating system image, your SSH key, the Firewall and the Network. Paste cloud-init user data if you have it.
- Attach a Volume if the server holds data that should outlive it, and mount it with a stable path.
- Enable Backups on the server if it will hold anything you cannot recreate.
- Create an API token with read and write permission if you plan to use the hcloud CLI or Terraform, and store it in a secrets manager rather than a shell history.
- Check the project's current limits in the Console so you know how many servers, Volumes and Floating IPs you can create before requesting an increase from Hetzner.
- If you bought the Open 25 Port variant, configure reverse DNS, SPF, DKIM and DMARC before the first message is sent, and send a test to a mailbox you control.
- Take a Snapshot once the server is configured so you have a known good image to return to.
Common Hetzner search terms and what they map to here
Many buyers arrive on this page from searches that describe a feature rather than a listing. This section maps those phrases honestly to what is actually on offer, so nobody buys a variant expecting something the label does not say.
Buy Old Hetzner Account. Searchers using this phrase usually want an account that is past the point where a provider applies its tightest new customer restrictions. No variant on this page is labeled by age. Each listing is described only by its server limit or by port availability, and that is all you should read into it. If account age matters to your plan, ask before you order.
Buy Verified Hetzner Account. This phrase generally means an account that has completed the provider's identity or payment checks. The variants here are not labeled as verified and we make no claim beyond the label. Hetzner runs its own checks on customers and on orders for dedicated products, and those checks remain Hetzner's to apply. The useful question is whether the account can create servers up to the listed limit, and that is what the label describes.
Buy Hetzner Account with Credits. Hetzner does not run a standing promotional credit programme in the way some providers do, and no variant on this page is listed with a credit balance. Any promotional credit a provider offers is set by that provider and subject to change. Resources you create are billed by Hetzner at its published rates. If you are specifically after a credit based account, our UpCloud account listings are labeled with a credit amount.
Buy Hetzner Free Trial Account. There is no free trial variant on this page and we do not claim one exists. Trial terms, where a provider offers them, are set by the provider and change without notice. The closest listed option for a low cost start is the Hetzner 5 Server Account at $50, with usage inside it billed hourly by Hetzner so a small experiment costs very little.
Buy Hetzner Account with Higher Limits. Among the listings on this page, the Hetzner 10 Server Account at $90 is the higher limit option. Beyond that, Hetzner raises limits on request through the Console, as its documentation describes, and that request is between you and Hetzner.
Buy Hetzner Cloud Account and Hetzner Cloud Account for Sale. Both phrases describe exactly what these listings are: a Hetzner customer account with Cloud Console access, labeled by server limit or port availability. Dedicated root servers, GPU servers and Storage Boxes are separate Hetzner products that can be ordered from within the account, subject to Hetzner's review.
Frequently asked questions before you Buy Hetzner Accounts
What exactly do I receive when I buy a Hetzner account here?
You receive a Hetzner customer account with access to the Hetzner Cloud Console, described by the variant label you chose: a listed server limit of 5 or 10, or outbound port 25 available. Servers, Volumes and other resources are created by you inside the account and billed by Hetzner at its published rates. The listing does not include prepaid usage, credits or dedicated hardware.
What does the server limit mean in practice?
It is the maximum number of cloud servers a project can hold at the same time. Deleting a server frees the slot. The limit does not restrict the size of each server, so a five server account can run large CCX dedicated vCPU machines. Hetzner documents that it raises limits on request from the Console, which is a matter between you and Hetzner after purchase.
Why does the Open 25 Port variant cost more?
Hetzner restricts outbound port 25 on new cloud accounts by default, as its FAQ explains, because open SMTP from fresh servers is a common spam vector. The Open 25 Port variant is listed with that port available, which is a different account state from the server limit variants, and the price reflects that. It is intended for legitimate transactional and notification email that complies with Hetzner's terms and anti-spam law.
Can I send marketing newsletters from the Open 25 Port account?
Only if every recipient has consented, your messages carry a working unsubscribe mechanism and honest headers, and your sending follows Hetzner's acceptable use policy and the anti-spam law that applies to you. For genuine bulk marketing, a purpose built email platform with reputation tooling is a better choice than a self-hosted mail server on a cloud VPS. This variant is designed for application email such as receipts, alerts and password resets.
Which locations can I use?
Hetzner Cloud offers Falkenstein and Nuremberg in Germany, Helsinki in Finland, Ashburn and Hillsboro in the United States, and Singapore. Availability of specific server types varies by location, and the Console shows what is offered when you create a server. Location choice is yours after purchase; the account is not tied to one location.
Does the account include dedicated root servers or GPU servers?
No. The variants describe a Hetzner Cloud account only. Dedicated root servers, including Hetzner's GPU dedicated servers, and Storage Boxes are separate products that a customer can order from within the same account through the Robot panel. Hetzner reviews those orders itself, and availability and pricing are set by Hetzner.
Is there a free trial or credit variant?
No. Nothing on this page is listed with a trial or a credit balance, and we do not claim that Hetzner offers one. Provider promotions, where they exist, are set by the provider and change over time. The lowest cost entry point here is the Hetzner 5 Server Account at $50, and because Hetzner bills hourly, a small experiment inside it costs very little.
How do I automate Hetzner from code?
Create an API token in the project with read and write permission, then use the hcloud command line tool, the Hetzner Cloud Terraform provider, Ansible modules or the REST API directly. Cloud-init user data lets you configure a server at first boot. Tokens are per project, so keep separate tokens for production and staging.
What should I do first for security?
Enable two-factor authentication on the login, upload an SSH key and create servers with it, disable password SSH login, create a Cloud Firewall with a default deny inbound rule, and invite team members as project members rather than sharing the credential. Enable Backups on any server that holds data you cannot recreate.
Can I run Kubernetes on Hetzner?
Yes, as a self-managed cluster. Hetzner does not sell a managed Kubernetes product, but the community cloud controller manager and CSI driver integrate Load Balancers, private Networks and Volumes with a cluster you install yourself. A small highly available cluster with three control plane nodes and three workers fits inside the 10 Server variant with room for a bastion.
What happens if I exceed the listed server limit?
The Console and API will refuse to create another server in that project until you delete one or Hetzner raises the limit. Hetzner's documentation describes the limit increase request in the Console, and Hetzner decides on that request. Plan your server count against the listed limit, and choose the 10 Server variant if you expect to grow.
Where can I get help after purchase?
For questions about the listing itself, use our contact page. For questions about Hetzner services, server types, limits and billing, Hetzner's documentation and its own support are the authoritative sources. Our marketplace FAQ covers ordering, delivery and general questions that apply to every listing.