> For the complete documentation index, see [llms.txt](https://docs.term.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.term.finance/terminal-1-execution/workflows/deploy-a-new-market-factory.md).

# Deploy a new market (Factory)

Factory deploy lets you create a new Term Repo when you need custom loan parameters that are not available in an existing market. Each Term Repo is defined by fixed parameters, including maturity, loan token, collateral token, LTV, and collateral/risk configuration. If no existing Term Repo matches the terms you need, you can deploy a new one.

Factory deploy is constrained to assets supported by the protocol’s oracle configuration. The loan token and collateral token(s) must be onboarded into the oracle set; unsupported assets cannot be used to create a new market.

<div data-with-frame="true"><figure><img src="/files/JCVlRrrR5eMJTldQx0lh" alt="" width="375"><figcaption></figcaption></figure></div>

*Where to find factory deploy. In the Create Order flow, if you don’t see a market that matches your needs, use the “Deploy your own Term” link in the term picker.*

### When to use factory deploy

* A required market (maturity or token pair) does not exist.
* You need a distinct collateral/risk configuration for an existing token pair.

### Inputs

* Chain
* Maturity date
* Loan token (purchase token)
* Collateral token(s)
* Collateral ratio / collateral-risk parameters
* Any required deployment configuration surfaced by the UI

### What the route does (high level)

A factory deploy route generally:

* validates that the selected tokens are supported by the oracle,
* deploys the Term Repo (market) contract set via the factory,
* pairs/initializes the market so it is usable by the protocol and indexers,
* returns the new market address (repo servicer) and associated contract addresses.

### Common failure cases

* Token set is not oracle-onboarded.
* Incompatible market parameters.
* Required authorization for deployment is missing.
* Market initialization/pairing fails due to protocol configuration or chain conditions.

### What to review before signing

* Market definition (maturity, loan token, collateral token(s), collateral parameters).
* Oracle support for the selected assets.
* The resulting market address and where it will appear in the UI.