~/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

$ ls ~/topics
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

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.

Open-source licences, in one sentence each
LicenceWhat it lets you doThe catch
MITUse, change and sell it, almost without limitsKeep the copyright notice. That’s about it.
Apache 2.0Same freedom as MIT, plus an explicit patent grantYou must note changes you make to the files
GPLv3Use and change it freelyIf you distribute your version, it has to be GPL too
AGPLv3Same as GPLRunning it as a network service counts as distribution
Source-availableRead and often self-host the codeUsually bans offering it as a competing hosted service; not open source by the usual definition
Where a typical cloud bill actually goes
Line itemWhat drives itEasy to forget because…
ComputeInstance size × hours runningTest servers left on over the weekend still count
StorageGigabytes stored, plus snapshotsOld backups and snapshots quietly pile up
EgressData leaving the provider’s networkInbound is usually free, so nobody models outbound
Managed servicesDatabases, queues, search, AI APIsPriced per request or per hour, not per server
Support planOften a percentage of total spendIt grows automatically as everything else grows
Credits & commitmentsStartup grants and prepaid spendThey 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.

Owen Calder, editor of Puffin Notes

whoami

Owen Calder

Owen has spent most of his career keeping other people’s software running — first on racks of Linux servers, later across more cloud accounts than he’d like to admit. He writes Puffin Notes for the person who gets the pager alert and the invoice.

Contact Us

We'd love to hear from you