localstack/lstk has 41 GitHub stars and 8 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 20:18 UTC. Last push 2026-11-10.
What you can do
- Start / stop / status / logs β manage the full LocalStack emulator lifecycle with a single command
- Interactive TUI β a Bubble Tea-powered terminal UI in interactive terminals, plain output for CI/CD and scripting
- Browser-based login β authenticate via browser and store credentials securely in the system keyring, or use LOCALSTACK_AUTH_TOKEN for CI (it takes precedence over stored credentials)
- Snapshots β save, load, and manage emulator state as local files, cloud snapshots, or in your own S3 bucket
Measured star growth
- in 24h
- 0
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
πΎ lstk is a command-line interface for LocalStack built in Go with a modern terminal Ul, and native CLI experience for managing and interacting with LocalStack deployments.
Developer ToolsREADME.md
Originallstk
A command-line interface for LocalStack. Built in Go with a modern terminal UI and native CLI experience for managing and interacting with LocalStack deployments. πΎ
npm install -g @localstack/lstk
See Installation for other install methods.
Prerequisites
- A Docker-API-compatible container engine β Docker, Rancher Desktop, Colima, OrbStack, Lima, and Podman are all auto-detected; see container runtimes for details.
- LocalStack account β required for credentials, the CLI will guide you through authentication.
Installation
Homebrew (macOS / Linux)
brew install localstack/tap/lstk
npm
npm install -g @localstack/lstk
Binaries
Pre-built binaries are also available from GitHub Releases. π¦
Quick Start
lstk
Running lstk will automatically handle authentication, configuration, and container setup, then start LocalStack. On the first interactive run, it also prompts you to pick which emulator to run (AWS, Azure, or Snowflake) and remembers your choice.
Features
- Start / stop / status / logs β manage the full LocalStack emulator lifecycle with a single command
- Interactive TUI β a Bubble Tea-powered terminal UI in interactive terminals, plain output for CI/CD and scripting
- Browser-based login β authenticate via browser and store credentials securely in the system keyring, or use
LOCALSTACK_AUTH_TOKENfor CI (it takes precedence over stored credentials) - Snapshots β save, load, and manage emulator state as local files, cloud snapshots, or in your own S3 bucket
- Cloud CLI proxies β run
aws,az,terraform,cdk, andsamcommands against LocalStack with the endpoint, credentials, and region pre-configured - Target an external emulator β pass
--endpoint-url <url>(or setLSTK_ENDPOINT_URL) to point most commands at an already-running LocalStack instance β docker compose, host-network mode, CI, a different machine, or a cloud-hosted ephemeral instance (https://is supported) β instead of one lstk manages locally - Extensions β Git-style
lstk-<name>executables extend the CLI with new commands; see extension authoring - Self-update β
lstk updatechecks for and installs the latest release - Structured JSON output β pass
--jsonto a supported command for a machine-readable envelope instead of formatted text; see structured output
For the full command reference, configuration options, environment variables, and troubleshooting, see the lstk documentation.
Participating
lstk is developed by the LocalStack team. You can read the source, build it, and fork it freely β but we don't accept pull requests from outside collaborators.
The lstk core is licensed under Apache 2.0. Certain bundled first-party extensions, including doctor and deploy, are proprietary and are not licensed under Apache 2.0. See LICENSE for the core's terms; the THIRD_PARTY_NOTICES.txt file shipped with every download lists the open-source components it includes.
The best way to participate is to open a well-formed issue. A bug report we can reproduce is worth more to us than a patch, because it captures the part we can't discover ourselves. CONTRIBUTING.md explains what to include in bug reports and feature requests.