<aside> ℹ️ Here you'll understand in more detail what our system architecture looks like

</aside>

Our Thinking

Collective aims to provide the Saas to onpower all our collectives. As Collective scales to become a complex Saas, we will look for reliability and scalability to keep our users happy.

Thus, to iterate fast and be reliable, we try to use as many good Saas that can prevent us to re-invent the wheel (AWS for hosting, Datadog for monitoring, Forest Admin for the admin)

Key Components

Architecture

Our app currently follows a simple classical architecture. We will look in the future to integrate in a resilient way with many third party APIs in our backend to automate the processes of our platform (Docusign or similar for eSignature, Plaid, Swan or similar for banking integrations, ...)

Note: Our backend is already designed with a micro service architecture in mind in order for us to scale as we grow.

Rationale behind our choices:

• Typescript, React and NestJs are the most trendy tech in the Javascript ecosystem - they allow us to recruit easily as many engineers have these skills - and they are proven at scale as many big companies uses them (Netflix, Twitter, ...)
• AWS usage is a pragmatic, most developpers worked with this cloud and it is the most famous and reliable
• Forest Admin is a Saas platform allowing us to build in a fast and reliable way an admin, without having to take care of the UI parts, the Role based access, and much more. This is once again a choice for reliability and scalability.
• Sendgrid is our mailing platform, that we use mainly for mail notifications to our users. Its powerful templating features and easy API are the reason we chose this Saas.

Technologies