Get Started
Less Ops More Coding
Stakpak is the Open-source DevOps agent that helps you with securing, deploying, and maintaining production-ready infrastructure.
But what's special about Stakpak?
Built for operations
The most secure agent
It learns from your environment
Open Source & Written in Rust 🦀
Installation
Installing Stakpak is as easy as running one command
curl -sSL https://stakpak.dev/install.sh | sh

Press Y to proceed with installation

Press Y to use Homebrew for installation
Then it will automatically open the browser and check if you are signed in, if not then you will be redirected to sign in/register.

Then you will be redirected to the api key page, and it will be copied automatically and sent to your terminal

No you can close your browser
That's it, we are ready to use Stakpak🥳

Use Cases
Now that we have installed Stakpak, let's take a look at what we can do with it
Containerize Your Apps
Instead of spending hours configuring containers, you can simply ask Stakpak to Dockerize this app
and it would automatically:
Analyze the application structure, language, frameworks, and dependencies
Choose a secure and minimal base image
Generate an optimized multi-stage Dockerfile
Configure Docker Compose for the app and dependent services
Build Docker images with proper tagging and
.dockerignore
Run containers and verify application startup and migrations
Perform health checks and endpoint testing
Clean up unused containers, images, and volumes
Document environment variables, secrets, and deployment instructions
all of that while you are drinking your coffee
Secure Your IAM

Instead of manually reviewing IAM roles and figuring out which ones give more access than they should, just ask Stakpak, and it will:
Analyze existing IAM roles and policies
Flag risky permissions that could expose your environment
Generate least-privilege policies on the fly
Create audit scripts and compliance reports
Analyze Your Cloud Cost
Instead of going between billing dashboards and guessing where money is wasted, just ask Stakpak and it will:
Analyze your cloud usage and spending patterns
Identify idle, overprovisioned, or unused resources
Recommend specific actions to reduce costs
Handle Incidents

Instead of going through logs, alerts, and dashboards to try to figure out what's wrong you can just ask Stakpak and it will:
Quickly identify root causes from your terminal
Suggest and implement fixes to resolve issues faster
Monitor logs, metrics, and dependencies in real time
Document the incident and resolution automatically
Features
Agent Sessions

Review and audit your past agent sessions to understand exactly what your agent did and why.
Each session includes:
Full conversation history
Key checkpoints and decisions
Actions taken and their results
A clear trail for debugging
You can also view the sessions from your terminal by opening stakpak and typing /sessions
Rule Books

Rule Books are how you teach Stakpak agents to follow your way of doing things. Think of them as smart, markdown based SOPs (standard operating procedures), whether it’s how to deploy to production, upgrade infrastructure, or tag resources correctly. Stakpak uses Rule Books to make decisions that align with your team’s standards, not just generic best practices.
There are two types of rule books:
Official Rule Books They are created by the Stakpak team, and they cover common workflows like Dockerization, infrastructure software upgrades, and cloud deployments. They follow industry best practices and are ready to use out of the box.
Your Rule Books Your custom Rule Books define how your team works. From deployment procedures to incident response, Stakpak will follow them step-by-step, just like a teammate would
Memory Blocks

Memory Blocks are reusable pieces of knowledge that your agent learns during sessions.
As you interact with the agent, it automatically extracts useful information like commands, configs, environment details, or error fixes and stores them as memory blocks for future use.
Each memory block includes:
A title and tags for easy search and organization
The content the agent learned (in markdown)
Metadata like source session and timestamp
You can edit and tag memory blocks to improve how agents recall and apply them in future tasks, making your agent smarter over time.
You can also manually ask the agent to memorize the important information at any moment by typing /memorize
and it would automatically extract it from your conversation
Security
Stakpak was built with a security first mindset
Mutual TLS (mTLS)
End-to-end encrypted communication between agent components
Dynamic Secret Redaction

Stakpak agents can interact with secrets like API keys and tokens without ever seeing their actual values. Secrets are redacted at runtime and never exposed in logs or memory.
Warden

Warden acts as a deterministic policy enforcer for every agent action. It inspects, validates, and blocks any destructive or unauthorized operations before they reach your environment.
To start warden open your terminal and write stakpak warden
Secure Password Generation
Generate cryptographically secure passwords with configurable complexity
Privacy Mode
Redacts sensitive data like IP addresses and AWS account IDs
Keyboard Shortcuts

Use
Arrow keys
orTab
to select optionsPress
Esc
to exit the prompt?
for Shortcuts/
for commandsPageUp/Down
orFn + ↑/↓
for fast scroll$
for shell mode↵
to send a messageShift + Enter
orCtrl + J
to insert a newlineCtrl + r
to retryCtrl + C
to quit
Frequently Asked Questions (Q&A)
How to install Stakpak?
To install Stakpak, just run curl -sSL https://stakpak.dev/install.sh | sh
in your terminal
How to update Stakpak?
To update Stakpak to the latest version, just open your terminal and write stakpak update
What is Stakpak Warden?
Stakpak Warden wraps coding agents to apply security policies and limit their capabilities
To turn on Warden, all you need to do is open your terminal and write stakpak warden
How to resume the agent at a specific checkpoint?
To resume the agent at a specific checkpoint, just open your terminal and write stakpak --checkpoint <CHECKPOINT_ID>
Note: replace <CHECKPOINT_ID>
with your checkpoin ID
Last updated