We built Stackery from the ground up to help software development teams harness cloud innovation and bridge the leap from server-centric to serverless applications

Create a cloudside development environment and then bridge it to local development. With the automation of safeguards, best practices, and curated cloudwatch metrics, your serverless confidence will scale like a Lambda.

Set up your development environment

Step away from the whiteboard and configure a deployable architecture in the Stackery Editor. With visual configuration of infrastructure resources and what you already know about API gateways, Database tables, streams, timers, functions, and more you can compose with AWS service resources in minutes. Stackery automatically applies best practices like least priveldge permissions into a CloudFormation template you can edit bi-directionally. Forgot to put RDS inside the VPC? No worries. Fix it or crumple it up and try another stack with just a few clicks.

Develop locally against live cloud resources

You can’t fit AWS on your laptop, but with the Stackery CLI local invoke, you can develop your functions, analyze your code, and iterate in seconds. With a bridge between your resources in the cloud and your local IDE, you’ll be more productive than ever.

Professional environment management

As you add more people, applications, and environments to your pipeline, the number of active stacks running in your AWS accounts will increase. Stackery choreographs the differences in your dev, test, and production environments with namespaced environments, rollback, secrets management and more to save you time and keep everything compliant and clear.

Deploy a prototype architecture, then iterate.

When building on cloud services, a common first step is to compose and deploy an architecture you think makes sense. While it may feel strange to “deploy” first, it’s similar to setting up a development environment on your laptop, the only difference is you are provisioning cloud services instead of localhost. Stackery enables you to choose from 22+ AWS resources to visually configure while learning infrastructure-as-code best practices. Want to use something outside those 20? Everything Stackery helps you build is in open AWS CloudFormation, so anything you can do in CloudFormation, you can do in Stackery. The “Anything resource” is designed just for that. Next, you’ll begin developing functions against those resources.

See all the resource types in our docs.

Build Without Limits - Stackery
The Stackery CLI gives you the ability to build out your application architecture, debug any Lambda, deploy, invoke, and more. It also comes in a VS Code plugin if that's your IDE. When you first get started, you'll save your templates locally and deploy from your laptop.
Plot twist! When you start building with serverless, you should deploy the cloud resources you plan to use to a cloudside dev environment first — before you write your functions. The Stackery Role helps you keep everything deployed properly, namespaced, and organized.
Unless you already have a project you want to add, deploying a stack gives you a set of resources to develop your functions against. Stackery permissions enable us to prepare your dev stack or production-packaged application (and everything in between) with the correct environment parameters and secrets. But to deploy your first stack, you’ll need to have the rights via either the AWS console or the Stackery CLI.
The result of your ideal serverless workflow is simple: focus and happiness, and speed. To achieve this, your development environment should be consistent with production and enable quick iteration of applications. With your existing IDE, the Stackery CLI, and the AWS SAM Local CLI, you’ll have the ability to iterate function code quickly on your laptop against the live cloud resources you deployed in step #3.
Now that you have functions written and your architecture deployed, it’s time to make changes to the resources in your architecture to either
A. Ship your newly developed function code into your cloudside environment.
B. Promote your stack in a test, staging, or production environment.
Stackery keeps all the namespacing and AWS accounts straight so you can rollback, collaborate, use your existing CI/CD system and much more.

3 minutes to start architecting a serverless app

Without Stackery, configuring a VPC is a several hour long processes - even for engineers well versed in YAML. With Stackery, new VPCs or deploying applications into existing VPCs can be done in just a few clicks. Or perhaps you just want to understand how to connect resources to handlers? Seconds. Here are the steps to get your initial cloudside development environment up and running.

Cloudside consistency with local speed

The goal of any development environment is consistency with production and fast iteration of application to keep you focused and happy. With your existing IDE, the Stackery CLI, and the AWS SAM Local CLI you will have the ability to quickly iterate your function code on your laptop against live cloud resources.

A key component of this approach is to query the environment and IAM configuration directly from your cloudside development environment. This avoids the need to keep a local copy of environment variables and other forms of bookkeeping needed to integrate with cloudside services. The result? Consistency between how your code behaves locally and in the cloudside environment. For example, one common debugging headache results from mismatched service to service permissions and configurations between local and cloudside resources. This setup cuts off that entire class of problems.

Learn about local + remote development and alternative approaches

Stackery Application Setup on AWS Lambda

Operate professionally

Stackery’s environment management ensures you have a clear view across your serverless pipeline into which versions of your code and infrastructure are running. By integrating with your existing CI/CD system, your release and test engineering processes can also stay the same. Finally, once in production, you’ll have one-click access to X-Ray traces, Cloudwatch metrics, and logs curated for each service. Want to level up on monitoring? Enforce consistent monitoring policies with cloudwatch and X-Ray out of the box or by adding your Epsagon license key. Interested in other monitoring options? Ping us on the live chat in the corner or drop us a line. And then, of course we are an AWS Advanced Technology Partner.


Stackery is SaaS minus the data. Your code and configurations are deployed into your cloud accounts and stored locally for free accounts or in your git repositories for pro accounts. Have on-premises Git like Github Enterprise, Gitlab, or Bitbucket? We support those, too. Stackery is built on AWS, so we inherit AWS security governance on the infrastructure front. Stackery itself ensures permissions are tightly scoped, production services are logged, and other best practices. If your security teams has questions for us, we’re happy to chat with them in more depth.

Scale Applications with a Single Click - Stackery

Native AWS and Open Tooling

Despite the foundational change from servers to services, the role of most tools in a serverless pipeline is similar. However, none of those tools were built to also manage and configure cloud resources and environments. With Stackery, your existing IDEs, code repositories, and CI/CD systems remain the same while your code, data, and credentials always remain in your systems and infrastructure as code is rendered in standard AWS SAM. No abstractions and plenty of flexibility to handle your build needs.

Begin your journey from tutorial app to "Wow, Thanks!"

Sign up now and experience cloudside development on our free tier. Contact one of our product experts to get started building amazing serverless applications today.

To Top