// the find
apex/up
Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.
Up wraps AWS Lambda + API Gateway into a Heroku-like deploy experience: run `up` in any directory with an HTTP server and it handles the Lambda packaging, API Gateway config, and CloudFormation stack. Targets solo developers and small teams who want Lambda's economics without writing CloudFormation. Last meaningful commit was early 2024 and the project is effectively in maintenance mode.
The proxy shim approach is clever — it intercepts standard HTTP traffic and translates to Lambda's event format, so you deploy any existing Node/Go/Python HTTP server unchanged. The middleware chain (gzip, CORS, error pages, static files, redirects) is implemented as composable Go http.Handler wrappers with solid test coverage. Built-in log querying with a real query parser (PEG grammar in internal/logs/parser) is a genuinely useful operational tool that most similar projects skip entirely. CloudFormation stack management is abstracted cleanly enough that the deploy/teardown cycle is reliable and idempotent.
The project is abandoned in practice — no active maintainer, issues pile up unanswered, and the Pro subscription (billing, teams, encrypted env vars) is through apex.sh which is also gone. AWS Lambda runtimes have moved on: Crystal and Clojure support were never first-class and are effectively broken. The CloudFormation stack it generates is opinionated and inflexible — no VPC support, no EFS, no container image lambdas — so you'll hit a wall the moment you need anything beyond the basic HTTP-app pattern. There is no CDK or Terraform equivalent output, making it hard to incrementally migrate off when you outgrow it.