Search docs

Docs search

Supported Stacks

ArchPilot Smart Init and architecture validation work across common backend, frontend, library, and repository patterns using deterministic local detection.

Why it matters

Use this page to understand what ArchPilot can detect today and where Smart Init can help teams model architecture faster.

Backend stack coverage

  • Node.js / TypeScript
  • NestJS
  • Express.js
  • Java
  • Spring / Spring Boot
  • Kotlin
  • FastAPI
  • Django
  • Flask
  • PHP
  • Laravel
  • Go
  • .NET
  • Ruby on Rails

Frontend stack coverage

  • React
  • Next.js
  • Angular
  • Vue

Infrastructure stack coverage

  • Terraform
  • Ansible

Python framework detection

These detections stay local, deterministic, and evidence-based. ArchPilot does not rely on deep semantic framework parsing to propose the initial architecture context.

  • FastAPI detection uses dependency markers, imports, route patterns, and practical repository evidence.
  • Django detection uses django dependency markers, manage.py, settings.py, common Django project layout, and practical repository evidence.
  • Flask detection uses flask dependency markers, from flask import Flask, app = Flask(__name__), route decorators, and practical repository evidence.

Repository and project patterns

  • Single-project repositories
  • Monorepos with apps, packages, libraries, or services
  • Backend and frontend multi-project repositories
  • Repository layouts with feature or module-style folders

How to interpret support

Support here means ArchPilot can detect practical evidence and use it to propose architecture context and validation defaults. It does not mean every stack has identical depth across every architecture rule family.

The goal is consistent architecture validation and architecture governance workflows, with deterministic local behavior across a broad range of repositories.

Supported Stacks | ArchPilot Docs