I am worried about AWS imposing their own political rules on the models. For example, they may impose censorship, or safety requirements. It is hard for me to trust them as a central platform in this ecosystem
+1 Bedrock supports custom model import, though I haven't used it and can't speak to limitations there. Also, this boilerplate provides a solid foundation for any LLM app, whether you use Bedrock or opt for models hosted elsewhere.
CEO here. Candidly, our average deal size is less than $1K. We have not done a 6-figure deal for the Framework. I'm not aware of any mature discussions around a deal this size because most folks are gradually incrementing to V.4, which is the right approach.
I highly recommend you discuss this with us/me. We're small, approachable, flexible, and you've been with us so long we're more motivated than ever to make this work.
You can opt out of the observability features in the Dashboard.
I've been using serverless framework since v1. I'm trying to wrap my head around this idea of credits... Paying per lambda invocation? Why do I need to pay serverless framework per lambda invocation? If I'm not using the dashboard can I opt out? Can I disable that and not have to pay?
1 Lambda invocation = 4 metrics. 4 million Metrics = 1 credit. Credits are $4 each. This comes out to being 20x more expensive than what I pay AWS for lambda invocations (granted, it doesn't include runtime costs).
There is no cost for Lambda invocations with the new Serverless Framework license. Pricing IaC around Lambda invocations does not make sense. Instead, pricing is a fixed fee for each Framework Service Instance (e.g. app) you have.
If you use the Framework's (optional) observability product, pricing is based on Traces and Metrics, like most observability solutions.
Credits are used to pay for these various features.
You love developer tools that help you build more and manage less.
We're working on three big tools and services. You can impact all of them:
• Serverless Cloud - A next-generation Heroku, led by Jeremy Daly.
• Serverless Desktop - A graphical user interface for building serverless applications.
• Serverless Framework CLI - The application framework that started the serverless movement.
Yes, we do this, like other build engines, CI/CD products, and other cloud services. We try to be clear about what's happening and why in this section of the documentation: https://github.com/serverless/components#where-do-components... and we discuss the cloud-based deployment approach elsewhere in the docs.
Further, this is all designed to support and facilitate our upcoming component-scoped permissions, which will significantly reduce required permissions for the Framework, compared to what Serverless Framework Traditional requires.
We'll add more clarity in the docs specifically on credentials and try to make this known upfront.
I’m not sure I’m understanding what’s happening here, I’m using the serverless command line app to deploy a lambda function to AWS from my local terminal. Nowhere in that process is serverless.com required to be involved. Are my AWS credentials being pushed to serverless.com when I do a deploy? If so, how do I disable this? We’re in a regulated industry and serverless.com is not an approved vendor of ours and should not be receiving any of our AWS credentials.
I apologize for the confusion. The original post is misleading and I should have clarified this in my response above (I'm juggling a newborn ATM).
The Serverless Framework open-source experience does not do this. But there are premium features, like Serverless Framework Components (which this post is actually referring to) which do this.
When you use these premium features you must log into the Serverless Framework SaaS offering via your CLI, accept a TOS, etc.
At the same time, we need to make sure our communication on these SaaS offerings and how they work is more clear. With respects to that, we'll collect all of the feedback we can to get this right!
"serverless" is used to describe a new type of cloud infrastructure you can run your apps (Django, Flask, Express) so that they scale automatically and charge only per request, never for idle, at ~$0.000001 per request.
The candid reason developers and Fortune 500s use serverless cloud infrastructure is because they want to build more and manage less.
The "Serverless Framework" is a developer tool that helps developers deploy their apps to serverless cloud infrastructure, without having to be an expert in that type of infrastructure. It makes it easy for developers to deploy Django, Flask, Express apps so that they auto-scale and pay only per request, never for idle.
Here is how you can deploy Express.js in seconds to serverless infrastructure:
Complexity in any form can be lock-in to contractors, eng. teams, vendors, etc.
Make no mistake, serverless cloud services are the greatest building blocks of all time. That doesn't mean you should use all of them, nor use them in the most granular manner.
As always, the architect should make prudent decisions.
