Home Features Setup Guide Documentation FAQ GitHub

Features

SWAT provides a clean Symfony foundation with built-in CI/CD, automated deployments and a lightweight frontend stack for real-world projects.

Core features

🚀 Modern Symfony stack

Built on a clean Symfony structure with sensible defaults, production-ready configuration and a codebase that stays readable from day one.

⚡ Lightweight frontend

Twig, Webpack Encore, TypeScript, Turbo and SCSS provide a modern frontend workflow without the overhead of a heavy SPA stack.

🔧 Built-in CI/CD

GitHub Actions workflows are included to validate, build and deploy your application across preproduction and production environments.

📦 Frontend asset pipeline

Webpack Encore handles TypeScript, SCSS and asset compilation with minimal configuration, so you can focus on building instead of wiring tooling.

🧪 Validation and quality tools

SWAT includes PHPUnit, PHPStan, ESLint and Vitest to help keep both backend and frontend code reliable before deployment.

🪶 Fast to start, easy to extend

The starter stays intentionally lightweight, so you can move fast at the beginning without locking yourself into an overengineered structure.

What makes SWAT different

SWAT is not just a Symfony starter with a nice structure. Its real value comes from the combination of a clean application base and a deployment workflow that is ready to use from day one.

No overengineering

No unnecessary architectural layers, no bloated stack and no fake complexity. SWAT focuses on the common foundation needed to start a modern Symfony project properly.

Real CI/CD, not just local setup

SWAT includes real validation and deployment workflows. Push to dev for preproduction, then create a release tag to deploy to production.

Built to be used, not just explored

The project is meant to be cloned, adapted and shipped for real applications, not just explored as a demo repository.

Design philosophy

SWAT is opinionated enough to provide a strong starting point, but intentionally limited to the shared foundation. Project-specific infrastructure and business needs are meant to stay in the final project, not in the starter.

Simple by default

The stack stays readable and understandable, even for developers who want to move fast without fighting the tooling.

Flexible in practice

You can adapt the workflows, change the deployment strategy, evolve the frontend or reorganize the project without having to fight the base structure.

Focused on the shared core

SWAT provides the common base. Cron jobs, workers, custom infrastructure and project-specific logic remain where they belong: in your application.

Ready to get started?

Start with SWAT, get your project running locally, then move from validation to deployment with the included workflows and documentation.