Viewing profile — charlesTwenty

Hi, I'm Charles and leading the engineering work on Twenty! We've made the bet to invest on a tailored design for our components. Using an existing UI library is a strength to use …

Very nice Readme! What have you used to generate the illustrations? Also, congratulation guys. It looks very interesting and as an engineer I'm always happy to see more open-source…

Hi, I'm one of the main maintainer of Twenty and we have onboarded Gitstart on our codebase a few weeks ago. I can give a feedback on our collaboration so far: 1) Code quality is g…

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: ra…

Interesting feedback! The recommended install is already local (through yarn). The only piece mentioning docker is to provision a Postgres database, which you need to have to run a…

We are unsure about the right license to use, so this is a great feedback. We had a MIT license one week ago that we know that we cannot hold on long term and we felt we were lying…

The pricing is for the cloud version: you can use it for free if you stay under 100 contacts. Self-hosting is completely free!

Thank you!

Yes, as an engineer I am rooting for opensource and to build something that last beyond the company. I also think it will force us to install a good company culture centered around…

Yes! https://app.twenty.com . It's still very early but we are happy to share it and to get feedbacks. We already have a few users that are using it on a daily basis and we are try…

Thank you, we put a lot of effort into providing a good user experience and a good developer experience. Feel free to jump in on Github issues!

+1, thanks for the link

Very interesting, this makes sense, it is definitely a direction we could go into. We are using Postgres and were also considering using 1 schema per tenant.

Thank you, happy to see you on the codebase!

Thank you for the feedback. What you said resonates with me a lot. Standardized APIs: While we are designing Twenty, we have in mind to provide three APIs: a GraphQL API (headless)…

We have mainly chosen to use JS on the frontend and on the backend to lower the learning curve for people that would want to contribute / extend it to their own needs. Then typescr…

A middle ground I've encountered in an ERP system (prophet21 if you're interested) was each table had multiple "CUSTOM_XX" columns that were initially blank. Customers could edit t…

Haha! Yes, fixing it, thank you!

I'm rather worried about having a large table being able to accommodate for any custom object than the fact it is multi-tenant, we could shard by tenant_id quite easily. I might be…

Yes, agree! We try to re-use as much opensource software as possible. One difficulty is that we are also trying to make it as easy as possible to self host the CRM. If we start inc…

Thanks for the feedback! We have been discussing this a lot. Here is one of the option we have in mind for the upcoming months and we would love to know if this could work in your …

That's a very good point. In the early stage, we were thinking about a single tenant architecture which would make this questions way easier. However, I am a strong believer in mul…

We also plan to support CSV import and export

Yes, we are providing a graphql API that you can find "documented" here: https://docs.twenty.com/graphql/ Right now, you need to provide a JWT token that you can get at login or re…

Sure! We want to build something flexible where users can define their own custom objects and fields. We were thinking about leveraging Hasura that's already providing a flexible g…