# What is the difference between a bespoke and a packaged factory?

A bespoke software factory is assembled by a team from its own rules and checks, while a packaged software factory is bought as a product and configured.

Last updated November 19, 2026, 8 min read

## Learning objectives

After reading this article you will be able to:

-   Define bespoke and packaged software factories
-   Compare what each one gives a team
-   Choose which parts to build or buy

## Related content

-   [What is a software factory?](https://specstory.com/learning/software-factories/software-factory)
-   [Should you build your own software factory?](https://specstory.com/learning/software-factories/build-or-buy-a-software-factory)
-   [Examples of software factories](https://specstory.com/learning/software-factories/software-factory-examples)
-   [What is a software factory process?](https://specstory.com/learning/software-factories/software-factory-process)

## What is the difference between a bespoke and a packaged factory?

A bespoke and a packaged software factory differ in who assembles the pipeline. A team puts a bespoke factory together itself, from its own rules, queue, agent workflows, and checks. A vendor builds a packaged factory and sells it as a product that the team configures.

A [software factory](https://specstory.com/learning/software-factories/software-factory) is a repeatable process in which [coding agents](https://specstory.com/learning/ai-coding/coding-agent) take work from a queue, build it, check it, and ship it. The stages and their order are the [factory process](https://specstory.com/learning/software-factories/software-factory-process).

A factory can mix the two kinds. A team that builds its own still buys its coding agent, and a team that buys one still writes the parts that describe its product. In both cases, some stage has to run the finished software and report evidence, and the team decides what that stage checks.

Diagram: Who supplies each part of a bespoke and a packaged software factory

Only the middle layer changes hands. The rules and the checks stay the team's own work in both kinds of factory.

## What is a bespoke software factory?

A bespoke software factory is a software factory that a team assembles for its own product, from a rules file, a queue, agent workflows, and its own checks. A custom software factory is the same thing. The team writes four parts:

-   **Rules file.** A file in the repository tells each agent what it must and must not do.
-   **Queue.** A list holds the work that agents take next, e.g. a Markdown file with one line per change.
-   **Agent workflows.** A script runs a fixed sequence of agents for each change.
-   **Checks.** The team's tests run on each change, and a separate agent starts the software and tries the change.

A bespoke factory can start small, with those four parts and one coding agent. The team owns each stage and can change a rule the day a problem shows up. The cost is upkeep, because the team also maintains the infrastructure.

The [software factory examples](https://specstory.com/learning/software-factories/software-factory-examples) include companies that built their own.

## What is a packaged software factory?

A packaged software factory is a product that supplies the pipeline, the agent runners, and the review steps of a software factory. A team configures it for its own repositories. Such a product is also called a software factory platform.

A packaged factory can supply five things:

-   **Runtime.** The product starts [background coding agents](https://specstory.com/learning/ai-coding/background-coding-agents), usually in the vendor's [sandboxes](https://specstory.com/learning/environments/ai-sandbox), and keeps a log of each run.
-   **Intake.** Work arrives from the tools a team already uses, e.g. a message in a chat channel.
-   **Default pipeline.** A sequence of stages exists before the team writes one.
-   **Measurement.** A dashboard counts runs and costs, and some products grade finished runs with a large language model (LLM), a setup called [LLM-as-a-judge](https://specstory.com/learning/verification/llm-as-a-judge).
-   **Governance.** Access roles and an audit trail are available in the product.

Three products show the range, and each supplies different parts. [Warp's page](https://www.warp.dev/factories) presents Warp Factories as infrastructure, and lists its parts under the heading "The factory infrastructure you'd build yourself." Factory, a company that sells one, describes a software factory in [its announcement](https://factory.com/news/software-factory) as a loop in which changes are "built, tested, reviewed, secured, shipped, and monitored." The page for [8090 Software Factory](https://www.8090.ai/software-factory) calls it "The AI-native software development control plane."

The products differ in which agent does the building. In its announcement, Factory calls its agents Droids. Warp's page says its product accepts "any MCP-capable coding agent," that is any agent that uses the [Model Context Protocol](https://specstory.com/learning/ai-coding/model-context-protocol) (MCP). The page for 8090 Software Factory says its work orders "are executed by agents inside Cursor, VS Code, or Claude Code."

## When should a team use a bespoke or a packaged factory?

Here is an illustrative example. Acme Co. sells furniture online. Its 6 developers want agents to work from the issue tracker, and nobody has time to build sandboxes. Acme buys a packaged factory and writes its own acceptance criteria.

A developer files the request "Let customers edit their delivery address during checkout." The change moves through five steps:

1.  The factory takes the issue from Acme's tracker and plans the change.
2.  A coding agent changes the checkout code in a sandbox, and Acme's test suite passes.
3.  A verification step starts the store with the commands that Acme documented.
4.  The step follows Acme's criteria, and one says the cart keeps its 2 items when the address changes.
5.  The step reports a failed criterion with a screenshot. The address saved, but the cart emptied.

The package supplied the intake, the sandbox, and the pipeline. The check found the bug because Acme had written what checkout should do.

A packaged factory fits a team that needs many agents running soon and has nobody free to build the infrastructure. A bespoke factory fits a team whose process is specific to its product, or that wants to change any stage itself. The [build or buy](https://specstory.com/learning/software-factories/build-or-buy-a-software-factory) page covers that decision.

This example is simplified. A real team would also try both kinds on a few changes.

## Can a bespoke and a packaged factory be used together?

A bespoke and a packaged factory can be used together, and a bought factory needs bespoke parts to work. Some packaged factories can run a step that uses the finished app, a form of [runtime verification](https://specstory.com/learning/verification/runtime-verification). [Warp's documentation](https://docs.warp.dev/factories/use-cases/computer-use-verification/) describes a worker that "builds and starts the app from the pull request, then uses Computer Use to test it as a user would." Its prerequisites include "Acceptance criteria naming the visible states and interactions to verify."

Six parts stay the buyer's own work:

-   **Acceptance checks.** The team writes or approves what the finished software should do, in terms a checker can observe.
-   **A way to run the product.** For its Missions feature, [Factory's documentation](https://docs.factory.com/missions/overview) says "your codebase needs an automated, scriptable way to exercise the app the way a user would."
-   **Tests.** The package runs the team's own test suite in continuous integration (CI), so the limits of [CI for coding agents](https://specstory.com/learning/ci-cd/ci-for-coding-agents) still apply.
-   **Standards.** The team writes its rules files and its [agent skills](https://specstory.com/learning/ai-coding/agent-skills).
-   **The definition of the factory.** The team chooses the stages, their order, and where a person approves.
-   **The release decision.** The team decides what merges and ships. Warp's page says "merge is always yours."

A verification step in a package checks the criteria it has, so the team should write those criteria or approve them. A change of vendor means rebuilding the runtime and the intake. The parts a team wrote can live in its repository, so they move with the team.

## How do bespoke and packaged factories compare?

The two kinds differ on these attributes:

| Attribute | Bespoke factory | Packaged factory |
| --- | --- | --- |
| Who assembles it | The team that uses it | A vendor, and the team configures it |
| Starting point | A rules file, a queue, and one workflow | Runtime, intake, and a default pipeline |
| Infrastructure | The team builds and maintains it | The vendor supplies it |
| Process | The team writes each stage | The team edits the vendor's default |
| Measurement and governance | Added when the team needs them | Included in the product |
| Main cost | Engineering time and tokens | Fees, tokens, and setup time |
| Acceptance checks | Written by the team | Written or approved by the team |
| Release decision | The team's | The team's |

The last two rows stay with the team. Which kind costs less depends on how much infrastructure the team would otherwise build.

## How can a team check what a packaged factory ships?

A report from a packaged factory covers what its own stages tried. Write the acceptance criteria yourself, so the stages check what your product should do. Then add a [check before the merge](https://docs.specstory.com/runstory/workflows/merge-gate) that runs the finished software from outside the factory's own agents.

RunStory checks your software by running it. RunStory independently runs the software against your change and returns evidence to the coding agent. Your team keeps the final release decision.

[Join the RunStory alpha →](https://specstory.com/runstory#alpha)

## FAQs

### What is a software factory platform?

A software factory platform is another name for a packaged software factory. The product supplies the pipeline, the agent runners, and the review steps, and a team configures it for its own repositories.

### Which companies sell packaged software factories?

Three companies whose products carry the words software factory are Warp, a company named Factory, and the company 8090. Their products are Warp Factories, Factory, and 8090 Software Factory.

### Does a packaged factory verify the software it builds?

A packaged factory can verify the software it builds when the team supplies the means. Some products can run a step that starts the app and tests it as a user would, against acceptance criteria that the team supplies.

### Can a team move from a packaged factory to a bespoke one?

A team can move from a packaged factory to a bespoke one. The parts the team wrote can live in its repository, so they move with it. The runtime and the intake have to be rebuilt.

### Is a bespoke software factory cheaper than a packaged one?

A bespoke software factory costs engineering time to build and maintain, while a packaged one costs fees and setup time. Which is cheaper depends on how much infrastructure the team would otherwise build.

---

Source: [Bespoke vs. packaged software factory | SpecStory](https://specstory.com/learning/software-factories/bespoke-vs-packaged-software-factory)
