LocalStack is ephemeral, so when you stop and restart it, all data is lost. You can use certain features to save the state & load it back when you restart LocalStack. This includes saving the local state for S3 buckets, DynamoDB tables, RDS databases and more. In this video, we explore three mechanisms that allow you to save state in LocalStack: persistence, state export and import, and Cloud Pods.

So many of the challenges that slow down software development stem from the fact that early-stage dev & test cycles are performed in cloud environments.
Local cloud development removes these challenges.
By simulating AWS application behavior in a local container, the local cloud enables developers and agents to validate the security, quality, and reliability of their applications faster and more effectively than they can on the cloud.

Silvio and Carole introduce lstk, LocalStack's next-generation CLI built from scratch in Go. They explain why the team rebuilt the CLI, walk through its key features — zero-config startup, seamless browser-based authentication, and a rich interactive TUI that surfaces real-time progress and actionable errors — and demo how lstk gets you from install to a running emulator in seconds. They also dive into the architecture behind lstk and how it is designed to support multiple emulators, flexible runtimes, and deep integrations with CI pipelines and IDEs.

Cloud-first development kills your inner dev loop. There's a better way. TypeDB on AWS is powerful — Lambda functions querying complex relationship hierarchies, recursive schema functions resolving transitive memberships, all without application logic. But iterating on schemas and queries in the cloud is slow and expensive. Harsh Mishra introduces the TypeDB extension for LocalStack: run a fully functional TypeDB server inside your local AWS environment and connect your app exactly as you would in production. Faster iteration, zero unnecessary spend.