SwarmCraft helps operators define the smallest coherent operation they should own instead of reproducing an entire SaaS suite feature for feature.
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 work that is:
- repetitive enough to define clearly
- painful enough to justify replacing
- focused enough to ship safely
- bounded enough to assign real ownership, continuity, and review
Fast Start keeps the existing system of record and plans the focused workflow around it. Deep Discovery can examine a broader coherent operation, including bounded records, when evidence, migration risk, and operating responsibility support that boundary.
Who SwarmCraft fits best
SwarmCraft fits best when an accountable operator 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 has two discovery entries:
- Fast Start: use a focused guided conversation and confirm a bounded handoff when the workflow and existing system-of-record boundary are already clear.
- Deep Discovery: use sources, owner interviews, and nine reviewed documents before previewing and authorizing one exact text package.
Both routes then use the same Project Unlock, create one project and initial board through private server generation, and move into the same board and VS Code delivery loop.
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 accounting ledgers, identity infrastructure, payroll, regulated clinical records, or other high-liability systems without the migration, reconciliation, continuity, compliance, support, observability, and rollback work that responsible ownership requires.
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
Choose the setup path that matches the discovery depth:
- Choose Fast Start or Deep Discovery.
- For Fast Start, begin in the browser and confirm the guided workflow summary.
- For Deep Discovery, install VS Code and SwarmCraft, sign in with MFA, and open one trusted Git repository before starting.
- Continue through Project Unlock only when the route-specific review boundary is complete.
- Connect and build the resulting project through the shared delivery workflow.
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.