This FAQ is the central public reference for the most common SwarmCraft questions.
Use it when you want a plain-language explanation of who SwarmCraft is for, what kinds of workflow replacement are in scope, how the unlock works, what setup looks like, and where the formal legal terms live.
Fit and qualification
What is SwarmCraft?
SwarmCraft helps teams replace one narrow workflow inside bloated SaaS instead of buying another broad platform. The goal is to keep the part of the work that matters and remove the software waste around it.
Who is SwarmCraft for?
SwarmCraft is for pragmatic operator-builders: the founder, manager, consultant, or internal champion who knows which workflow still matters, can describe it clearly, and wants a smaller replacement path without another large subscription.
What problem is SwarmCraft designed to solve?
It is designed to help teams stop paying for broad software they barely use when only one small workflow still matters. The usual pattern is recurring SaaS spend, awkward manual patchwork, and a workflow that no longer fits the real job.
Where should I start if I am still figuring out fit?
Start by naming one workflow that still matters inside the broader product you want to reduce or replace. If you can describe the owner, the pain, and the system of record that must remain, you are already close to a good first SwarmCraft conversation.
If you want a broader overview before you start chatting, read What SwarmCraft is and then Start your first discovery chat.
How is SwarmCraft different from another SaaS platform?
SwarmCraft is not another broad platform you rent every month. It helps you define and unlock a narrower replacement path for the workflow you actually use, then carry that work forward yourself.
Do I need to know how to code?
No. You do need enough comfort with software and process detail to review the workflow, make decisions, and keep the work grounded in reality.
How much work do I need to do myself?
You need to help define the current workflow, explain what still matters, review the proposed replacement path, and then work through the follow-up implementation loop in VS Code. SwarmCraft gives you the board, packet files, and AI-assisted delivery flow, but you still drive the work, review the changes, and decide what is good enough to keep.
Workflow boundaries and safety
What does "replace the workflow, not the system of record" mean?
It means starting with the operational layer around the trusted system rather than trying to rip out the core record system itself. Good first targets are intake, approvals, boards, dashboards, and review loops that sit around an existing platform.
What kinds of workflows are a good fit for SwarmCraft?
The best fits are narrow, repeatable workflow surfaces with clear owners, real pain, and visible waste inside a broader tool. Good examples include intake forms, approval flows, internal ticketing, operational dashboards, onboarding steps, and knowledge workflows.
What kinds of workflows are not a good fit?
Poor fits include full system-of-record replacements, highly regulated or high-liability systems, and situations where nobody can clearly describe the workflow that needs replacing. SwarmCraft is strongest when the scope is narrow and the boundaries are explicit.
How does SwarmCraft reduce the risk of replacing the wrong thing?
It starts with one narrow workflow, clarifies what must stay in the existing system of record, and avoids broad replacement claims. The point is to make the scope small enough to reason about before you commit to building.
What if my workflow still depends on an existing SaaS tool or system of record?
That is normal. In many cases the first goal is to replace the workflow surface around the trusted system, not to remove every dependency on day one.
Unlock flow and pricing
What happens in the chat step?
The chat identifies the bloated product, the exact workflow that still matters, the pain around it, and the safer scope boundary before any unlock happens. It is there to make the replacement path clearer, not to push you into paying before the scope makes sense.
If you want the broader commercial flow, see Pricing.
What do I get when I unlock a project?
You get a project board, starter task set, and a clearer path to build the workflow replacement you just defined. The unlock moves the work from discovery into something you can review and act on.
Why is the unlock a one-off payment instead of a subscription?
The commercial model is built around helping customers escape recurring software rent, not adding another monthly platform bill. The offer is intentionally shaped as a one-off unlock so the economics match the ownership story.
Why is the price so low?
The unlock price is meant to be a low-friction way to test a workflow replacement path against the much larger cost of ongoing SaaS waste. It is a small commercial step designed to prove whether the replacement is worth carrying forward.
What happens after I unlock the project?
After unlock, the work moves from discovery into an actionable project you can review, refine, and build forward. The project is meant to give you momentum, not leave you with a vague summary and no next step.
The usual next steps are to connect the project to the right repository, open the board, work the first ticket, and start the delivery loop inside VS Code.
If you want the detailed flow, continue with Connect SwarmCraft to your project and Build the project.
Ownership and capability
Do I own the workflow and artifacts that come out of SwarmCraft?
You should expect to keep control of your workflow materials and outputs, while SwarmCraft still owns the platform itself. For the formal legal terms, read the Software License and Terms of Service.
Can I keep improving the workflow myself after the initial unlock?
Yes. A core part of the SwarmCraft promise is that you should become more capable and be able to keep shaping the workflow over time instead of becoming more dependent.
Who runs and deploys the finished app?
Your team runs and deploys the finished app through the infrastructure and release path you already trust. SwarmCraft helps define and build the workflow replacement, but it does not become a hosted operations layer that takes over deployment responsibility.
If you want the delivery-side explanation, read Deploy your app.
Why does SwarmCraft use AI and still emphasize human judgement?
AI helps accelerate planning and delivery, but people still need to define the workflow, review outputs, and make accountable decisions. SwarmCraft is built around human-reviewed orchestration, not AI magic.
Setup and operating model
What do I need before I can start using SwarmCraft seriously?
You need four practical things: a clear target workflow, a person who can describe the current process, a repository where the project work will live, and a machine with VS Code available for the delivery loop.
You do not need a fully formed technical specification before the first chat. You do need enough clarity to explain what workflow hurts today and what system of record must stay in place.
Do I need to install anything?
Yes. Discovery can start in the web app, but the delivery loop currently depends on the SwarmCraft VS Code extension. The normal setup path is: install VS Code, install the extension, sign in, complete MFA, and connect the right repository folder.
Use these guides when you are ready:
Do I have to use VS Code?
For the current SwarmCraft delivery loop, yes. The web app handles discovery, board access, and project coordination, but the local implementation workflow is designed around the VS Code extension and the repository it is connected to.
Do I have to move to new infrastructure or a new hosting platform?
No. SwarmCraft is strongest when the replacement app is delivered through the infrastructure your team already knows how to operate. The goal is to replace the workflow that no longer fits, not force a second platform migration at the same time.
How do I submit a support ticket?
SwarmCraft has a dedicated signed-in support workspace inside the product. Open Support in the authenticated workbench, choose New ticket, add a subject, choose the closest topic, and describe the problem in enough detail for follow-up.
After you submit the ticket, you can keep using the same support area to review status updates, read the thread, and reply when the support team needs more information.
If you want the full support workflow, read Use the support workspace.
Legal and policy questions
What terms govern billing, cancellations, and refunds?
The plain-language answer is that SwarmCraft’s billing, cancellation timing, payment handling, and refund position live in the Terms of Service. The FAQ is only a summary entry point, so use the legal page for the authoritative wording.
Related pages
- Learn the product story in About.
- Review the commercial flow in Pricing.
- Read the formal terms in Terms of Service.
- Review ownership and platform-use terms in the Software License.
- Review privacy details in the Privacy Policy.
- Review analytics and consent controls in Cookie Settings.