HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
twentyhq
twenty
TypeScript2023–2026
twentyhq / twenty

twenty

The open alternative to Salesforce, designed for AI.

13Distinct people
20Mentions
0Explicit recommenders
60.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The open alternative to Salesforce, designed for AI.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year20 dated mentions

Observed mentions: 2023-07-19 18:54:50 UTC to 2026-10-28 20:45:51 UTC.

0369122023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 12 mentions; 4 submissions, 8 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1248
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC431

What Hacker News says

4 sources
aray07·Oct 28, 2026Submission

Show HN: I built a tool that finds reliability bugs in your code

Hey HN, I’m Abhishek. I'm building Opslane, a tool that finds reliability issues in your code. On every PR, it spins up your entire app and then tries to find weak spots that would break in production. Demo: https://youtu.be/47phxkdh6f0 Example: We tested Opslane on Lago (open-source billing) and found a bug where customers get double charged. Opslane made Stripe take the money and then return a 500. Lago marked the payment failed. A retry from the dashboard charged the customer again. https://github.com/getlago/lago-api/issues/6903 Why I built this I used to work on reliability at Robinhood. We used to run chaos testing in our staging environments: inject faults in various parts of the system and see what breaks. We found issues like Kafka or Redis being unavailable for a few seconds could take the whole app down. But that kind of testin
Read the rest
g was expensive. It needed a well maintained staging environment. Engineers needed to know what to test. Most teams never actually did it. Over the last year, coding agents have gone writing some of my code to almost all my code now. Teams are shipping way more code than they were 6 months ago. Code review tools read the diff, but a lot of reliability bugs aren't in the diff. They're in how your code behaves when Stripe, Redis or the network misbehaves. And e2e tests usually mock those services out and test the happy path. Agents have made this type of testing a lot cheaper. And we will see more of this (kinda like security scanning / testing) How it works A full copy of your app per PR: Postgres, Redis, Kafka, SQS, S3. Working copies of your third-party dependencies: Stripe, Slack, Gmail and more. Traffic goes through our proxy, which lets us inject failures. The agent picks what to test: It reads every PR and writes down invariants that need to hold (for e.g. a customer should never be charged twice). It then injects faults likely to break the invariants. Bugs we've found We ran Opslane on some popular open-source apps and here are some of the bugs we have found: 1/ Twenty: deleting a workspace while Stripe is failing locks everyone out, and billing keeps going. Twenty merged a fix. (https://github.com/twentyhq/twenty/issues/28043) 2/ Dub: a restart in the middle of a payout paid a partner $240 for $120 owed. (https://github.com/dubinc/dub.link/issues/4707) Full list: opslane.com/open-source Opslane is pretty early - we have a couple of early customers. We have found bugs in their system that their other code review tools missed. Would love to get feedback from folks and how they are seeing the reliability of their systems evolve over time with agents.
6 points · Open discussion
It’s not as far-fetched as people think. I see so many comments here doubting you can vibe code a full CRM or e-commerce SaaS, but a skilled AI-assisted programmer absolutely can, especially if they're aware of strong open-source alternatives already out there. For Salesforce-like CRM, there's Twenty[0], a good-enough alternative. For Shopify-style e-commerce, Medusa[1] is a headless commerce platform. The real power comes from using AI to study how these projects implement specific features (payments, inventory, customer dashboards, etc.) and adapt them to your stack. AI excels at finding the "seams" (those connection points where a feature ties into the tech stack) and grasping the full implementation. The trick is knowing precisely where the feature lives in the code (files, functions, modules), because AIs often miss scattered pieces
Read the rest
otherwise. That's what I'm building at opensource.builders[2]: turning OSS repos into a modular cookbook with structured "skills" that point to exact details for reliable remixing and porting. SaaS companies are forever beholden to raising their market cap, even in solved spaces like cart, payment processing, and CRMs. Most businesses run on CRUD apps anyway, and if your core app exposes an API, you can build any customization you need on top of it. People here discounting how valuable it is for a business to have the software that runs their business on a tech stack they understand and something they truly own. [0] https://github.com/twentyhq/twenty [1] https://github.com/medusajs/medusa [2] https://opensource.builders
In AI is killing B2B SaaS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.