SwarmCraft helps teams replace one focused workflow at a time instead of trying to rebuild an entire SaaS suite in one jump.
It is designed for the early questions people usually ask first: what SwarmCraft is, who it is for, what kinds of workflow replacement are in scope, what happens after unlock, and how much of the delivery path still belongs to the team using it.
The best SwarmCraft projects usually start with a workflow that is:
- repetitive enough to define clearly
- painful enough to justify replacing
- focused enough to ship safely
- still connected to an existing system of record
That is why SwarmCraft works well for intake steps, approval flows, lightweight boards, reporting views, and handoff processes wrapped around a larger platform.
Who SwarmCraft fits best
SwarmCraft fits best when one person or team can clearly explain the current workflow, the pain around it, and the boundary between the workflow surface and the trusted system underneath.
That usually means an operator, founder, manager, consultant, or internal champion who wants a focused replacement path instead of another broad monthly platform.
How the flow works
SwarmCraft currently follows a practical sequence:
- Start with discovery chat and describe the workflow you want to replace.
- Confirm the summary so the scope is clear before any project work begins.
- Unlock the project when the path looks worth building.
- Use the project board and VS Code extension to move from plan to implementation.
The flow is meant to create confidence in stages: first clarify the workflow boundary, then unlock a concrete project, then move into guided delivery rather than stopping at a vague summary.
What SwarmCraft is not
SwarmCraft is not a promise to replace your core accounting, identity, payroll, or compliance systems on day one.
The product is designed to help you replace the workflow surface around those systems, not the trusted record underneath them.
It is also not a managed runtime that takes over your infrastructure, release process, or operating responsibility. SwarmCraft helps you define and build the replacement, while your team still chooses how the finished app is reviewed, deployed, and run.
What setup usually looks like
Most teams follow the same setup path:
- Start the discovery chat in the web app.
- Install the VS Code extension.
- Sign in and complete MFA.
- Connect the correct repository.
- Unlock the project only when the workflow boundary is clear.
If you want the step-by-step setup guides, continue with Download VS Code and install SwarmCraft and Sign in and set up MFA.
Good next steps
If you are new to the product, continue with Choose a technology stack, Set up a git repository, and Frequently asked questions before you connect the VS Code extension.