# Introduction


- **Product**
- [Introduction](https://axelix.io/docs/product/introduction): Welcome to Axelix! We're glad you're here.
- [Motivation](https://axelix.io/docs/product/motivation): This document explains the core problems that Axelix solves for Spring Boot developers and organizations. Through real-world examples, we'll explore the pain points that inspired Axelix's creation.
- [Architecture](https://axelix.io/docs/product/architecture): Axelix has one central application — **Axelix Master** — that talks to every Spring Boot service you want to manage through an **Axelix Starter** dependency on the service side. The web UI and the MCP server both live inside Master, so the same data is served to a browser and to an AI agent from a single process.
- [How discovery works](https://axelix.io/docs/product/discovery): How Axelix Master learns which Spring Boot instances exist and keeps their state up to date, either by finding them in Kubernetes on its own or by letting each instance register itself.

- **Start**
- [Getting Started](https://axelix.io/docs/start/getting-started): This page describes the recommended way to roll Axelix out across an organization: which environments to start with, in what order to install the components, and how to reach production safely. Each step gives the concrete commands and the minimal configuration, and links to the detailed configuration page for the full reference.
- [Install with AI](https://axelix.io/docs/start/SKILL): Install Axelix into a Spring Boot service: the Axelix Spring Boot starter, the Axelix build plugin, and, for a local trial, Axelix Master itself. Use when the user asks to install, add, set up, try, or connect Axelix.
- [Configuring Master](https://axelix.io/docs/start/configuring-master): This page shows how to run Axelix Master in your own environment. Pick a shape that matches how you ship the rest of your services: a standalone JAR, a Docker container, a Docker Compose stack, or a Kubernetes deployment.
- [Configuring Spring Boot Starter](https://axelix.io/docs/start/configuring-spring-boot-starter): How to wire the Axelix Spring Boot Starter into a Spring Boot application so Axelix Master can discover it, read its state, and act on it.
- [Configuring the Axelix Build Plugin](https://axelix.io/docs/start/configuring-build-plugin): Applying the Axelix build plugin stamps your build coordinates into the artifact so Axelix Master can identify the instance.

- **UI Guide**
- Dashboard
  - [Dashboard](https://axelix.io/docs/ui-guide/dashboard/legacy-dashboard): The Dashboard is a landing page in Axelix. It summarises every Spring Boot service that Axelix Master currently tracks: the runtime versions in the fleet, how many instances are healthy right now, and the aggregate memory footprint.
  - [Overview](https://axelix.io/docs/ui-guide/dashboard/overview): The Overview dashboard shows which versions of Spring Boot, Spring Framework, Java, and Kotlin the applications in the fleet use.
  - [Spring Portfolio](https://axelix.io/docs/ui-guide/dashboard/spring-portfolio): The Spring Portfolio dashboard shows which Spring Boot and Spring Framework versions the applications in the fleet use, and how many of them are already past OSS support.
  - [Languages Profile](https://axelix.io/docs/ui-guide/dashboard/languages-profile): The Languages Profile dashboard shows which Java releases, JDK builds, and Kotlin versions the applications in the fleet run on.
  - Technologies
    - [Java](https://axelix.io/docs/ui-guide/dashboard/technologies/java): The Java dashboard shows which JVM features the services in the fleet use: Project Leyden, garbage collectors, GC logging, and Project Lilliput.
    - [Persistence](https://axelix.io/docs/ui-guide/dashboard/technologies/persistence): The Persistence dashboard shows which services in the fleet have the most N+1 queries and in-memory pagination.
    - [Spring Framework](https://axelix.io/docs/ui-guide/dashboard/technologies/spring-framework): The Spring Framework dashboard shows how many services in the fleet run with Open Session in View enabled.
- [Wallboard](https://axelix.io/docs/ui-guide/wallboard): The Wallboard is the default landing page in Axelix.
- [Service Profile](https://axelix.io/docs/ui-guide/service-profile): The Service Profile is the per-instance area of Axelix. It groups every diagnostic and inspection screen for a single Spring Boot instance behind one sidebar, so you can move between Beans, Loggers, Thread Dumps, and the rest without losing the context of the instance you are looking at.
- [Users](https://axelix.io/docs/ui-guide/users): The **Users** screen is where you see who can sign in to Axelix Master, what role each account carries, and — when local authentication is enabled — where you create, edit, and delete those accounts. The page is reachable from the **Users** link in the top navigation bar.
- [MCP](https://axelix.io/docs/ui-guide/mcp): The MCP screen lists every tool that Axelix Master exposes through its bundled Model Context Protocol server. Each card is one tool an AI agent connected over MCP can invoke against any registered Spring Boot instance.

- **Features**
- Insights
  - [Details](https://axelix.io/docs/features/insights/details): The Details page provides information about a managed Spring Boot application instance. This page displays technical metadata, runtime information, and build details in an organized, easy-to-read format.
  - [Metrics](https://axelix.io/docs/features/insights/metrics): The Metrics page lists every Micrometer meter exposed by a managed Spring Boot instance, with a live chart and tag filtering per metric.
  - [Loggers](https://axelix.io/docs/features/insights/loggers/loggers): The Loggers page shows the logging level of every logger and logger group in a Spring Boot instance and lets you change it at runtime, permanently or for a limited time.
  - [Dependencies Analyzer](https://axelix.io/docs/features/insights/dependencies-analyzer): The Dependencies Analyzer shows every library a Spring Boot instance runs with, flags the projects that are no longer actively developed, and shows whether the instance's Spring Boot line still receives OSS updates.
- Spring Framework
  - [Properties](https://axelix.io/docs/features/spring-framework/properties): The Properties page shows where every property of a Spring Boot instance comes from, which value the application actually uses, which properties are deprecated, and which beans read them.
  - [Beans](https://axelix.io/docs/features/spring-framework/beans): The Beans page lists every Spring bean registered in the managed instance's ApplicationContext. Each row is an expandable accordion that shows the bean's class, scope, dependencies, qualifiers, proxying strategy, and the origin Spring used to create it.
  - [Configuration Properties](https://axelix.io/docs/features/spring-framework/configuration-properties): The Configuration Properties page lists every @ConfigurationProperties bean registered in the Spring Boot instance, grouped by bean class, with the property prefix and the values Spring currently binds into the bean.
  - [Scheduled Tasks](https://axelix.io/docs/features/spring-framework/scheduled-tasks): The Scheduled Tasks page provides access to all tasks annotated with @Scheduled within a Spring Boot application. You can also update the task status, modify its schedule, and trigger it manually when required.
  - [Conditions](https://axelix.io/docs/features/spring-framework/conditions): The Conditions page shows the Spring Boot auto-configuration report for the managed instance — every @Conditional evaluation Spring performed at startup, split into two tabs by outcome.
  - [Caches](https://axelix.io/docs/features/spring-framework/caches): The Caches page provides access to all configured caches in the Spring Boot application. It displays a per-cache hit/total ratio chart, hit and miss counts, the estimated number of entries, allows status management, and supports clearing individual caches or all caches at once.
  - [Transaction Control](https://axelix.io/docs/features/spring-framework/transaction-control): The Transaction Control page finds @Transactional methods that keep a database connection busy longer than they should: blocking network calls, N+1 queries, and in-memory pagination inside the transaction. For each problem, it shows where it happens, so you can find the place in the code.
  - [Entities Map](https://axelix.io/docs/features/spring-framework/entities-map): The Entities Map page checks the JPA mapping of every entity in a Spring Boot instance and shows the associations that are mapped in a way that costs extra queries: eager fetching, List-backed @ManyToMany, cascade REMOVE or ALL, and unidirectional @OneToMany.
- JVM
  - [Thread Dump](https://axelix.io/docs/features/jvm/thread-dump): The Thread Dump page shows a live snapshot of every thread in the managed Spring Boot instance. The page polls the instance periodically, so the list, the thread states, and the timeline reflect recent JVM state rather than a frozen capture.
  - [Garbage Collector](https://axelix.io/docs/features/jvm/garbage-collector): The Garbage Collector page lets you enable JVM GC logging on a managed Spring Boot instance, trigger an on-demand collection, and download the resulting log file. GC logging is normally off in production. The page exists to switch it on for a focused investigation and then turn it off again.

- **Master**
- [What is Master?](https://axelix.io/docs/setting-up-master-ui/what-is-master): Axelix Master (or simply "Master") is the central hub of the Axelix ecosystem, application with enhanced capabilities for managing and monitoring Spring Boot applications across various environments.
- [Configuring Master](https://axelix.io/docs/setting-up-master-ui/configuring-master/configuring-master): This page shows how to run Axelix Master in your own environment. Pick a shape that matches how you ship the rest of your services: a standalone JAR, a Docker container, a Docker Compose stack, or a Kubernetes deployment.
- [Database Migrations](https://axelix.io/docs/setting-up-master-ui/migrations/migrations): Master owns its database schema and keeps it in step with the running version.
- [Authentication](https://axelix.io/docs/setting-up-master-ui/authentication/authentication): This page explains how sign-in to Axelix Master actually works: which authentication options exist, how the browser session is established and verified on each request, the role/authority model that gates the UI, and how the MCP server authenticates AI agents.
- [MCP Tools](https://axelix.io/docs/setting-up-master-ui/mcp/mcp-tools): This page is the reference list of every tool the bundled MCP server in Axelix Master exposes to AI agents.

- **Your Services**
- Spring Boot Starter
  - [What is the Axelix Spring Boot Starter?](https://axelix.io/docs/setting-up-spring-boot-service/spring-boot-starter/what-is-spring-boot-starter): Axelix Starter (also known as ASBS - Axelix Spring Boot Starter) is a Spring Boot starter dependency that enables your Spring Boot applications to integrate seamlessly with the Axelix platform. It's the bridge between your applications and the Axelix Master management console.
  - [Configuring Spring Boot Starter](https://axelix.io/docs/setting-up-spring-boot-service/spring-boot-starter/configuration): How to wire the Axelix Spring Boot Starter into a Spring Boot application so Axelix Master can discover it, read its state, and act on it.
- Build Plugin
  - [What is the Axelix Build Plugin?](https://axelix.io/docs/setting-up-spring-boot-service/build-plugin/what-is-build-plugin): The Axelix build plugin is a small Gradle or Maven plugin you apply to every service you want Axelix to manage. It runs at build time and writes a `META-INF/axelix-info.properties` file into your application's artifact. That file carries the identity Master uses to tell one application apart from another.
  - [Configuring the Axelix Build Plugin](https://axelix.io/docs/setting-up-spring-boot-service/build-plugin/configuration): Applying the Axelix build plugin stamps your build coordinates into the artifact so Axelix Master can identify the instance.

- **More**
- [Glossary](https://axelix.io/docs/more/glossary): This document defines key terms and abbreviations used throughout the Axelix documentation and codebase.
- [Why not just Spring Boot Admin?](https://axelix.io/docs/more/why-not-spring-boot-admin): Spring Boot Admin (SBA) is often the first tool teams reach for when they want a solution over Spring Boot deployments. This page explains where Axelix fits relative to SBA: what problems Axelix was built to solve, and how the two products compare on capabilities and operations.
- [Compatibility & Versioning](https://axelix.io/docs/more/compatibility-and-versioning): This page explains how Axelix itself is versioned and how it stays compatible with the major parties in play: the Java version your services run on, the Spring Boot major version they are built against, and how Axelix's own components stay compatible with each other.
- [Upgrading Axelix](https://axelix.io/docs/more/upgrading): The procedure that makes upgrading a real fleet safe and predictable when Master and the starters move at different speeds.
- [Support Policy](https://axelix.io/docs/more/support-policy): How often Axelix releases new versions, which open source versions still receive fixes, and for how long.
- [Licensing](https://axelix.io/docs/more/licensing): Which license covers each Axelix component, and what the licenses mean when you use Axelix in your own projects.
- [Versions in the docs](https://axelix.io/docs/more/versions-in-docs): How the documentation marks releases and which release the screenshots show.
- [Troubleshooting](https://axelix.io/docs/more/troubleshooting): This page describes the most common issues that occur during Axelix installation and configuration.
- Development
  - [Branching Model](https://axelix.io/docs/more/development/branching-model): Axelix is developed in the open as a monorepo, so understanding how the codebase evolves also explains why releases arrive the way they do.
  - [Releases](https://axelix.io/docs/more/development/releases): This page describes the exact procedure by which we release Axelix.