Stakpak Adds /Init Scan, Knowledge Store, and Extension

In Short

Stakpak shipped three updates aimed at reducing hands-on infrastructure troubleshooting. The release includes a new /init command, a Knowledge Store, and a browser extension.

What Happened

On June 3, 2026, Stakpak shared a product changelog focused on how engineers use the platform in production.

First is /init, a command that scans your infrastructure, meaning your cloud accounts, clusters (groups of servers that run apps together), and configuration files. Stakpak says it detects reachable systems and integrations, then flags risk areas like permissions (who can access what), stateful services (systems that store data and cannot be restarted casually), drift (when real setup differs from your saved configuration), and exposure (services reachable from the public internet). The tool also generates recommended schedules and guardrails, which are automated checks and rules, and creates an Apps.md file.

After /init, Stakpak prompts users to enable Autopilot for continuous monitoring, which means it keeps checking for changes and risks over time.

Second is the Stakpak Browser Extension. It lets Stakpak use an engineer’s existing browser session, navigate pages, click, and type via simple CLI commands. The company says the feature is designed to help debug dashboards and use the AWS Management Console with full auditability, meaning actions are logged so teams can review what happened.

Third is Knowledge Store, described as a persistent operational memory layer. It lets users save, search, update, and remove operational knowledge across sessions using stakpak ak. In plain terms, it is a shared memory for infrastructure context like discoveries, runbooks (step by step fix guides), troubleshooting notes, and architecture decisions.

Why It Matters

For African engineering teams running lean DevOps, time spent chasing outages and configuration issues is expensive. Automated infrastructure scanning and risk analysis can surface common issues earlier, before they become incidents.

A persistent knowledge store can also reduce reliance on tribal knowledge, where only one person knows how production works. The browser extension points to a workflow where command line automation and web console actions are combined, which may help teams move faster during incident response and post-incident reviews.