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, 3:59:04 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

12 sources
hzia·Aug 7, 2023Submission

Launch HN: GitStart (YC S19) – Remote junior devs working on production PRs

Hi HN, I’m Hamza from GitStart (https://gitstart.com/). We’re building a service for engineering teams to assign tickets and get back PRs. Here’s a video of how it works: https://www.loom.com/share/61d46a5b07e04b45a51af2a5008ee173 We recruit devs who want to grow from remote countries, to work full-time on these tickets and review each other’s PRs. For tech teams it’s pay as you go, and they only pay if they merge the PRs (we pay our devs a base regardless). GitStart is very personal to me because I struggled myself to start my career as a junior dev. Being born in Pakistan made it super hard to find my first remote job. Things changed with Google Summer of Code, which was the first time I got paid to contribute to a large production codebase. When I became a staff engineer, I started mentoring junior devs on their solo projects. I then
Read the rest
realized what they really needed was production code experience, so I started sending them tickets from my backlog to grow them through code reviews. I also paid them for it. They learned a lot and I got a lot done, which started GitStart. That’s why, in the description above, we say “devs who want to grow”. This is key to what we do—we are not just a body shop or middleman, and we don’t charge by the hour. We provide useful mentorship to junior devs. We want to be a meaningful part of their career path. Our thesis (to use that slightly pretentious word) is that the economics work better this way as well. There is a lot of junior dev talent in these countries whose potential will bever be realized by hourly piecework. What’s needed are longer term relationships and work engagements, over the course of which a junior dev can learn and grow on a large production codebase. Much of this has to do with learning the culture of effective tech teams. On the other side, effective tech teams don’t want hourly piecework either. Clients tell us they love having developers dedicated to their project, becoming more familiar with the code over time. This is the way for value to be maximized on both sides. A number of commercial open source repos already use us, so you can check out some of the PRs created by GitStart here: Cal.com: https://github.com/calcom/cal.com/pulls?q=is%3Apr+author%3Ag... SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a... StoryBooks: https://github.com/storybookjs/storybook/pulls?q=is%3Apr+aut... Strapi: https://github.com/strapi/strapi/pulls?q=is%3Aclosed+is%3Apr... Supabase: https://github.com/supabase/supabase/pulls?q=is%3Apr+author%... Twenty: https://github.com/twentyhq/twenty/pulls?q=is%3Apr+author%3A... Our main technical challenge has been securing code sharing. One solution was building GitSlice, which enables creating sub-repos that sync with the upstream repo. When GitStart devs create PRs on the platform, GitSlice syncs them upstream while pulling back CI/CD checks and review comments. This enables our devs to contribute with limited codebase access. To prevent slices from breaking, we verify they run within a docker container, which also enables us to build review environments. Fun fact: we managed to support native iOS and Android codebases by building and running them on appetize.io instead of docker. There have been countless attempts at this space so we would love to hear your feedback on how we approached this problem or your past experiences working with junior devs in this way. We look forward to a good conversation!
235 points · Open discussion

Show HN: Open-Source Favicon Provider

Hey HN, We couldn’t find a reliable favicon provider for our CRM [1]. There are existing solutions (FaviconKit, Google faviconV2, ...) but we have faced issues with all of them: rate-limiting, down-time, inconsistent icon size. We were looking for a solution that is: 1) reliable: no down-time ; 2) accurate: request a specific icon size to optimize for user bandwidth ; 3) high-quality: that provides the highest resolution icon available for a given requested size ; 4) open-source: this is a common need and a simple problem to solve: an open solution should exist and anybody should be able to contribute or to host it. Technical details: Here is the source code: https://github.com/twentyhq/favicon. The way it works is very simple. We have implemented a few strategies to fetch favicons: get favicon from html meta/link tags, call Google Favico
Read the rest
n API. Then we retrieve the image and store it into S3. The next time someone asks for the image it is usually served from our CDN cache directly. If not, then it’s pulled from S3. Cloud Hosting: We are hosting a server on favicon.twenty.com. We will be using it to power Twenty CRM, so it will be maintained up and running for our own needs. Feel free to use it by directly by embedding images like this: https://favicon.twenty.com/google.com or https://favicon.twenty.com/google.com/64 [1] https://github.com/twentyhq/twenty
14 points · Open discussion
iFelix·Jul 19, 2023Submission

Launch HN: Twenty.com (YC S23) – Open-source CRM

Hello HN, Seven years ago, I complained about Salesforce on HN. Somebody said: "one day, someone will do better". That stuck and today we're trying to be that “someone” with my co-founders Thomas (design) and Charles (eng like me). Our company is called Twenty and our repo is here: https://github.com/twentyhq/twenty We want to fix two issues: most CRMs aren't enjoyable to use and they often clash with engineering teams. YC encouraged us to launch early. What you see now is about two months' worth of feature development. Our tool only does a small part of what big CRM players offer, but we focused on providing a great user experience on the basics, instead of spreading ourselves thin across a vast range of features and delivering them half-heartedly. Plus, we've found that many small companies like the product as it is because they don't n
Read the rest
eed all the complex stuff. Once we have covered the basics, we’ll soon be working on three big features: - Moving to a robust metadata-driven architecture; - Providing innovating ways to extend the CRM with Typescript; - Making it easy to connect data sources, and fetch data in real-time like in BI tools. The startup world is littered with ghosts of so-called "Salesforce killers", so we know it sounds naive to pitch ourselves in a similar way. But we think that if someone ends up changing this market, it will most likely be through a community-led effort. And there hasn’t really been any serious attempt to start a great new open source CRM in the last decade. Twenty is built with Typescript, React, and NestJS with GraphQL, and licensed under AGPL. We plan to make money by offering a hosted version. Our docs are here: https://docs.twenty.com. Try on cloud: https://app.twenty.com. Dev setup and demo: https://www.loom.com/share/7b20b44d8d5146fea8923183511bb818 (Loom said they couldn’t provide a transcript because they don’t support “language other than english” haha... apologies in advance!) We’re very eager to get your feedback as we haven’t launched anywhere before this post. What's your CRM story? What should we prioritize next?
415 points · Open discussion

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.