Flagsmith’s Post

View organization page for Flagsmith, graphic

1,210 followers

Deciding what to open source can be tough. Here's a bit from Ben Rometsch on our open source philosophy and how we decide! #opensource #buildinpublic #softwaredevelopment

View profile for Ben Rometsch, graphic

When we release a feature we ask the same question: "Would this be useful to a single developer?" This helps us choose what to open source and what to put in the commercial version. i.e. A solo developer building their own app should see no difference between the open-source version and the commercial version. A couple of examples: - Core product features like feature flagging, A/B testing, alerts for stale flags all stay open. - Role-based access control is closed. Why? You can use the platform without RBAC. Developers generally don't care about RBAC and it doesn't affect their work. ↪ But the business and procurement teams buying software care about RBAC and want to be able to do stuff like stopping interns from adding kill switches to a public website. So RBAC gets put into paid commercial plans because we need to be a sustainable business. The trick is to charge for features that don’t make your product objectively better to the developer. Never kneecap the platform for developers.

To view or add a comment, sign in

Explore topics