SwarmCraft does not get stronger when you choose the fanciest stack. It gets stronger when you choose the stack your team can actually ship, review, and operate.
Use these four decisions first
Before you unlock a project, make four choices explicit:
- frontend surface: browser app, internal tool, extension-driven workflow, or no frontend at all
- backend runtime: the platform your team already supports comfortably
- persistence: existing system of record, new database, or a lightweight workflow store
- deployment target: where the final app will actually run
Prefer familiarity over novelty
If your team already runs React, Spring Boot, Node, .NET, or another stable stack well, start there.
SwarmCraft works best when the project board and packet flow are helping you move faster through delivery, not forcing the team to learn a brand-new platform at the same time.
Match the stack to the replacement target
Good stack choices usually reflect the workflow you are replacing:
- dashboards and forms often benefit from a simple web frontend
- approval or intake flows often need an API plus a durable store
- extensions or internal tooling may need tight editor or repository integration
Keep the first slice boring on purpose
The first release only needs to prove that the workflow can be replaced safely. You can widen the architecture later.
Once the stack is clear, continue with Set up a git repository.