Checkout crashes when a saved card expires
#ACM-61
Powered by a competition-winning agent harness
The agentic coding platform for your most difficult projects.
Swarmli turns one conversation into a swarm of agents. They grill your idea, write the spec, build in parallel and prove that every change works — before it ever reaches your review.
A Acme/ / Workspace TD
ACM-41 Webhook retry backoff Implement
Claude Code · Opus
› /implement ACM-41
Reading the Spec and 3 acceptance criteria
Plan · queue → backoff → dead letter
✎ src/lib/webhooks/retry.ts +84 −6
ACM-42 Rate-limit public search Implement
Codex · GPT
› /implement ACM-42
✎ src/routes/api/search/+server.ts +22
✎ src/lib/server/limits.ts +57
From one conversation to merged code
- Talk
- Grill
- Spec
- Tickets
- Swarm
- Verify
- Review
- Merge
Agent Meetings
Meetings where the agents did the homework.
Swarmli books an Agent Meeting into your calendar and walks you through the agenda. It grills every ticket with questions it has already answered for you, writes the spec, cuts the work into tickets — and saves nothing until you say so.
A Acme/ Meetings TD
Meeting Agents
Agent Meeting — Web app: 5 Tickets to spec, 2 Merge Requests to accept
Ticket 3 of 5 · ACM-53 · ASAP
Usage-based billing
Customers on the Growth plan want to pay for what they track, not per seat. Finance needs invoices that show it.
Grill this Ticket to write its Spec, or skip it.
Grill this Ticket Skip
Ask anything…
-
Booked into your free time
Swarmli reads your calendar and plans the meeting where you have room.
-
Answers already recommended
Every question comes with the option the swarm would pick, and why.
-
A Spec you can build from
Goal, rules and acceptance criteria — written while you decide.
-
Tickets that know their order
Sub-Tickets with what blocks what, ready for agents the moment you save.
Ticket board · The board
A board that fills itself.
Inbox 0
Backlog 0
Next Release 0
This Release 0
Implementation 0
Completed 0
Export the board to CSV
#ACM-62
Delete a client’s data within 30 days
#ACM-63
Sign-in link expires too fast on mobile
#ACM-64
Dark mode for the dashboard
#ACM-50
Offline mode for field teams
#ACM-55
Move the docs to the new schema
#ACM-57
Audit log export
VO #ACM-54
German for the client portal
#ACM-56
Board columns keep order after a rename
#ACM-58
Usage-based billing
#ACM-53
SSO with Google Workspace
#ACM-52
Webhook retry backoff
#ACM-41
Verify
Stream the events table
#ACM-45
Code review
Rate-limit the public search
#ACM-38
Rotate the signing key
#ACM-36
Read-only board for client viewers
#ACM-33
Ask anything…
The swarm
A swarm, not a single chat.
Other tools give you one agent in one chat window. Swarmli runs as many as the work needs — each on its own branch, watched by its own Observer, conducted by a hub that never sleeps.
-
One worktree per ticket
Every agent works on its own branch, in its own checkout. Nothing collides, everything merges.
-
Observers that correct
A second agent watches the first and sends corrections the moment it drifts from the Spec.
-
Handoffs, mid-flight
Claude Code, Codex, Cursor — hand a Session to another agent without losing a line of context.
-
A fleet that heals itself
Stalled agents get a nudge, then a restart. Only what truly needs you reaches you.
The harness
A competition-winning agent harness.
Under every agent runs a harness built to win coding contests against the clock. It races several solvers at once, judges every answer before you see it, and repairs in the same breath. Here it is next to your usual vibe-coding flow.
the same answer · 1,500 output tokens
t = 0.0 s
Swarmli fast lane
0 tok
Swarmli second lane
0 tok
Your usual flow fast model
0 tok
Your usual flow balanced model
0 tok
Your usual flow frontier model
0 tok
Same task. Same answer. Watch the clock.
30×
faster to a first answer
than a frontier model typing in a chat
Parallel
solvers on every task
different approaches race; the first answer that passes wins
Judged
before you see it
every answer runs against real examples and gets repaired in place
Review walk
Merge requests that explain themselves.
Every change arrives as a guided walk: what it is, the proof that it works, and the diff cut into steps that make sense. Reviewing a day of agent work takes minutes, not an afternoon.
-
In the order you should read it
The agent that wrote the change plans your review: overview, proof, then the code in slices.
-
Evidence, not promises
Recordings of the feature working, test logs, and every acceptance criterion ticked against them.
-
Reviewed before it reaches you
Code review, security review and verification ran first. You decide; you don’t dig.
A Acme/ / / !61 Usage-based billing TD
What this change is
Growth workspaces now pay per tracked event. Usage is counted per workspace and day, priced in four tiers, and shown as lines on the invoice. A failed charge retries three times over seven days before ingest pauses.
Lines
+184 −32
Files
9 of 9
Code steps
3
Branch
feat/usage → main
The review plan was written by the agent that built it, in the order you should read it.
Close Merge
Fully autonomous runs
You sleep. The swarm ships.
Hand Swarmli a goal and a budget before you leave. It plans, grills, builds, reviews, verifies and merges through the night — measuring against your targets, and saving the one question it couldn’t answer for your morning.
Tonight
22:00
A Acme/ / Auto report TD
1 Headline 2 Auto inputs · 3 Board changes · 4 Features landed · 5 Working now · 6 Next
Goal
Ship usage-based billing for the Growth plan
Running · 9 h left of 9 h
Done
3
At work
3
Waiting
9
Blocked
0
Target
Invoice page p95 under 400 ms
Not measured yet
Needs you
Nothing yet
Features landed
Beyond the code
Everything around the code, too.
From the first customer call to the incident at three in the morning, Swarmli covers the whole life of a difficult project — not just the part where code gets typed.
Concept workshops
Join the customer call. Leave with a clickable prototype.
Swarmli listens, asks the questions you forgot, maps the systems involved and builds the prototype while you talk.
- Client Our field teams lose signal in the basements.
- You So the checklist has to work offline?
- Client Yes — and sync the photos later.
Offline checklistsPhoto syncManager overview
offline
System map
Every system, every gap.
Unknowns get a best-guess assumption at once, so work never waits for an answer.
Voice
Talk to your swarm.
On a walk or on the drive in: steer every agent with your voice.
“Put ACM-61 on two agents and ship it by noon.”
Self-healing production
Incidents fix themselves.
An alert becomes a ticket, a fix, a verified merge — before anyone is awake.
03:12 alert03:31 fix merged
Targets
Performance that holds.
Set a bar once. Every merge proves it got no worse.
Swarm memory
It learns how your team builds.
Conventions, decisions and taste — remembered across every project and every agent.
Svelte 5 runesForms with valibotNo barrel filesMoney in centsTests next to codeGerman UI copy
Client portal
Docs, changelog and forum on your domain.
Written by the swarm as it ships, read by your customers.
docs.acme.com/changelog
NEWUsage-based billing
NEWOffline checklists
NEWFaster event tables
Price estimates
Quote it before you build it.
Hours and a price range from the projects you already delivered.
€ 18–24k 160–210 h · from 7 past offers
The creator
One builder. A whole swarm.
Creator of SwarmliThomas Dallinger
Software solution architect and team lead at Deckweiss.
- CCC Classic · 1st place
- Team lead · Deckweiss
- Jugend Innovativ award
Be first in the swarm.
Swarmli opens step by step — for solo builders and whole teams alike. Leave your e-mail and you’ll hear the moment it’s your turn.
Investor or design partner? Talk to the creator