[Feature] Serverless setup #1819

Closed
opened 2026-02-28 19:55:17 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @alshdavid on GitHub (Feb 4, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Hi all,

I'd love it if Actual had a serverless hosting option. The benefits of this would be:

  • Actual, being a personal finance application, is by nature a low traffic application. It would likely be free to host serverlessly for 99.99% of users.
  • Eliminates hosting costs for users and make it more resilient to VPS migrations/maintenance.
  • While docker compose is simple, https certificates and reverse proxies makes it (arguably) easier to deploy as a serverless application as this could be streamlined within a Terraform or Cloudformation script

Describe your ideal solution to this problem

Provide a terraform or cloudformation script to enable deploying Actual as a serverless service. Notable options include:

In addition, https can be automatically provided by

  • Cloudfront
  • Cloudflare proxy

Managed/external authentication could be provided by

I have had success in the past writing an adapter for Nodejs's express and node:http that enables the use of the same http handler syntax to be used for a hosted server and serverless configuration.

Teaching and learning

I don't know if AWS has the ability to deploy infrastructure to AWS on behalf of an AWS account (like having a button on the Actual homepage that says "Click here to deploy to AWS").

However a few screenshots showing AWS console sign in, navigating to cloudformation, pasting in the cloudformation script and hitting deploy should suffice as it's straightforward enough.

e.g.

  1. Go to CloudFormation
Image
  1. Create stack with new resources
Image
  1. Sync from Git or paste in CF script
Image
  1. Deploy and use Actual from the Cloudfront URL
Originally created by @alshdavid on GitHub (Feb 4, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Hi all, I'd love it if Actual had a serverless hosting option. The benefits of this would be: - Actual, being a personal finance application, is by nature a low traffic application. It would likely be free to host serverlessly for 99.99% of users. - Eliminates hosting costs for users and make it more resilient to VPS migrations/maintenance. - While docker compose is simple, https certificates and reverse proxies makes it (arguably) easier to deploy as a serverless application as this could be streamlined within a Terraform or Cloudformation script ### Describe your ideal solution to this problem Provide a terraform or cloudformation script to enable deploying Actual as a serverless service. Notable options include: - [AWS Lambda](https://aws.amazon.com/lambda/) - [AWS Aurora Serverless V2 (PSQL)](https://aws.amazon.com/rds/aurora/serverless/) - [Cloudflare workers](https://workers.cloudflare.com/) - [Cloudflare D1 (SQLite)](https://developers.cloudflare.com/d1/) In addition, https can be automatically provided by - Cloudfront - Cloudflare proxy Managed/external authentication could be provided by - [Cognito hosted sign-in/sign-up](https://cloudcompiled.com/2021/05/08/aws-cognito-hosted-ui/) can be used I have had success in the past writing an adapter for Nodejs's `express` and `node:http` that enables the use of the same http handler syntax to be used for a hosted server and serverless configuration. ### Teaching and learning I don't know if AWS has the ability to deploy infrastructure to AWS on behalf of an AWS account (like having a button on the Actual homepage that says "Click here to deploy to AWS"). However a few screenshots showing AWS console sign in, navigating to cloudformation, pasting in the cloudformation script and hitting deploy should suffice as it's straightforward enough. e.g. 1) Go to CloudFormation <img width="946" alt="Image" src="https://github.com/user-attachments/assets/a908b494-403f-46ed-9d24-b48e81268ad8" /> 2) Create stack with new resources <img width="320" alt="Image" src="https://github.com/user-attachments/assets/7e8af609-c893-40f7-8f13-667065d2b85f" /> 3) Sync from Git or paste in CF script <img width="965" alt="Image" src="https://github.com/user-attachments/assets/3ab442fd-4ddc-470c-a333-a0a64e6fb276" /> 4) Deploy and use Actual from the Cloudfront URL
GiteaMirror added the needs votesfeature labels 2026-02-28 19:55:17 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 4, 2025):

Thanks for sharing your idea!

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Feb 4, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Author
Owner

@Landaman commented on GitHub (Dec 22, 2025):

I put some time in and was able to make this work using SST (basically Pulumi). The hard part about making this cost effective is figuring out networking with IPv6 only, since if you pay for IPv4 networking this doesn't make any sense cost wise vs using something like Fly. (Normally lambdas get free internet networking, but we need a EFS which means a VPC, and VPCs don't automatically get external networking from Lambda).

It works though!

Stack is:

  • Lambda to run migrations
  • Lambda per endpoint
  • EFS volume to store SQLite stuff
  • S3 to host the static frontend
  • CloudFront for routing/https

Feel free to check out my fork if you're curious. Some small refactoring to the sync server to let ESBuild work and to let us package for lambda, but pretty much everything lives in sst.config.ts.

Basically all you pay for in this setup is the S3 costs to store the Lambda source and static files. Should be a couple cents a month, but no promises since it's AWS and can be variable. Especially if I made a mistake somewhere (or you get hit with a botnet or something). I'm not convinced this is a good one-click option due to that, but it's cool if you're comfortable with it!

@Landaman commented on GitHub (Dec 22, 2025): I put some time in and was able to make this work using SST (basically Pulumi). The hard part about making this cost effective is figuring out networking with IPv6 only, since if you pay for IPv4 networking this doesn't make any sense cost wise vs using something like Fly. (Normally lambdas get free internet networking, but we need a EFS which means a VPC, and VPCs don't automatically get external networking from Lambda). It works though! Stack is: - Lambda to run migrations - Lambda per endpoint - EFS volume to store SQLite stuff - S3 to host the static frontend - CloudFront for routing/https Feel free to check out my [fork](https://github.com/landaman/actual-sst) if you're curious. Some small refactoring to the sync server to let ESBuild work and to let us package for lambda, but pretty much everything lives in sst.config.ts. Basically all you pay for in this setup is the S3 costs to store the Lambda source and static files. Should be a couple cents a month, but no promises since it's AWS and can be variable. Especially if I made a mistake somewhere (or you get hit with a botnet or something). I'm not convinced this is a good one-click option due to that, but it's cool if you're comfortable with it!
Author
Owner

@alshdavid commented on GitHub (Dec 22, 2025):

You're kidding. That's amazing, nice work! Checking it out

@alshdavid commented on GitHub (Dec 22, 2025): You're kidding. That's amazing, nice work! Checking it out
Author
Owner

@alshdavid commented on GitHub (Dec 22, 2025):

EFS volume to store SQLite stuff

Turso has a free serverless SQLite solution. It's outside of AWS but still a great product

@alshdavid commented on GitHub (Dec 22, 2025): > EFS volume to store SQLite stuff Turso has a free serverless SQLite solution. It's outside of AWS but still a great product
Author
Owner

@Landaman commented on GitHub (Dec 23, 2025):

Glad someone will get some use out of :)

Turso and D1 are both great options, but I think it'll be more work to get them working. I didn't dig into the sync-server internals very much, but I know there are multiple sqlite files, potentially some other types of files. Also the encryption would be tricky. EFS supports the use case pretty well, it's just the edges of VPC that are annoying :(

@Landaman commented on GitHub (Dec 23, 2025): Glad someone will get some use out of :) Turso and D1 are both great options, but I think it'll be more work to get them working. I didn't dig into the sync-server internals very much, but I know there are multiple sqlite files, potentially some other types of files. Also the encryption would be tricky. EFS supports the use case pretty well, it's just the edges of VPC that are annoying :(
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1819