The social contract behind Sulu

Sulu is released under the MIT license, and it always will be. That license is about as generous as software licensing gets. You can use Sulu, change it, build a business on it, ship client projects with it, and never owe us a cent or ask for our permission. This is deliberate. It is not a temporary state on the way to something more restrictive, and it is not going to change.

But a license only describes what you are allowed to do. It says nothing about what keeps a project healthy. The MIT license is the floor. It is not the building.

Above that floor sits something quieter. It is the understanding that a thing shared by many people needs care from many people. Nobody writes it down, and nobody can make you honor it. Plenty of companies build on open source and give nothing back, and the license permits exactly that. But a project where too few people hold up their end slowly weakens, however good its code is. The open source projects that last are the ones with enough people who choose to honor the contract anyway.

For Sulu, the shared thing is larger than the codebase. It is the community. The bug reports and the issues raised. The community bundles built. It is the documentation. It is the conversations in Slack where someone who solved a problem last month helps someone facing it today. It is the reputation of the project, the quiet confidence that lets a developer choose Sulu for their next project.

Sulu GmbH stewards all of that. But we do not own it. The trust that has gathered around this project was built by everyone who contributes to it.

When people hear the words "contribute to open source," they often picture a pull request against the core. That is one form of contribution, and a valuable one. It is far from the only one.

A bug report with a clear reproduction saves a maintainer hours. A fix to a confusing paragraph in the documentation saves every reader who comes after you. An answer in Slack, a talk at a local meetup, a write-up of how you solved something real with Sulu, a community bundle kept current. Each of these strengthens the commons, and none of them require you to be a core contributor. Small contributions compound, and the barrier to making one is much lower than most people assume.

I want to be straightforward about how Sulu works as a business, because the social contract only holds if everyone can see the whole picture.

Sulu GmbH earns its revenue mainly through development services, consulting and training. We have an official partner program with an annual subscription, and additional products like Sulu.ai and Sulu.cloud. All of this together funds the time we put into Sulu as an open source project. Today we are the largest single steward of Sulu by a wide margin, and that is intentional.

We take that role seriously. Stewarding Sulu means keeping the project moving, making the architectural decisions, holding a high bar for quality, and keeping the documentation and the community in good shape. We are glad to carry it, and we intend to keep carrying it.

Stewardship is part of the social contract as well. It sets a direction, but the best direction comes from a wider conversation, and joining that conversation is a contribution in itself. So we would love for more people to help decide where Sulu goes, in the discussions about what it should become and in the development that gets it there.

Our partner program is the clearest place where this becomes concrete. Partners build real businesses on Sulu, and the partnership itself runs on an annual subscription. That subscription is a contribution in its own right. It partly funds the work that keeps Sulu moving. Beyond it, partners give back in the ways the social contract describes: representing the project well to their own clients, improving the codebase, reporting bugs, filing feature requests, and bringing new people into the ecosystem. It works because both sides give something real.

Our products play a part too. When a team builds with Sulu.ai or hosts on Sulu.cloud, the revenue helps fund the open source project underneath. It is an indirect way of supporting the work, and it adds up.

This brings us back to the question from the start. A partnership or a commercial product is one way to hold up the contract. It is not the only one, and it is not something we expect from everyone. What matters is that you answer the question honestly for yourself: how do you want to take part, and what kind of contribution is realistic for you? For some the answer is a partnership. For others it is a pull request, a careful bug report, or an hour spent helping someone in Slack. Every honest answer holds up the contract.