Each pillar of the platform can be adopted on its own. The fastest way to get the whole platform is through its Build Ecosystem: the anarchy-toolkit CLI tool creates a complete solution, and its Anarchy automation components, powered by Fallout Build, can also be added to a repository you already have. Individual Infrastructure packages work on their own too.

Developer workstation with a terminal and code editor, dark theme, red-orange accent lighting, wide banner

flowchart TD
    Start{"What do you have?"}
    Start -->|"An empty folder"| CLI["<b>anarchy-toolkit bootstrap</b><br/>solution + build + apps"]
    Start -->|"A repository, no build tooling"| Automation["<b>Anarchy.Toolkit.Automation.Build</b><br/>build targets for your solution"]
    Start -->|"An application that needs a capability"| Packages["<b>Individual packages</b><br/>dotnet add package + UseModule"]
    CLI --> Scaffold["anarchy-toolkit scaffold<br/>api · job · ui"]
    Automation --> Make["make compile · test · check_layering · pack"]
    Scaffold --> Make
Path Best for Page
CLI tool New services and monorepos: generates the layered solution, the Anarchy build, the Makefile and scripts, and APIs, jobs or UIs on the toolkit’s packages. New solution with the CLI
Anarchy automation Existing repositories: adds standard compile, lint, test, layering, dependency-map, packaging, release and Docker targets. Adding Anarchy automation
Packages Existing applications: add persistence, messaging, telemetry, hosting or web plumbing one package at a time. Using the packages

Automation preferences are optional: use the documented folder baseline without creating a config file, or inspect and edit saved defaults in Automation Preferences.

Not sure which packages you need? See Which package do I need?. Not sure which path fits? The Adoption Advisor asks a few questions about your project and suggests the packages, steps and pages, in order. The guides walk through both main paths: Your First Solution and Adopting an Existing Solution.

Let your agent do it

Using a coding agent? Paste this line into it, from the folder or repository where you want to adopt it:

Follow https://raw.githubusercontent.com/anarchy-io/anarchy-toolkit/main/agents/ADOPT.md to adopt Anarchy Toolkit in this repository.

The agent works out which path fits, asks before anything destructive, can install the toolkit’s agent skills and verifies the result with the build.

Requirements

  • The .NET 10 SDK.
  • Bash and Make (macOS, Linux or WSL) for the generated Makefile and scripts. Windows users can run supported build targets directly with dotnet run --project build/_build.csproj -- <Target>; see Without Make.
  • Access to nuget.org, where the packages are published under the anarchy-io profile (or a feed mirroring the Anarchy.Toolkit.* packages).

See it working

The samples are complete applications built on the toolkit’s defaults: a REST API, a Lambda job, an EC2 worker and a WebApp, with their tests.