I completely understand why some people are tired of subscriptions. These days it feels like every app, every service, every small tool wants to become “just another monthly payment”. After a while that becomes annoying and hard to keep track of.
So when people look at FrontierWings and say, “Oh no, not another subscription,” I get it. That reaction is fair.
Still, I want to explain why I chose this model, what I think the upsides are, and where I fully admit the downsides are.
Yes, it is another recurring payment
Let’s start with the obvious downside.
A subscription is a recurring payment. Even if the monthly price is relatively small, it still adds up, and it still becomes part of that growing pile of things people need to manage. I understand very well why some people prefer a simple one-time purchase: pay once, own it, done.
And yes, if someone uses FrontierWings for years, they may eventually pay more than they would have paid for a fixed-price addon. That is a another valid point.
The question is not whether subscriptions are automatically better. They are not. The question is whether this model makes sense for FrontierWings specifically.
FrontierWings is not a download-and-forget addon
FrontierWings is a cloud platform.
It has user accounts, missions, pilot progress, companies, validation, backend systems, a simulator client, server infrastructure, and ongoing maintenance. That makes it different from a scenery package, an aircraft, or a small offline tool.
Whether FrontierWings is sold as a subscription or as a one-time purchase, users still have to trust me to keep the platform running, either way. If the servers are shut down, the platform is over. That is not a subscription-specific problem. It is simply the nature of a cloud-based product.
Why I chose the subscription model anyway
If FrontierWings had a one-time price, it would probably need to be something like 40 or 50 euros, maybe more, to make sense. But that creates a much higher barrier for the user. Someone would have to pay a fairly large amount before really knowing whether the platform fits their style of flying.
And because FrontierWings is currently in early access, I also have a no-refunds policy to protect myself and the project.
That may sound strict, but FrontierWings is a small one-person platform, not a large company with a support department, finance department, and lots of room to absorb refund risk. I cannot realistically build the product around larger upfront payments and then also carry the risk of those payments being reversed after the service has already been used.
This is one of the reasons why I think the lower monthly subscription is the more honest model here.
For the user, trying FrontierWings does not mean committing to the price of a full addon aircraft or scenery package. They can try 7 days for free, then subscribe, fly some more missions and tours, see whether the idea clicks with them, and cancel if it does not.
For me as the developer, the risk is also more manageable. I do not have to rely on a high one-time price that would make my no-refunds policy feel much harsher.
It is not perfect, but it keeps the initial risk smaller on both sides.
I am not interested in taking the money and running
One thing I really want to avoid is the feeling that I am collecting a larger fixed payment from people and then disappearing.
That is not what this project is about.
FrontierWings is still growing. I currently only have a handful of subscribers. They are very helpful, giving me valuable feedback. There are features I want to add, rough edges I want to smooth out, documentation and videos to create, and many small improvements that only become obvious once people actually use the platform.
A subscription fits that ongoing reality better than pretending the product is “finished” at the moment of purchase.
It also means people can leave when they no longer feel it is worth it. I think that is fair. I would much rather have users who actively decide that FrontierWings is still useful to them than people who paid a high price once and then feel disappointed.
What about freemium?
Someone also asked whether FrontierWings could use a freemium model.
In theory, I understand the idea. Let people use a limited version for free, then charge only for the advanced features. That can work for some products.
But honestly, I am not a big fan of freemium models, especially not for FrontierWings.
Freemium often creates strange incentives. As a developer, you have to decide which parts of the product are useful enough to attract people, but not useful enough to make the paid version unnecessary. That can lead to artificial limitations which exist only because the business model needs a dividing line between “free” and “paid”.
I do not really like that.
FrontierWings is also not a huge platform with venture capital behind it. It is a small niche project. Even free users still create costs: server usage, accounts, stored data, support requests, bug reports, edge cases, and general maintenance.
Free is never actually free on the operational side.
If the free version is too limited, it feels like a frustrating demo. If it is too generous, the paying users effectively subsidize a larger number of free users. For a huge company, that may be a strategy. For a small one-person project, I am not convinced it is healthy.
I would rather keep the model simple and honest: FrontierWings is a paid platform, but the monthly price is meant to keep the initial commitment low.
That feels cleaner to me than building a deliberately restricted free version.
It will not be for everyone
Some people will never subscribe to a flight sim platform, no matter the price. That is perfectly fine. I do not take that personally.
Others may prefer to wait and see how FrontierWings develops before trying it. Also fair.
And some people may subscribe for a month here and there, fly a bunch of missions, pause for a while, and come back later. Honestly, I think that is fine too. Flight simming itself often comes in waves. It did for me during the last 40 years. Sometimes we fly a lot, sometimes we barely touch the simulator for weeks.
I do not think every user needs to be permanently subscribed forever for the model to make sense.
My goal
My goal with FrontierWings is not to build the most aggressive monetization machine possible.
It is to build a platform that makes bush flying and small-aircraft operations more meaningful: finding contracts, flying to remote places, building a pilot career, and having a reason to go somewhere beyond “I guess I’ll just pick an airport”.
The subscription model is my attempt to make that sustainable while keeping the initial commitment low.
It has downsides, I know that. Subscription fatigue is real, and people are right to be careful with recurring payments.
But for FrontierWings, I believe there is a fair version of this model: one where users do not have to risk a large upfront payment, where my no-refunds policy does not become an unreasonable burden for the user, and where the platform can continue to grow instead of being treated as finished on release day.
That is the version I am trying to build.