~/puffin-notes $ cat README
The software is free.
Running it never was.
Puffin Notes is a small, independent publication about open source, Linux and the infrastructure underneath modern software — and about the part most tutorials skip: what it actually costs to keep it running.
Open source · Linux · Cloud · Operating costs
open-source/ infrastructure/ costs/
$ grep -c “it depends” ~/notes/*
412
$ uptime
# the only metric your users notice
$
// why this exists
Most guides end at “it works on my machine.” That’s where the real work starts.
Getting an open-source project to run is usually an afternoon. Keeping it running for three years — patched, backed up, monitored, and paid for — is a different job, and it’s the one that decides whether a project was a good idea.
We write for the people doing that second job: developers who ended up owning the servers, small teams running their own stack, and founders who just opened a cloud invoice and want to understand it.
Expect practical write-ups, the occasional strong opinion, and a lot of tables. When we compare hosting options, we show the numbers. When a licence change affects you, we explain what actually changes, not just what the announcement says.
We don’t sell software, hosting or consulting. Nobody pays us to recommend a vendor. If we ever link to a product, it’s because we think it’s useful, and we’ll say so plainly.
$ tree -L 1 ~/topics
Three folders. Everything we write lives in one of them.
/open-source
Open Source & Linux
Projects worth knowing, licence changes that matter, and how the communities behind the software actually work — including who pays the maintainers.
e.g. what a licence switch means for self-hosters · choosing a distro for servers you won’t touch for years
/infrastructure
Cloud & Infrastructure
Servers, containers, managed services and the trade-offs between them. Where to run things, how to move them, and how to avoid getting locked in by accident.
e.g. self-hosting vs managed databases · the real cost of leaving a cloud provider
/costs
Running Costs
The money side of software: hosting bills, egress fees, support contracts, startup credits and commitments. How to read the invoice, and how to make it smaller.
e.g. why egress is the line nobody budgets for · using cloud credits before they expire
$ git log –oneline -3
Latest notes
- Azure Startup Credits for OpenAI GPT-6 Models: Costs Compared
Running Costs · Cloud & Infrastructure · ~18 min read Microsoft will give an early-stage startup up to $150,000 in Azure credits, and those… Read more: Azure Startup Credits for OpenAI GPT-6 Models: Costs Compared - Cloud Egress Costs 2026: What It Really Costs to Leave AWS, Azure & GCP
Cloud & Infrastructure · Running Costs · ~18 min read We priced what it costs to move 10 TB out of the major clouds,… Read more: Cloud Egress Costs 2026: What It Really Costs to Leave AWS, Azure & GCP - Server Decommissioning Checklist: 7 Steps, Physical & Cloud
Open Source & Linux · Cloud & Infrastructure · ~13 min read Switching a server on takes an afternoon. Switching one off properly takes… Read more: Server Decommissioning Checklist: 7 Steps, Physical & Cloud
commit 7f3a9c1 · Author: Puffin Notes
“Nobody chooses a stack because of its hosting bill. Plenty of teams leave one because of it.”
// quick reference
Two tables we keep coming back to.
| Licence | What it lets you do | The catch |
|---|---|---|
| MIT | Use, change and sell it, almost without limits | Keep the copyright notice. That’s about it. |
| Apache 2.0 | Same freedom as MIT, plus an explicit patent grant | You must note changes you make to the files |
| GPLv3 | Use and change it freely | If you distribute your version, it has to be GPL too |
| AGPLv3 | Same as GPL | Running it as a network service counts as distribution |
| Source-available | Read and often self-host the code | Usually bans offering it as a competing hosted service; not open source by the usual definition |
| Line item | What drives it | Easy to forget because… |
|---|---|---|
| Compute | Instance size × hours running | Test servers left on over the weekend still count |
| Storage | Gigabytes stored, plus snapshots | Old backups and snapshots quietly pile up |
| Egress | Data leaving the provider’s network | Inbound is usually free, so nobody models outbound |
| Managed services | Databases, queues, search, AI APIs | Priced per request or per hour, not per server |
| Support plan | Often a percentage of total spend | It grows automatically as everything else grows |
| Credits & commitments | Startup grants and prepaid spend | They make early bills look small — until they expire |
$ man puffin-notes
Questions people ask us
Who is this for?
Developers, sysadmins and small teams who run their own software, plus founders and finance people who have to pay for it. You don’t need to be a kernel hacker, but we won’t explain what a terminal is.
Is self-hosting cheaper than the cloud?
Sometimes. It depends on how steady your workload is, how much your time is worth, and how much data you move around. We try to answer it with numbers for specific cases rather than with a slogan.
Do you take sponsored posts?
No paid content dressed up as editorial. If a post links to a product or service, it’s because we think it helps the reader, and any commercial relationship is disclosed in that post.
Can I suggest a topic?
Please do. Our best posts usually start as a reader question along the lines of “why is this line on my invoice so big?”
Is this the original Puffin Group?
No. This domain once belonged to an early open-source software company that was acquired around the turn of the millennium. Puffin Notes is a new, independent publication under unrelated ownership. We have no connection to that company, its founders or its successors, and we don’t speak for any of them.
