# Elements and Serverless Platforms

**URL:** <https://forums.realmacsoftware.com/t/elements-and-serverless-platforms/45838>\
**Category:** RapidWeaver Elements\
**Created:** [January 7, 2025, 1:15pm UTC](https://forums.realmacsoftware.com/t/elements-and-serverless-platforms/45838 "2025-01-07T13:15:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon68150607](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@anon68150607](https://forums.realmacsoftware.com/u/anon68150607)\
**Post date:** [January 7, 2025, 1:15pm UTC](https://forums.realmacsoftware.com/t/elements-and-serverless-platforms/45838/1 "2025-01-07T13:15:45Z")

</div>

Over the past few years we’ve seen the rise of ‘serverless’ (aka ‘cloud’) platforms (such as [Cloudflare Pages](https://pages.cloudflare.com), [AWS Amplify](https://aws.amazon.com/amplify/), [Google Cloud](https://cloud.google.com/?hl=en), and [GitHub Pages](https://pages.github.com), etc) become increasingly common due in part to their attractive and competitive pricing (often free for smaller sites), excellent performance (often paired with a CDN), complementary services (functions, streaming, image conversion/optimization, etc), and complete lack of server management.

Seeing as Elements is billed as _a modern web design tool_, it would be fantastic to see serverless workflows (deploy/publish[1]) and features (functions, headers, redirects, etc) supported directly within Elements.

[1] Sites on these platforms are often deployed (aka published) via GitHub instead of (S)FTP. While these workflows may be slightly more complex to set-up _(FTP can also be a massive pain)_ they do provide additional benefits such as automatically deploying to CDNs around the world (better performance), as well as the ability to quickly and easily ‘roll back’ a site to a previous version should the need arise.

If these capabilities are of interest to you, please consider adding your voice to [the feature request](https://elements.nolt.io/32). 🙂