# Serverless Discourse

**URL:** <https://meta.discourse.org/t/serverless-discourse/103726>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [December 7, 2018, 7:37pm UTC](https://meta.discourse.org/t/serverless-discourse/103726 "2018-12-07T19:37:04Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rootsh3ll](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rootsh3ll/32/119507_2.png) [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)\
**Post date:** [December 7, 2018, 7:37pm UTC](https://meta.discourse.org/t/serverless-discourse/103726/1 "2018-12-07T19:37:04Z")

</div>

I am quite new to this buzzword “serverless”.

All that I understand is that at minimum you need one server for any deployment. In serverless you just don’t have to manage the server side of things and only focus on code development.

Since Discourse is a SaaS, I wanted to know if it’s possible for Discourse to be run as serverless application?

Like on AWS Lambda? If yes what are the benefits over running on normal instances.  
performance? bandwidth? cost?

---

_[View the full topic](https://meta.discourse.org/t/serverless-discourse/103726)._