
An install command that says thank you
I would not be here without open source software.
This is not a figure of speech, but an objective truth.
I learned most of what I know about software engineering by reading other people’s code, leveraged free tools I wouldn’t have been able to afford otherwise, and built most of what I’ve shipped on top of other people’s packages.
This is not just my story, but the story of nearly every developer I’ve met. Somebody left a door open, and we simply had to walk through it.
Yet most of us have never once said thank you to the people who gave us all this and asked for nothing in return. That’s what Obrigado aims to change.
Turbulent tAImes
Consuming and producing open source has never been cheaper. An agent can pull in a dependency, wire it up, and move on in seconds. It can fork a codebase and tailor it to your needs with little to no effort on your part. And because anyone can open a pull request on an open source project, so can your agent, whether or not anyone involved has actually read the code.
The friction that used to make you read a library’s documentation or source before adopting it - and sometimes, having read it, file an issue or send a patch - is going away. It was never a feature, exactly. But an enormous amount of contribution, understanding, and ecosystem building happened inside that friction. Arguably more importantly, it also acted as a rate-limiter. Sending a patch used to take real effort, so the people who sent one had usually done their homework.
Now an agent can write a pull request in minutes, and it still takes a person just as long to review it. So maintainers are getting more contributions than ever, and a lot of them are slop: code that doesn’t build, fixes for bugs that don’t exist, security reports for vulnerabilities a model made up. Someone still has to read every one of them before closing it. In January 2026, curl shut down its bug bounty largely because of it. Fewer than one in twenty reports had turned out to be real the year before, and its lead maintainer wrote about the toll the rest were taking on the team.
The pitch was that AI would free maintainers up to do more of the work they actually care about. Instead, everything around them moves at the speed of an agent, while they still move at the speed of a person with a day job and a few free evenings.
Something has to give.
Even projects that had figured out how to pay for themselves are struggling. The same month curl ended its bounty, Tailwind Labs laid off three-quarters of its engineering team. Tailwind had never been more popular, but if your agent already knows how to write it, you have little reason to visit the docs, and the docs were the only place people found out about the paid products that funded the framework. Docs traffic was down about 40% from early 2023, and revenue was down close to 80%.
Tailwind was at least big enough to be heard, and within days Vercel, Google AI Studio and a handful of others had signed on as sponsors. Most maintainers don’t have that kind of audience. They’ve been saying all of this out loud for a while, and mostly what they get back is sympathy, which does not put food on the table.
Yet another attempt
People have been trying to fund open source for about as long as it’s existed, and it’s harder than it sounds, because money changes things. Open source runs on people giving their work away, and the moment you attach a reward to something, you start attracting people who are only there for the reward. curl’s bug bounty was meant to make curl safer, and by the end, most of what it attracted was slop.
So most attempts to fund open source have been careful to keep the money at arm’s length. Sponsorships usually come with no strings attached, and foundations exist partly so that no single company can own a project. Obrigado is yet another attempt in that flavor.
Here’s how it works: you install it the same as you would any other package, and it renders a single labelled sponsored line to your coding agent’s status bar - currently Claude Code, Cursor/VScode, IntelliJ, and OpenCode are supported.
By default, the only things it sends home are the package names in your lockfile, which agent and OS you’re using, and whether anyone’s at the keyboard, all under a random install ID rather than an account. Never any sensitive info like your hostname, your repo name or a file path. The client code is also open source so you can verify it yourself.
Advertisers bid against each other for that line. They can only aim at your packages, your country, your IP range, and saying no still funds maintainers just the same, just decreases the ability to target and by extension the value of the ads. Every campaign’s targeting is public, and any maintainer can stop advertisers from targeting their packages, no questions asked.
For a company, it’s simply advertising. It comes out of a marketing budget they already have and gets measured like any other ad, where the majority of it just happens to end up with the maintainers their audience depends on. It also gives them access to a cohort that’s very hard to reach otherwise: developers will write browser shells, modify kernels, and block ads at the DNS level. There’s no way to reach them unless they want to be reached.
For you, it’s one line in a status bar you were already looking at. You don’t pay anything, and you don’t earn anything either, so nobody has a reason to game it. What you get is open source that has a better shot at still being maintained next year.
Our goal
One day we’d like to have a team of elite full-time engineers on payroll, who don’t have to worry about making ends meet or securing sponsorships or pandering to patreons, whose only job is to contribute to the open source everyone depends on.
That might sound ambitious, but the math is friendlier than you’d think.
The average global salary for a full-time engineer is around $136,000 a year, and goes up to $390,000 for the top 10% in the US, as per levels.fyi’s data. On our end, each sponsored line stays up for thirty seconds and sells for at least $2.18 per thousand views, 70% of which goes to the pool. So a developer who works with their agent for three hours a workday brings in about $130 a year for maintainers.
That’s somewhere between 1,000 and 3,000 developers per engineer, or 10,000 to 30,000 for a team of ten, which is a small fraction of the developers already using coding agents. Advertisers would be spending $1.9 to $5.6 million a year, which is less than a sixth of what Datadog alone spent on advertising in 2025.
Of course, that assumes every slot gets sold, which we still have to prove we can do. It also assumes they all sell at the minimum, when advertisers targeting a specific stack or region should pay more. On paper, at least, a team of ten is well within reach.
With the remaining 30%, we cover payment processing, legal and infrastructure costs, put food on our own table, and fund the other projects we’re working on. None of that ever comes out of the maintainers’ 70%.
Obrigado
curl -fsSL https://obrigado.dev/install.sh | sh && obrigado install