> For the complete documentation index, see [llms.txt](https://serious-people.gitbook.io/serious-amm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://serious-people.gitbook.io/serious-amm/product-overview/system-overview/architecture-summary.md). # Architecture Summary Serious AMM utilizes a distributed architecture built on proven cloud technologies. Our front end leverages Next.js hosted on Vercel, communicating with a NestJS backend on Heroku through standardized REST APIs. This foundation is augmented by Telegram integration for notifications and group management, delivering a responsive and reliable user experience inside and outside the platform. PostgreSQL on Neon provides a secure and scalable database layer, while Firebase handles authentication and user management. This combination enables features like connection pooling, rate limiting, and horizontal scaling, ensuring the platform can handle substantial traffic while maintaining consistent performance. Security and compliance are built into the system's core through Firebase's enterprise-grade encryption and Neon's isolated database instances. The platform implements essential data privacy features, with automated backups, role-based access controls, and self-service data management capabilities. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://serious-people.gitbook.io/serious-amm/product-overview/system-overview/architecture-summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.