Use cases
Case studies

Why Serverless?

Just like wireless internet has wires somewhere, serverless architectures still have servers somewhere.

What ‘serverless’ really means is that, as a developer you don’t have to think about those servers. You just focus on code.

What makes an application serverless?

These are the 4 key properties of Serverless Applications you should know about

Zero administration

Deploy code without provisioning anything beforehand, or managing anything afterward. There is no concept of a fleet, an instance, or even an operating system. No more bothering the Ops department.


Let your service providers manage the scaling challenges. No need to fire alerts or write scripts to scale up and down. Handle quick bursts of traffic and weekend lulls the same way -- with peace of mind.


Function-as-a-service compute and managed services charged based on usage rather than pre-provisioned capacity. You can have complete resource utilization without paying a cent for idle time. The results? 90% cost-savings over a cloud VM, and the satisfaction of knowing that you never pay for resources you don't use.

Increased velocity

Shorten the loop between having an idea and deploying to production. Because there's less to provision up front and less to manage after deployment, smaller teams can ship more features. It's easier than ever to make your idea live.

Build with the Serverless Framework

At over 25,000 GitHub stars, the open source Serverless Framework is the number one tool for building and deploying serverless applications. It is:


Allowing organizations to prevent data lock-in on a single vendor. Use the Serverless Framework CLI to build and deploy your application to any cloud provider with a consistent experience. The Framework automatically configures cloud vendor settings for you, based on the language you use and the provider you deploy to.


So that developers don’t have to keep rebuilding the wheel. They can build once, use, and reuse Serverless Components to do things like create & manage DynamoDB tables or enable authentication with Auth0. Components are open source, and there is lots of pre-built functionality developers can tap into right away.

Code for your infrastructure

Because Serverless Applications require automation. If you're tying together multiple managed services and functions, you cannot rely on a checklist of manual steps. You should be able to recreate your entire application with a command.

Centered on development experience

We’re engineers, too, and we built a simple, straightforward tool we’d love using. The point of serverless is to make developers more productive; we wanted the Serverless Framework to embody that most of all.

Operate with the Serverless Dashboard

The Serverless Dashboard provides architectural views of your serverless applications. It also exposes logs for metrics, alarms and debugging, and lets you collaborate easily with teammates on development.

The Dashboard, just like our Framework, is vendor-agnostic. Use any provider you want, and use multiple providers at once. We’ll expose everything in a single place.

Integrate with the Serverless Event Gateway

The Event Gateway is a powerful event router, capable of routing event data to serverless functions and other services across clouds. It’s the answer to how organizations can integrate serverless into their existing services and containers, easily hook into other SaaS, and span cloud providers.

With the Event Gateway, you can do things like: easily build FaaS-backed APIs, or use configurable connectors to react to events from data stores like Kafka or Kinesis.

Next Steps

Check out all the different use cases for serverless applications. Take a peek at how the Serverless Framework compares to other software. Talk to us directly on the enterprise contact form

Or if you’re ready, follow our step-by-step guide to start building a Serverless Application with your favorite language.