- Author
- dev-bot-be · sandbox sbx-7f3a
- Reasoning
- Rounding happened before currency conversion. Moved it after, per spec AC-3. Added 14 property-based tests across 6 currencies.
- Gates
- 412 testscoverage 87%review-bot: approvesec-bot: cleanlicences ok
- Cost
- 2 Delivery Credits · compute €3.40
Software, built by bots.Openly.
A software company made of AI agents, governed by humans who answer for every release. You see everything.
Most software shops use AI and don't tell you. We are AI, and we show you.
A company made of bots.
Declared on the label.
Not "AI-assisted". Not "our talented team". Bots write the code, the tests and the deploy scripts. A small group of humans sets the standards, checks the work and signs it. Radical transparency is not a feature we bolted on. It is the company.
We say it.
Every line, test and deployment is produced by bots. We put that on the contract, the invoice and the homepage.
Humans own the outcome.
Our people don't type code. They define "done", review the work and put their name on every delivery.
You can watch.
Every bot action is timestamped, attributable and visible to you, live. Export it for your auditors.
Results, not hours.
Hours were a proxy for value. We don't need proxies anymore. You pay for accepted work.
Four steps.
One signature.
A multi-bot pipeline with gates that don't get tired, don't skip tests and don't merge on Friday evening. The last gate is always a human.
- 01intake-bot
You ask.
A ticket, a backlog, a sentence. Intake Bot turns it into a spec with acceptance criteria. Ambiguity goes to a human, not into your code.
- 02architect · dev bots
Bots plan, build, test.
Tests first. Every task in an isolated sandbox, one branch per change. Anything structural needs a human nod.
- 03reviewer · qa · sec
Four eyes, two brains.
The Reviewer Bot runs on a different model from the one that wrote the code. QA and Security bots block merges below threshold.
- 04human gate
A human accepts.
Your named Delivery Manager reviews and signs. Nothing customer-facing ships, and nothing touches production, without a human.
Every pull request shows its working.
Reasoning summary, tests run, the review bot's verdict and the name of the human who accepted it. If something breaks later, you know exactly who did what, and why.
Ten bots.
Clearly labelled.
Each bot has one job, a narrow set of permissions and a token budget. None of them pretends to be human. All of them answer to one.
Turns requests into specs with acceptance criteria. Flags ambiguity early.
Proposes design and impact analysis. Humans approve anything structural.
Front end, back end, mobile, data. Isolated sandboxes, one branch per task.
Different model, different vendor. Reviews every line it didn't write.
Writes and runs the tests. Blocks merges below threshold. No exceptions.
SAST, DAST, dependency and licence scans, secrets detection.
CI/CD, infra-as-code, monitoring. Production needs a human gate.
Daily digests, weekly reports, a risk register that's actually current.
Compute budget per task and client. Stops token blow-ups before you pay for them.
Keeps the immutable activity log behind your dashboard.
Land with a Pack.
Expand to a Crew.
Fixed prices for outcomes. A fixed monthly line for ongoing work. You pay for accepted work, never for time.
No hourly rates. Ever.
Farm Assessment
Codebase and backlog audit. You get a report, a modernization map and a fixed quote. Credited against your first Pack.
Testing Pack
An agreed coverage target. Regression and E2E suites, wired into your CI. Flaky tests named and shamed.
MVP Pack
Fixed scope, 3 to 6 weeks, full code ownership. Internal tools and back-office apps welcome.
Modernization Pack
Framework upgrades, monolith to modules, PHP/Java/.NET. Before and after metrics on every unit.
Crew S
Keep it alive and moving.
- ~20 Delivery Credits / month
- Response within 1 business day
- 30-day bug fix warranty
- Human review on every release
- Monthly review
Crew M
Less than one developer. Designed to out-ship two.
- ~55 Delivery Credits / month
- QA + DevOps bots included
- 8 business-hour response SLA
- 60-day bug fix warranty
- Live Farm dashboard
Crew L
Your outsourced engineering floor.
- ~120 Delivery Credits / month
- 4h response · 1h critical, 24/7
- Security bot on every change
- Dedicated delivery lead
- 90-day bug fix warranty
What's a Delivery Credit? A normalised unit of accepted work. A small ticket is 1 credit, a medium feature is 3 to 5. The sizing guide is public, and unused credits roll over one month. No "FTE equivalents". No timesheets.
SLA detailsPilot-phase pricing. All figures are indicative "from" prices, excluding VAT, and will be validated with our first clients. Your final price comes as a fixed quote after a Farm Assessment. Pilots are paid, discounted and under NDA.
Watch it work.
Every client gets a live window into their farm: what each bot did, what it cost, and which human approved it. Agencies send timesheets. We send the log.
Every action, attributable
Timestamped, immutable, exportable for audits. Bots and humans in the same log.
Glass PRs
Reasoning, tests, review verdict and the human approver on every change.
Cost in the open
Credits used and compute spent, per task. No surprise invoices.
Monthly Farm Report
Throughput, quality metrics, incidents and cost trend. Written by a bot, signed by a human.
Is bot-written code actually good enough?
Every output passes tests written first, an independent review bot running on a different model, security scans, and human acceptance for anything customer-facing. Fixes come with a warranty.
Don't take our word for it: start with a small Pack and judge the output, not the pitch. We'll publish our acceptance and defect rates as soon as we have pilot data worth publishing.
What about the security of our code?
Isolated per-client sandboxes, least-privilege and short-lived credentials, an EU hosting option, and no training on your code (zero-retention model terms where available). Every action is in the audit log, and no bot gets production write access without a human gate.
No humans? Who do I call when it matters?
Your named Delivery Manager. A human. Bots do the work; a person owns your account, every release and every escalation. "Zero humans" would be a lie, and we're in the business of not lying.
Who owns the IP? Is AI-generated code even protectable?
You own it: full contractual assignment of every deliverable. We scan licences to keep open-source contamination out, and we document the human direction, architecture decisions and acceptance behind each delivery. That record matters under EU and Italian copyright rules, and we keep it for you.
What happens when a bot makes a mistake?
It will. So do humans. That's why there are gates, warranties and insurance, and a log that shows exactly what happened, who approved it and how we fixed it. We write post-mortems in the open.
Isn't this just Devin with a sales team?
Tools need you to drive them, which means you still need the developer you didn't want to hire. We take responsibility for the result: a multi-bot process, SLAs, warranties and human governance. You hire us instead of hiring someone to operate the tools.
Aren't you killing developer jobs?
The work is changing either way. We chose to be honest about it rather than hide it behind "our talented team". Our humans do the higher-value part: architecture, quality and judgment. We never mock developers. The joke is on opacity, not on people.
Hire a farm.Keep your weekends.
Start with a paid pilot: one Pack, a fixed price, and a live view of every bot on your project.
or write to hello@swarmjar.com · a human answers