Apex Up deploys infinitely scalable serverless apps, APIs, and static websites in seconds, so you can get back to working on what makes your product unique. Up focuses on deploying “vanilla” HTTP servers so there’s nothing new to learn, just develop with your favorite existing frameworks such as Express, Koa, Django, Golang's stdlib or others — just run `up` and your serverless application is ready to go.
Up is free open-source, with its source available on GitHub. Up Pro is available for commercial use or projects which need additional features such as alerting, securely encrypted environment variables, active warming and more.
Up packs a lot of functionality into a small and user-friendly package — deploying apps and APIs to your own private AWS account doesn't get much easier than this, check out some of the features available.
Deploy applications with a single command, making it easy for the entire team.
Scale infinitely, with no code or configuration changes needed, just deploy the app and you're done!
The days of paying extra for SSL certificates are over, Up provisions free SSL certs on your behalf with AWS ACM.
Don't wait minutes to build Docker containers and fetch dependencies, deploy most applications in seconds.
Don't make your customers wait for cold start times, most cold starts are well under 500ms.
Rich structured JSON log query support help you track down issues quickly, for only $0.5/GB with 5GB/mo free.
Up deploys to your private AWS account, isolating from multi-tenant systems for stability and security.
Up supports your favorite runtimes including Node.js 10.x, Golang, Python, Crystal, static sites and more.
Deploys made with Up are immutable, you can roll back to previous versions in an instant.
Up makes it easy to deploy single page applications by utilizing pattern-matched redirection and rewriting rules.
Up provides declarative built-in middleware for logging, CORS, redirects, rewrites, minification and more.
Define resources such as DNS records, alerts, and more in configuration and previewing changes before applying them.
Individual errors thrown during a request are isolated in containers, ensuring no other customers are impacted by a crash or failure.
Up Pro integrates with Git to provide insight into who, and when changes were deployed to a stage.
Up Pro lets you configure alerts for errors and other metrics, notifying the team via email, Slack, and SMS.
Up Pro integrates with Git to provide insight into who, and when changes were deployed to a stage.
Up Pro provides instant rollbacks to a previous deployment, using a Git SHA or tag.
Up Pro provides encrypted environment variables, keep secrets such as database connection credentials safe.
Up is free for side projects and trialing, give it a try and upgrade to Up Pro for additional features and commercial use. Up Pro's subscription allows for unlimited use within your organization, use it for one application or thousands.
Subscribe to ProFree | Pro | |
Applications
The number of applications which can be created.
|
∞ | ∞ |
Deployments
The number of deployments per application.
|
∞ | ∞ |
Team Members
The number of team members.
|
∞ | ∞ |
Encrypted environment
Encrypted environment variables for securely storing secrets.
|
- | ✓ |
Instant rollbacks
Roll-back to a previous version via Git tag or SHA instantly.
|
- | ✓ |
Active warming
Proactively "warm" the Lambda functions to ensure responsiveness.
|
- | ✓ |
Deployment log
See which Git commits were deployed to a particular stage, and when.
|
- | ✓ |
Alerting
Configure alerts and notify the team of issues.
|
- | ✓ |
0/mo | 20/mo |
View the documentation for a guide on subscribing to Up Pro. Commercial use requires an Up Pro subscription for the duration of its use in production.
Up is a self-hosted service, letting you deploy applications to your own AWS account for isolation, security, and longevity — don’t worry about a startup going out of business.
Most of the AWS Lambda based tools are function-oriented, while Up abstracts this away entirely. Up does not use framework “shims”, the servers that you run using Up are regular HTTP servers and require no code changes for Lambda compatibility.
Up keeps your apps and APIs portable, makes testing them locally easier, and prevents vendor lock-in. The Lambda support for Up is simply an implementation detail, you are not coupled to API Gateway or Lambda. Up uses the API Gateway proxy mode to send all requests (regardless of path or method) to your application.
If you’re looking to manage function-level event processing pipelines, Apex or Serverless are likely better candidates, however if you’re creating applications, apis, micro services, or websites, Up is built for you.
You might be thinking this defeats the purpose of Lambda, however most people just want to use the tools they know and love. Up lets you be productive developing locally as you normally would, Lambda for hosting is only an implementation detail.
With Up you can use any Python, Node, Go, or Java framework you’d normally use to develop, and deploy with a single command, while maintaining the cost effectiveness, self-healing, and scaling capabilities of Lambda.
AWS API Gateway provides 1 million free requests per month, so there’s a good chance you won’t have to pay anything at all. Beyond that view the AWS Pricing for more information.
Up scales to fit your traffic on-demand, you don’t have to do anything beyond deploying your code. There’s no restriction on the number of concurrent instances, apps, custom domains and so on.
With a 512mb Lambda function Up introduces an average of around 500µs (microseconds) per request.
Up uses AWS API Gateway, which imposes the stage base paths. Currently there is no way to remove them, however when you use custom domains these paths are not present.
This depends on the platform, and with Lambda being the initial platform provided the current answer is no, the server(s) are frozen when inactive and are otherwise “stateless”.
Typically relying on background work in-process is an anti-pattern as it does not scale. Lambda functions combined with CloudWatch scheduled events for example are a good way to handle this kind of work, if you’re looking for a scalable alternative.
You’re not limited to databases from any given platform, such as AWS Provided that the database host provides authentication, you can use anything. See the Wiki for a list of managed & serverless database solutions.