HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hetznercloud
cli
Go2018–2024
hetznercloud / cli

cli

A command-line interface for Hetzner Cloud

3Distinct people
4Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A command-line interface for Hetzner Cloud

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2018-01-23 10:51:27 UTC to 2024-11-17 15:43:26 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211

What Hacker News says

4 sources
hopefully i am doing everything right and that is the right location and the right way to post this. it is my first post here on HN. being a long time reader of HN i thought maybe it is the right location to ask other developers to vote for a unified cli/terraform experience with hetzner. hetzner brought me to terraform as they mentioned it in their documentation, newsletter or blog (i cannot remember). since then, i always preferred providers which had a good api or even better a good api and a terraform provider. while working with terraform/opentofu to interact with hetzner i also use their cli tool to quickly create json/yaml lists of resources to import or interact with them. sadly the official terraform provider and the cli tool only supports their cloud product. i really miss that it also supports the new s3 object storage, their d
Read the rest
ns and their share product. in the end i miss that the tool supports all their products and provides a unified way to interact with hetzner via cli and/or terraform. the hcloud tool developers understandably say they only support the cloud api with their tool. in my opinion they really have done am awesome job with the hcloud tool. i hope we can get some traction and shovel some budget to them by creating support requests which ask for support of their other products which maybe lead to a support of all their product. if you feel the same way, you can help: if you already have an account with some servers in it (paying customer), just login to your account and open a support ticket with the text "We vote for https://github.com/hetznercloud/cli/issues/918" i assume votes from accounts without server will also count but will not weight as much as votes from accounts with a few servers which will weight less then accounts with a lot of servers. in the end they are a for-profit company which try to please their customers and provide the tools they need. 1. is this the right location and the right way to ask for that or is this request to specific to be of interest for HN? 2. should they provide a unified experience with their cli tool and tf provider? (why or why not?) 3. do you think voting in such way can really change a thing? cheers
In Should Hetzner unify their CLI tool/tf experience?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.