OlympAPI: Local-first API client. Lifetime license, no subscription.

Hello Product Hunters,

I’ve been a System Administrator and Software Engineer for over 20 years and currently manage more than 30 Linux servers, 90% of them running Docker containers. I also manage some from local Companies, I mostly managed everything using PuTTY, but without proper workflows, it quickly becomes a pain. I just couldn't find any existing software that actually fit my needs or they changed their pricing model to subscriptions. So I started to create my own Software for everything and recently I decided to make the Apps I've created ready to be released.

I’m really frustrated with the direction big software companies are taking—forcing everyone away from Licensing and into SaaS models with mandatory accounts, cloud syncing, and feature paywalls. I don't run a massive company and I want to keep my data and infrastructure on my own machines, not in someone else's cloud. Plus, I don't want to pay monthly subscriptions for ten different tools, which solve a problem that is already solved for decades.

That’s why I founded OlympStack with the first Product: OlympSSH Commander. My goal is to build practical, comprehensive tools for Linux server management, Docker operations, monitoring, API testing, and infrastructure administration. All tools are free to use, with the option to purchase lifetime licenses—one payment, use forever. No subscriptions, no cloud forced on you, just full control for developers, freelancers, and small teams.

I got asked about my Update and Upgrade Strategie of the Tools and this is the answer.

Let me explain my approach using the example of my recently released app, OlympAPI:

You purchase a major version — say, v1.0.0. Minor updates, patches, and security fixes are included.
I maintain a public roadmap on the website featuring so-called "low-budget features": an API designer, an overview and documentation for workspaces and collections, keyboard shortcuts, code generation, an SSL certificate inspector, and additional display options. All of this is going into Version 1. As I mentioned, the practical workflow for an API client hasn't changed much in decades — we're still just making HTTP requests — so the app should run for years with minimal maintenance.
It is precisely this low maintenance requirement that frees up time for me to work on v2.

My ideas for OlympAPI v2 include "Bring Your Own AI" integration, CSV-based testing, a mock server, and an MCP client. That represents the next major step — a paid, optional upgrade. Does v1 meet your needs? Then simply keep using it. There is no "phone home" feature designed to disable the program, and I will continue to provide security updates and bug fixes for critical issues (those that would render the app unusable) as a standard service.

Note: While Version 1 remains available for €29, the cost to upgrade to Version 2 will be €20, as Version 2 is expected to cost €49. Those who only need the "Basic" API client can still purchase it for €29 and upgrade later; users requiring advanced features—such as AI integration or mock servers—can purchase Version 2 directly with the full feature set. (Prices are subject to change, but you own the software forever at the price you paid for it.)

I place a high priority on transparency in my projects and currently rely heavily on AI in all my workflows. Sometimes I run ChatGPT, Codex, and Claude as well as Claude Code simultaneously. I write prompts that are 10 to 20 pages in editor formatted with markdown and receive 100 pages of responses and explanations, which can be very time-consuming to produce.

I would really appreciate any feedback on my product, the idea, and my approach.

Hello Product Hunters,

I got asked about my Update and Upgrade Strategie of the Tools and this is the answer.

Let me explain my approach using the example of my recently released app, OlympAPI:

You purchase a major version — say, v1.0.0. Minor updates, patches, and security fixes are included.
I maintain a public roadmap on the website featuring so-called "low-budget features": an API designer, an overview and documentation for workspaces and collections, keyboard shortcuts, code generation, an SSL certificate inspector, and additional display options. All of this is going into Version 1. As I mentioned, the practical workflow for an API client hasn't changed much in decades — we're still just making HTTP requests — so the app should run for years with minimal maintenance.
It is precisely this low maintenance requirement that frees up time for me to work on v2.

I would really appreciate any feedback on my product, the idea, and my approach.