Mintarc
  ITコスト診断   お問い合わせ   メルマガ登録   ブログ    パートナー
Cost Assessment Questions?' Monthly Letter Monthly Blog Our Partners

Email us |TEL: 050-1720-0641 | LinkedIn | English | 日々のブログ | Q & A

Mine's Daily Postings

日本語の投稿

2026年4月

2026年1月

2025

12月の投稿

11月の投稿

10月の投稿

9月の投稿

8月の投稿

7月の投稿

6月の投稿

5月の投稿

4月の投稿

3月の投稿

Answers to Questions

A place for answers to questions we get about the things we post

What is the main difference between FOSS, FLOSS, and OSS

We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom ("free as in speech"). FLOSS adds "Libre" to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.

What are the risks of staying with "Big Tech" SaaS solutions?

This is always a "Prove it to me" questions LOL - Basically the risks include "SaaS Creep" (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.

What is OWASP ZAP and why should a business use it

Its is an open-source web security tool. It acts as a "manipulator-in-the-middle" to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.

What is "Shadow IT" and how does FOSS mitigate it?

This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.

My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?

The Business Risks You Are "Ignoring"

Even when things are running perfectly, relying on a single proprietary provider creates "silent risks" that don't matter... until they suddenly do.

  • The "Price Creep" when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the "cost of switching" becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.
  • Data Sovereignty & Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.
  • The "Feature Sunset", Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.

Is anti-Google Technical or Ideological?

  • FOSS advocates see Google as a "centralized authority" that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are "digital tenants" rather than "digital owners."
  • FOSS companies argue that Google’s code is a "black box." You can’t audit it for security flaws or "backdoors" yourself; you have to take Google's word for it. Many of us FOSS folk believe "given enough eyes, all bugs are shallow" meaning open code is inherently more secure because it can be audited by anyone.

You don't need to quit Google to benefit from Open Source. a "Hybrid Approach"

  • Stay on Google Workspace for email and docs because the collaboration is your preference.
  • Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.
  • Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.

English

April 2026

March 2026

February 2026

January 2026

2025

December 2025

November 2025

October 2025

September 2025

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

February 2025