Why a Git client does not need a subscription
A local Git client is classic software on your Mac, not a running service. A stance on owning instead of renting and when a subscription is fair anyway.
Renting software has become a habit
In recent years almost everything has turned into a subscription. Editors, password managers, note apps, even individual features in programs you used to simply own. For a tool you use every day, that adds up not only on the invoice but also in your head. A quiet feeling remains that you own none of it.
For some software a subscription makes sense. When a service runs continuously in the background, servers stand ready and data is synced, you pay for ongoing operation. The question is whether a Git client belongs in that group.
What a Git client actually does
A Git client is an interface to a tool that sits on your machine. Git itself is local. Your repositories, your history, your commits, all of it lives on your disk and belongs to you. The client shows it to you and helps with staging, committing, merging and managing branches. That does not need a running server in the background or a monthly rent.
Of course there are services around it, such as hosting with a provider. But you pay for hosting there, not at the client. The client running on your Mac is a classic piece of local software.
The difference between renting and owning
With a subscription, usage stops when payment stops. You can pay for years and end up empty handed the moment you pause. Some clients, such as GitKraken or Tower, work with this model. It is not immoral, but it shifts the relationship. You are the tenant of your working tool.
A one-time purchase turns that around. You pay once, the version is yours, and it keeps running whether or not you are still a customer tomorrow. That is exactly how Spire works. Updates within the purchased window are included, and after that you keep the last version you received. Nothing expires, nothing locks itself.
Why this is more than a price question
It is not only about the amount. It is about control and about calm. A tool you own cannot be switched off on you. You decide when to update. You are not at the mercy of the next price jump, nor of the worry that a feature you use daily moves behind a new tier.
For many developers this is a principle. Your own tools should belong to you. A carpenter does not rent the plane by the month.
When a subscription is fair anyway
To stay honest: there is software where a subscription is appropriate. Anything that runs a real ongoing service causes ongoing cost, and that has to be covered. Criticising that across the board ignores the reality of running servers and support. The point is not that subscriptions are bad in general. The point is that a local Git client is not one of those cases.
What ownership means concretely
- The purchased version runs permanently, even without further payment.
- No loss of features if a subscription were to lapse.
- You decide when to update.
- No risk of daily features moving behind a new tier.
Our stance
Spire exists because we wanted a Git client you buy and own. Native on the Mac, focused, and without the question of whether it still runs tomorrow. That is not a marketing pose but the reason the project is built the way it is. If that matters to you, you are in the right place.