Félix Malfait

Hey Chris, you can use it in prod with real customers without paying anything (for example you could create a cloud offering competing directly with Twenty.com). The only limitation today is on SSO and our implementation of Stripe Billing. Happy to discuss on a PR if you want to suggest changes, I agree wording could be improved

Would love to know if @grok has correctly interpreted @twentycrm commercial license that's mixed in with their open source license. For example it is open source unless you use it in production with real customers?! In the context of the Twenty project (github.com/twentyhq/twenty), **production use** refers to deploying and operating the software in a live, operational environment where it is used for real-world business or commercial purposes, such as managing actual customer data, running business processes, or providing services to end-users. This is distinct from using the software for **development**, **testing**, or **non-commercial purposes**, which are permitted under the **GNU Affero General Public License (AGPL) v3** without requiring a commercial license. ### Key Points About Production Use in Twenty - **Definition**: Production use involves running the software in a setting where it supports active business operations, such as a live CRM system managing real customer interactions, pipelines, or workflows. - **Licensing Restriction**: Files marked with `/* @license Enterprise */` in the Twenty codebase are subject to the **Twenty.com Commercial License** for production use. To use these files in a production environment, you must comply with Twenty's Terms of Service (twenty.com/legal/terms) and hold a valid **Twenty Enterprise Edition subscription** for the appropriate number of hosts and seats. - **Examples of Production Use**: - Hosting Twenty on a server to manage customer data for a business. - Using Twenty’s features (e.g., contact management, email integration, or pipelines) to support live business operations. - Deploying Twenty in a commercial setting where it interacts with real clients or generates revenue. - **Non-Production Use**: The AGPL v3 allows free use of the software (excluding enterprise-marked files) for: - Development (e.g., coding, modifying, or building features). - Testing (e.g., evaluating the software in a sandbox or staging environment). - Non-commercial purposes (e.g., personal projects or open-source contributions). - **Enterprise Features in Production**: Certain features, like **Single Sign-On (SSO)**, are explicitly tied to the commercial license for production use. Using these in a live environment requires a subscription, though enforcement may be lenient as of July 2025. ### Implications - If you deploy Twenty in a production environment without a commercial license, you are limited to using only the AGPL v3-covered components and must avoid using enterprise-marked files or features (e.g., SSO) in production. - Violating the commercial license terms (e.g., using enterprise features in production without a subscription) could lead to legal or compliance issues, as outlined in Twenty’s Terms of Service. - For clarity on which specific files or features require the commercial license, check the codebase for `/* @license Enterprise */` markers or consult the official documentation (twenty.com/docs). If you need details on the **Twenty Enterprise Edition subscription** or pricing, visit twenty.com/legal/terms, as pricing information is not publicly detailed in the provided sources.

Does @twentycrm really wuskify as open source if parts of the source code are under a commercial license? I wonder if you can even really self post it without violating a license. Need to go look at all files in repo.

@mitsuhiko Screens for inspiration (doesn’t have to go as far) figma.com/design/xt8O9mF…

@mitsuhiko github.com/twentyhq/twenty would love to see you try on our repo! Challenge: add a Merge option to the command bar to merge multiple duplicate records into one. So far none of our attempt came close to building a feature of that level of complexity cleanly

Does someone have an Open Source codebase they had little success with agentic coding I could use as a test-bed to improve the agent workflow? I think I might make a video about that. x.com/mitsuhiko/stat…

Congrats to the @twentycrm team on the $5M round! Twenty (YC S23) is building a flexible Open Source CRM alternative to Salesforce: techcrunch.com/2024/11/18/twe…

OSS has a great fit with enterprise infrastructure — not only with the usual data/cloud infra and dev tools, but also core business suites like CRM and ERP. And I am happy to announce that we led a $5M seed round of @twentycrm, building an open-source alternative to Salesforce!

@pierrevalade Please do it!

💗 I think with AI now, if I was to build Sunrise again — would look very different! …

@Bptstmlgt @aurelien_dio @levelsio Non j’étais trop obnubilé par ce beau Samoyède 😍

@aurelien_dio @levelsio @_felx t’as reconnu ? Ouais de Meylan ✌️

🐶 Testing the new Hailuo AI video model on Photo AI today I'm not sure if I like Kling AI or Minimax better But Kling AI's content filter is way too strict rn so half the jobs fail even if it's not NSFW, so I will use Minimax as a fallback 100% AI photo -> 100% AI video

iiiit's LAUNCH day 🍾 we're superduper excited to bring this community-developed platform live today! it is a day of celebration and we're hittin it off with a @hacktoberfest hackathon 🔥 all infos here, have a look ⬇️ producthunt.com/posts/oss-gg

Amazing time to start a robotics startup or just tinker for fun. And it’s open source!

@pierre_burgy @peer_rich at first I thought the .com gave 2000s energy but now I understand it was a genius move you’re getting a backlink + stealing the show in every mention🙇‍♂️

I am delighted to see an entire wave of new projects (Cal.com, Inc., Meilisearch, Medusa, PostHog, Twenty, and more) that better serve their missions, thanks to their respective communities. 👏

What is the most significant advantage of building open-source software instead of proprietary software? 🤩 We could mention security (self-hostable + the code is reviewed by thousands of users), a shorter feedback loop, cost-effectiveness, longevity, or sustainability. 🧵

@gregisenberg Betting on @openbb_finance by @didier_lopes, very high barrier to entry that makes a competitor hardly fundable but open source gives the intermediate momentum/validation steps to get there

Does anyone know why?

@McPizza0 @twentycrm github.com/twentyhq/twent…

any good OSS apps with icon selection? wanna see how its implemented

We released v0.20 with 121 improvements. Here are some of them: - audit logs for every object - a new timeline design for every object that features audit logs, emails, calendar events... - ability to create objects directly from an object page in a side panel (e.g. create a person from a company's page) - ability to invite team members by email - calendar and email blocklist - new onboarding flow with calendar/email import and team invite - bringing our REST API closer to parity with our GraphQL API - new documentation website - minimize task/note and keep it open while navigating - new command bar design - performance of table views

Google trends for Exit Tax in France after Macron dissolved the National Assembly and the next prime minister is likely to come from far left or far right

@thdxr We were using emotion and started migrating to Linaria last week because we display table views with lots of cells and emotion had an impact on performances. It’s the same syntax.

so in 2024 what non-tailwind things are people using for styling? pitch me on your choice - i'm specifically looking for thoughts around long term maintainability

@McPizza0 🙋‍♂️

I have some questions who's up for a chat?

@synchrolix Not that much. Around 50 people entered a credit card to signup to the cloud version - but I’d guess most are just curious and will churn

@_felx Does the traffic convert to real users, tho?

HN is still the best load testing service out there

@nevodavid summoning the Github trend expert! Any idea why this didn't make us trend? It usually did (+250 stars in 24 hours)

I think the most common mistake in today's AI excitement is thinking all software must become “AI-first”. Construction didn’t become “electricity-first” when electricity arrived. Paris didn’t need to be rebuilt. Haussmannian buildings and high-quality constructions evolved and still stand. Starting with weak software foundations and a direct focus on LLM is perhaps the worst way to build a defensible software in the era of AI. The best way to future-proof your SaaS is to focus on deep engineering problems. The core of what makes software great isn't changing; it's getting more important.