Top AI Repos — open-source AI, indexed and scored

Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.

Star history, last 90 days
Date	Stars
2026-07-24	35629
2026-07-25	35644
2026-07-28	35644
2026-07-30	35644
2026-08-06	35644

Star history, last 90 days

Date

Stars

2026-07-24

35629

2026-07-25

35644

2026-07-28

35644

2026-07-30

35644

2026-08-06

35644

<picture> <source media="(prefers-color-scheme: dark)" srcset="docs/images/fc_logo_full_transparent-bg_white-fg.png"> <source media="(prefers-color-scheme: light)" srcset="docs/images/fc_logo_full_transparent-bg.png"> <img alt="Firecracker Logo Title" width="750" src="docs/images/fc_logo_full_transparent-bg.png"> </picture> Our mission is to enable secure, multi-tenant, minimal-overhead execution of container and function workloads. Read more about the Firecracker Charter [here](CHARTER.md). ## What is Firecracker? Firecracker is an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant container and function-based services that provide serverless operational models. Firecracker runs workloads in lightweight virtual machines, called microVMs, which combine the security and isolation properties provided by hardware virtualization technology with the speed and flexibility of containers. ## Overview The main component of Firecracker is a virtual machine monitor (VMM) that uses the Linux Kernel Virtual Machine (KVM) to create and run microVMs. Firecracker has a minimalist design. It excludes unnecessary devices and guest-facing functionality to reduce the memory footprint and attack surface area of each microVM. This improves security, decreases the startup time, and increases hardware utilization. Firecracker has also been integrated in container runtimes, for example [Kata Containers](https://github.com/kata-containers/kata-containers) and [Flintlock](https://github.com/liquidmetal-dev/flintlock). Firecracker was developed at Amazon Web Services to accelerate the speed and efficiency of services like [AWS Lambda](https://aws.amazon.com/lambda/) and [AWS Fargate](https://aws.amazon.com/fargate/). Firecracker is open sourced under [Apache version 2.0](LICENSE). To read more about Firecracker, check out [firecracker-microvm.io](https://firecracker-microvm.github.io). ## Getting Started To get started with Firecracker, download the latest [release](https://github.com/firecracker-microvm/firecracker/releases) binaries or build it from source. You can build Firecracker on any Unix/Linux system that has Docker running (we use a development container) and `bash` installed, as follows: ```bash git clone https://github.com/firecracker-microvm/firecracker cd firecracker tools/devtool build toolchain="$(uname -m)-unknown-linux-musl" ``` The Firecracker binary will be placed at `build/cargo_target/${toolchain}/debug/firecracker`. For more information on building, testing, and running Firecracker, go to the [quickstart guide](docs/getting-started.md). The overall security of Firecracker microVMs, including the ability to meet the criteria for safe multi-tenant computing, depends on a well configured Linux host operating system. A configuration that we believe meets this bar is included in [the production host setup document](docs/prod-host-setup.md). ## Contributing Firecracker is already running production workloads within AWS, but it's still Day 1 on the journey guided by our [mission](CHARTER.md). There's a lot more to build and we welcome all contributions. To contribute to Firecracker, check out the development setup section in the [getting started guide](docs/getting-started.md) and then the Firecracker [contribution guidelines](CONTRIBUTING.md). ## Releases New Firecracker versions are released via the GitHub repository [releases](https://github.com/firecracker-microvm/firecracker/releases) page, typically every two or three months. A history of changes is recorded in our [changelog](CHANGELOG.md). The Firecracker release policy is detailed [here](docs/RELEASE_POLICY.md). ## Design Firecracker's overall architecture is described in [the design document](docs/design.md). ## Features & Capabilities Firecracker consists of a single micro Virtual Machine Manager process that exposes an API endpoint to the host once started. The API is [specified in OpenAPI