Main difference is your functions get deployed into your AWS account. This means lots of things like: console.logs go to Cloudwatch. Means you can interact with things like DynamoDB and S3 without making AWS credentials for each function. Instead you can just define what permissions you want each function to have in a RiseFunction config file. Vercel functions are triggered via hitting an http endpoint. If you instead deploy your function in your AWS account, u can trigger it by http, or by an AWS EventBridge event, can slot this function into an AWS Step Function workflow, have it triggered by AWS CodePipeline CICD step, triggered by AWS S3, etc.... So if you are using other AWS services, I would use Rise Functions, Serverless Framework, or arc.codes over Vercel
Cool stuff... however is this limited to javascript? Also how is this different from vercel functions?
Main difference is your functions get deployed into your AWS account. This means lots of things like: console.logs go to Cloudwatch. Means you can interact with things like DynamoDB and S3 without making AWS credentials for each function. Instead you can just define what permissions you want each function to have in a RiseFunction config file. Vercel functions are triggered via hitting an http endpoint. If you instead deploy your function in your AWS account, u can trigger it by http, or by an AWS EventBridge event, can slot this function into an AWS Step Function workflow, have it triggered by AWS CodePipeline CICD step, triggered by AWS S3, etc....
So if you are using other AWS services, I would use Rise Functions, Serverless Framework, or arc.codes over Vercel
Rise Functions is JS only