eve-software-factory-template vs marketing-team-eve-template
Two of the top agent backends, side by side: score, setup, license, activity and what each review found.
eve-software-factory-template
eve pipeline that turns GitHub or Linear issues into reviewed draft PRs
marketing-team-eve-template
eve lead agent delegating to five marketing specialists with approval gates
| What we compare | eve-software-factory-template | marketing-team-eve-template |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 46, known | 26, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 35, patchy | 28, weak |
| Easy to run | 67, easy | 67, easy |
| Agent-ready | 70, partly | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 1.2k | 450 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Sep 2026 | Aug 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
eve-software-factory-template
An eve pipeline named Foreman: label an issue factory, @mention it, or delegate from Linear, and four agents (classifier, analyst, implementer, reviewer) each run in their own sandbox and end with a draft pull request on FACTORY_REPO. The reviewer sees only the pushed branch, a factory brain keeps notes about your repo between runs, and it deploys to Vercel with GitHub and Linear connectors. For teams piloting agent-written PRs with human merge.
Who it is for: Teams piloting agent-written pull requests with human merge
Strengths
- Reviewer is isolated from the implementer; verdicts are made against the real diff
- Six entry points including red-CI self-repair on factory branches only
- Local dev TUI treats runs as untrusted; GitHub writes wait for approval
- Separate docs site; CLAUDE.md and AGENTS.md included
Weaknesses
- Tied to eve, Vercel Connect, Vercel Sandbox and Vercel Blob
- No model provider named in the README; model access comes through the Vercel stack
- No tests listed
- First task fails if the GitHub App cannot reach FACTORY_REPO; the error surfaces late
- TypeScript, eve, ai-sdk
- Needs vercel, github-app-connector, linear-connector, vercel-blob
- GitHub template
- env example file
marketing-team-eve-template
An eve project where a lead agent briefs one of five specialists (product marketing, content, social, SEO, email) and returns their output as Notion pages, Typefully drafts or Resend campaigns through MCP connections. A shared brand context document in Vercel Blob is the only state, sends and scheduled publishes pause for approval in Slack or the terminal, and models come through Vercel AI Gateway. For teams studying multi-agent delegation.
Who it is for: Teams studying multi-agent delegation with real tool writes
Strengths
- Approval matrix is enforced in connection tool lists, not only in prompts
- Each specialist is a directory; the lead routes on its description alone
- Remote agents let a specialist live in its own deployment
- CLAUDE.md, AGENTS.md and architecture docs included
Weaknesses
- Needs Notion, Resend and Slack connectors via Vercel Connect plus a Typefully key
- Tied to eve, Vercel AI Gateway, Blob and Sandbox
- No tests; pnpm validate covers lint and typecheck
- No .env.example
- TypeScript, eve, ai-gateway, ai-sdk
- Needs vercel-connect, notion, resend, slack, typefully-api-key, vercel-blob, ai-gateway
- GitHub template