# Serverless Cells **URL:** \ **Category:** Show and tell\ **Created:** [January 21, 2021, 11:40am UTC](https://talk.observablehq.com/t/serverless-cells/4491 "2021-01-21T11:40:50Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![tomlarkworthy](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tomlarkworthy/32/5940_2.png) [@tomlarkworthy](https://talk.observablehq.com/u/tomlarkworthy)\ **Post date:** [January 21, 2021, 11:40am UTC](https://talk.observablehq.com/t/serverless-cells/4491/1 "2021-01-21T11:40:50Z")
Serverless cells are http endpoints that read a notebook when called and run the executable code within. This has a few nice properties: - API endpoints are not a black box, you can see what code is running before sending data to it, lowering the risk of data shenanigans that is too common these days. - You can fork your own serverside implementation of an API service using Observable notebook features. - You can program backend services using front end technology - You can learn how others approach backend programming from tangible, live implementations. - You can distribute work and exploit parallelism. - Its faster to redeploy code than other Function-as-a-services Currently live at > **[Serverless Cells](https://observablehq.com/@tomlarkworthy/serverless-cells)** > > Serverless cells connect a URL to a notebook sourcecode cell. When the URL is called, the latest notebook is fetched from the public internet and run in a private environment using headless browser. You can figure out what code will be run, in... but I expect I will move it to > **[Observable](https://observablehq.com/@endpointservices/serverless-cells)** > > Explore and visualize data. Share and publish your insights. Discover and be inspired. soon. --- _[View the full topic](https://talk.observablehq.com/t/serverless-cells/4491)._