SwarmCraft helps you define and build the replacement. You still deploy the finished app through the infrastructure your team operates.
Typical deployment flow
Most teams follow the same release sequence:
- Build the deployable artifact.
- Apply the environment-specific configuration and secrets.
- Deploy to the target runtime.
- Smoke-test the workflow that motivated the project.
- Watch the first release closely and be ready to roll back.
Use the platform you already trust
If your delivery flow already uses Docker images, Kubernetes, or another managed platform, keep using it. SwarmCraft is not stronger because you introduce a second operations model.
In this repository, Docker and Helm guides already exist for the runtime assets. If your generated app follows a different deployment model, prefer the one your team can operate confidently.
Verify the replaced workflow
The final test is not only that the app starts. The final test is that the workflow you targeted now runs better than it did in the old tool.