Skip to main content

​
What is runnabl?

runnabl is a CLI-first, AWS-native deployment tool that lets you manage application infrastructure declaratively without drift, state files, or manual reconciliation. It enables you to declare high-level ideas like services or databases and deploy them within AWS quickly.
  • services long-running ECS tasks
  • workers event-driven async lambdas
  • databases managed postgres
  • storage s3 buckets
  • …and more
runnabl creates and manages the complicated parts of AWS using best practices, and stays out of the way when you need to tune your setup.

Start here

Follow our three step quickstart guide.

​
Why runnabl?

runnabl exists to make deploying and managing your applications on AWS simple, predictable, andsafe . Unlike other tools that try to track every detail of your infrastructure, runnabl focuses on minimal config: the things your app actually needs to run. This approach gives you…
  • No drift, no state files
    runnabl never stores local state or tries to reconcile every property of your resources. It always queries AWS live, ensuring your infrastructure matches your declared intent—nothing more, nothing less.
  • Safe, idempotent operations
    You can runnabl deploy as many times as you like. runnabl will create missing resources, configure required settings, and leave everything else untouched. Manual changes in AWS are respected unless they break your declared settings.
  • Focused abstractions
    runnabl exposes high-level, meaningful constructs like services, workers, databases, storage, and secrets. You don’t need to worry about VPCs, subnets, or IAM policies unless you want to - runnabl handles the best practices automatically.
  • Eject Anytime – You are never locked in.
    Runnabl manages only the minimal invariants your app needs to run, so you can leave at any time and take full control of your AWS infrastructure. No hidden state, no opaque tooling—everything is visible and editable (and reasonably named) in your account.
In short, Runnabl helps you declare what your app needs and forget the rest—so you can focus on building features instead of managing infrastructure.

​
Why Runnabl Feels Like a PaaS

runnabl gives you the ease and confidence of a Platform-as-a-Service without locking you into a proprietary environment. You don’t think about EC2 instances, subnets, or IAM policies. You just declare what your app needs: services, workers, databases, storage, and secrets. It handles all the heavy lifting for you: it ensures your services run, your workers are triggered, your databases exist, and your S3 buckets are accessible. It wires together networking, logging, security, and credentials in AWS automatically, so you can focus on shipping features instead of managing infrastructure. Like a PaaS, you get:
  • Instant deploys on the command line or CI
  • Automatic HTTPS with your own domain
  • Secure storage with s3 and postgres
  • Secrets management with zero boilerplate
But unlike a traditional PaaS, you retain full control of your AWS environment, can tune your setup anytime, and can use the full range of AWS services directly. Runnabl is essentially a lightweight, safe layer on top of AWS that gives you the productivity of a PaaS without taking ownership of your cloud. Best of all, you get the simplicity and productivity of a PaaS without the 10x markup. runnabl lets you run on AWS directly, so you only pay for the resources you actually use.