# Software Factory Agent Templates (Humans Still Merge)

> PR review, flakes, Sentry drafts, Linear triage — agent templates for eng teams. Humans still read and merge. jurniti Software Factory collection.

- Published: 2026-07-28 · Updated: 2026-07-28 · jurniti
- Canonical: https://www.jurniti.com/blog/software-factory-agent-templates

Engineering agents that "ship while you sleep" are a great demo and a terrible ops model. Merge is a judgment call. Security is a judgment call. **Humans still merge.**

The [Software Factory collection](/templates/collections/software-factory) is a gallery of agent templates for that reality: PR review, flake hunting, Sentry → draft PR, Linear triage, release hygiene — running in Firecracker microVMs, not in a shared laptop session.

## What "software factory agent templates" means here

Not a framework. Not a monorepo generator.

A **template** is a forkable snapshot of an agent setup: harness, skills, and workflow for a concrete eng job. You pay, jurniti provisions a microVM, you customize. Public templates are free to browse; the running agent is a paid box.

## Anti-lights-off is the product pitch

If a template promises unattended merges into `main`, it is the wrong collection. Software Factory cards are written so operators:

1. Draft the review or PR
2. Leave evidence a human can read
3. Stop before production authority

That is not a limitation. That is how maintainable teams actually use agents in 2026.

## Departments and tools

The catalog is split by **department** (product eng, frontend, backend, QA, DevOps, SRE, security, code review, DX, …) and **tool shelves** (GitHub, Linear, Sentry, Vercel, Actions, Slack, Notion, Datadog, Cursor, Codex, …).

Pick the job, then the system of record you already use. Do not invent a second stack just to run an agent.

Live index: [Software Factory templates](/templates/collections/software-factory).

## Why a microVM for eng operators

Eng agents touch:

- Private repos
- CI secrets
- Incident context
- Model keys

A shared Docker density host is the wrong default for that blast radius. Each jurniti agent gets its own Firecracker microVM (KVM boundary). Boot is ~124ms; provisioning after payment is still a few minutes.

## Related reading

- [GTM templates that never auto-send](/blog/gtm-agent-templates-that-never-auto-send) — same human-gate philosophy for sales ops
- [Self-host Langfuse for AI agents](/blog/self-host-langfuse-for-ai-agents) — observability sidecar when traces matter
- [Claude Code security](/blog/claude-code-security) — isolation for agentic coding

## Start

Open [Software Factory](/templates/collections/software-factory), fork a public template, paste keys, and keep the merge button under human control.

## Frequently asked questions

### What is the Software Factory collection?

A jurniti template gallery for engineering operators — product eng, frontend, backend, QA, DevOps, SRE, security, code review, and developer experience — with tool shelves for GitHub, Linear, Sentry, Vercel, Actions, Slack, Notion, Datadog, Cursor, Codex, and more. Each template forks into a paid microVM.

### Do these agents auto-merge PRs?

No. The Software Factory positioning is anti-lights-off: agents draft reviews and PRs; humans still read and merge. Templates that imply unattended production merges are out of scope for this collection.

### Which harnesses do Software Factory templates use?

Whatever the template was captured with — often Claude Code, Codex, OpenCode, or other coding harnesses on jurniti. The collection is about the job, not a single model brand.

### How is this different from a CI bot?

CI bots run fixed checks. These templates are full agent microVMs that can research, draft, and open PRs with isolation and BYOK. CI still owns the gate; the human still owns the merge.

### Is there a free trial?

No free trial and no free tier. Plans start at $25/mo with a 30-day money-back guarantee on the first purchase.