179 lines
6.5 KiB
HTML
179 lines
6.5 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en-us"><head><script src="/livereload.js?mindelay=10&v=2&port=1313&path=livereload" data-no-instant defer></script>
|
|
<title>Considerations on FOSS and subscription models - phil@bajsicki:~$</title>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
|
|
<meta name="description"
|
|
content="I’ve had this idea for a few days. Mulled it over. Thought about it. And I end up considering options.
|
|
There are a ton of vendors for automation services. Zapier, Make, and others. Fundamentally what they do can be done as a one-time service. ">
|
|
<link rel="canonical" href="http://localhost:1313/blog/foss-subscription-model/" />
|
|
|
|
|
|
<link rel="icon" href="http://localhost:1313/images/logo_w.png" />
|
|
|
|
|
|
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/modern-normalize/1.1.0/modern-normalize.min.css" crossorigin="anonymous" referrerpolicy="no-referrer" />
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
|
|
<link rel="preload" as="style"
|
|
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC|Noto+Emoji&display=swap" />
|
|
<link rel="stylesheet"
|
|
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC|Noto+Emoji&display=swap"
|
|
media="print" onload="this.media='all'" />
|
|
<noscript>
|
|
<link rel="stylesheet"
|
|
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC&display=swap" />
|
|
</noscript>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="stylesheet" href="/css/hugo-tufte.min.css">
|
|
|
|
|
|
|
|
<link rel="stylesheet" href="/css/hugo-tufte-options.min.css">
|
|
|
|
<link rel="stylesheet" href="/css/hugo-tufte-override.css">
|
|
|
|
</head>
|
|
<body>
|
|
|
|
|
|
<article id="main">
|
|
<header class="brand">
|
|
<h1>phil@bajsicki:~$</h1>
|
|
<p class="subtitle"></p>
|
|
<nav class="menu">
|
|
<ul>
|
|
|
|
<li><a href="/">Home</a></li>
|
|
|
|
<li><a href="/about/">About</a></li>
|
|
|
|
<li><a href="/blog/">Posts</a></li>
|
|
|
|
</ul>
|
|
</nav>
|
|
|
|
<hr />
|
|
</header>
|
|
|
|
<section>
|
|
<h1 class="content-title">Considerations on FOSS and subscription models</h1><span class="content-meta"><p class="date">2022-10-02</p><span>3 min read </span><a href="http://localhost:1313/tags/business">business</a> <a href="http://localhost:1313/tags/foss">foss</a> <a href="http://localhost:1313/tags/vendorlock">vendorlock</a> <a href="http://localhost:1313/tags/proprietary">proprietary</a> <a href="http://localhost:1313/tags/saas">saas</a> <a href="http://localhost:1313/tags/scam">scam</a> <a href="http://localhost:1313/categories/tech">@tech</a> </span></section>
|
|
|
|
|
|
|
|
<section><p>I’ve had this idea for a few days. Mulled it over. Thought about it. And I end up considering options.</p>
|
|
<p>There are a ton of vendors for automation services. Zapier, Make, and others. Fundamentally what they do can be done as a one-time service.</p>
|
|
<p>Make the automation script. Feed it the API keys and details. Set it up on a server and run it.</p>
|
|
<p>That simple. What the automation vendors offer is the front-end website, which lets you put together that code yourself in a graphical user interface.</p>
|
|
<p>These carry a subscription charge - for every month you use their servers to run those scripts, you are charged for the privilege of running very basic (and simple) code on their servers.</p>
|
|
<p>AND they don’t actually offer any support. If you want help with setting up an automation, whether it’s because you don’t understand something or because it broke (for whatever reason), you can’t count on them to come in and help.</p>
|
|
<p>With automation vendors like that, you’re entirely on your own to figure out what’s broken, and how to fix it.</p>
|
|
<p>So what if you had your own server? What if you had the scripts that do all the things, yourself? Not hidden behind a paywall, not obscured by fancy pictures and colors. Just there. Working. And in the off-chance something breaks… you have a team on call, and it’s reliably fixed within hours.</p>
|
|
<p>The funny thing is, you can. A basic VPS is about $20-30 a year. Hiring a coder who can create automations in an hour or two is about $100. Then you can easily find maintenance for it at $15-20/h, depending on the specifics.</p>
|
|
<p>Then instead of paying for a subscription… you can have the automations under your control. Your data. Your server. No dependence on a third party who may or may not be using your data for their own ends. No hang-ups or crashes that you can’t respond to. No downtime because of vendor errors.</p>
|
|
<p>Best part: you can then sell that same automation to your clients, or add it as a bonus. It’s already there. It’s working! There is absolutely no reason you can’t make it part of your product line.</p>
|
|
<p>There is a real market for this, and if it can be asked, this kind of offer can easily become the foundation for a managed automations business.</p>
|
|
<p>The idea being that you develop, install, and maintain automations for clients - not through a front-end, but by actually having a human look and write the code to meet whatever needs there are.</p>
|
|
<p>But the TL;DR is:</p>
|
|
<ul>
|
|
<li>Subscription services are a scam. The benefit of ’ease’ and ‘convenience’ is entirely offset by platform limitations and lack of real support.</li>
|
|
<li>Hosting your own software to do these things is much easier than it may seem.</li>
|
|
<li>Having control over your IT and business processes is a sure way to ensure that you’re not getting undercut by vendor issues.</li>
|
|
<li><a href="https://my.fsf.org/join">Join the FSF.</a></li>
|
|
<li>Use <a href="https://www.gnu.org/software/emacs/">Emacs</a>.</li>
|
|
</ul></section>
|
|
<section><footer class="page-footer">
|
|
<hr />
|
|
|
|
<div class="previous-post" style="display:inline-block;">
|
|
|
|
<a class="link-reverse" href="http://localhost:1313/blog/i-love-emacs/?ref=footer">« I really, really like Emacs</a>
|
|
|
|
</div>
|
|
|
|
<div class="next-post", style="display:inline-block;float:right;">
|
|
|
|
<a class="link-reverse" href="http://localhost:1313/blog/vps-is-my-new-friend/?ref=footer">VPS is my new friend »</a>
|
|
|
|
</div>
|
|
|
|
<ul class="page-footer-menu">
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<div class="copyright">
|
|
<p>
|
|
|
|
©2024 Phil Bajsicki
|
|
|
|
</p>
|
|
</div>
|
|
|
|
|
|
</footer>
|
|
</section>
|
|
<section><nav class="menu">
|
|
<ul>
|
|
|
|
<li><a href="/">Home</a></li>
|
|
|
|
<li><a href="/about/">About</a></li>
|
|
|
|
<li><a href="/blog/">Posts</a></li>
|
|
|
|
</ul>
|
|
</nav>
|
|
</section>
|
|
</article>
|
|
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
</html>
|