A hosted multi-agent software-delivery platform where an agent its maker calls a Droid takes a task from the terminal, an IDE, a browser or Slack and returns a code change to review.
Our description, from the vendor's documentation, as of 2026-09-23.
Runs onThe places the vendor's own pages say the product runs: your machine, a container environment you run, or a cloud service the vendor runs. It is not a limit.
Models runWhere the vendor's own pages say the product's models run, not a limit: your machine, a container environment you run, the model company's cloud (servers of the company that makes or serves the model), or a cloud provider's model service. For a cloud, read the data and compliance lines of the company running it, linked by its name.
Several providers in one sessionOne session can use models from different providers, for example one agent on one maker's model and another on a second maker's. Switching the single model for the whole session does not count on its own. A tool that is itself a gateway or library routing to the providers its page names counts.
Several endpoints built inThe tool itself can hold more than one provider or address, so nothing has to sit in front of it to reach different providers.
Local and cloud togetherA local model (on your machine or in a container environment you run) and a cloud model (in its model company's cloud or a cloud provider's model service) can both be used in the same session or setup.
Use a local model: How to set it up(docs.factory.com page, read 2026-10-22) Settings the guide names: customModels, baseUrl, provider, apiKey.
Use a local and a cloud model together: How to set it up(docs.factory.com page, read 2026-10-22) Settings the guide names: customModels, provider, model, displayName.
Hold several endpoints in the product: How to set it up(docs.factory.com page, read 2026-10-22) Settings the guide names: customModels, baseUrl, displayName, provider.
Same role (harness / agent client) at the same layer (Coding agents and assistants). Up to 4 others, in alphabetical order; nothing is ranked.
Product
Several providersOne session can use models from different providers, for example one agent on one maker's model and another on a second maker's. Switching the single model for the whole session does not count on its own. A tool that is itself a gateway or library routing to the providers its page names counts.
Several endpointsThe tool itself can hold more than one provider or address, so nothing has to sit in front of it to reach different providers.
Model on your machineThe tool can use a model running on your own computer, for example through Ollama, LM Studio, oMLX or llama.cpp.
Local and cloudA local model (on your machine or in a container environment you run) and a cloud model (in its model company's cloud or a cloud provider's model service) can both be used in the same session or setup.
Words in the cells: YesA page we read says so., PartlyA page says part of it, for example separate models per agent without saying the providers can differ., Via a proxyOnly with a proxy, or a local server that imitates a cloud provider's interface, in front of the tool., NoA page we read says the product does not support it., ClaimedA vendor page says so on a marketing or overview page, and we found no guide showing how to set it up., Not foundWe read pages for it and found nothing there. It says nothing about whether the product has the feature., n/aThe question does not apply to the product, for example because it is a model server and not a tool that connects to models., BlankNothing is published for it yet.
Data and compliance
Compliance: For Factory, SOC 2 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 27001:2022 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 42001 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); HIPAA BAA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); DPA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); for Droid, SOC 2 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 27001:2022 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 42001 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); HIPAA BAA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); DPA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.).
Data: For Factory, training use only under a conditionEvery sentence found holds only under a condition, such as a setting or a signed agreement.; default retention and data residency stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; zero-retention option not stated on the pages readWe read a page that could answer and found no sentence that does. It says nothing about what the maker does.; for Droid, training use only under a conditionEvery sentence found holds only under a condition, such as a setting or a signed agreement.; default retention and data residency stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; zero-retention option not stated on the pages readWe read a page that could answer and found no sentence that does. It says nothing about what the maker does..
Model and where it runs: Hosted by the maker; for Factory, model provider stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; where it can run only on some plans or optionsNothing found covers the product as a whole; what was found holds only for the plans, options or regions named. (Enterprise, Pro); for Droid, model provider stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; where it can run stated on the maker's pageA sentence on the maker's page answers it for this product..
Details: What the maker's own pages state, not a compliance determination, unverified after 2026-12-23: trust page, trust.factory.ai.
What the maker's own pages said on the dates shown, not a compliance determination.
Also covers
The vendor's own pages present these as parts or modes of this product, so each is described here and has no page of its own.
Factory AutoWiki
A feature of Factory that generates a structured wiki for a repository -- architecture overviews, module breakdowns, cross-linked pages -- and keeps it current as the code changes, rather than a one-time snapshot.
Our description, from the vendor's documentation, as of 2026-09-24.
Compliance: SOC 2 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 27001:2022 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); ISO/IEC 42001 (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); HIPAA BAA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.); DPA (company-wideThe mark rests on a sentence that names no product, so check on the page whether it covers this one.).
Data: Training use only under a conditionEvery sentence found holds only under a condition, such as a setting or a signed agreement.; default retention and data residency stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; zero-retention option not stated on the pages readWe read a page that could answer and found no sentence that does. It says nothing about what the maker does..
Model and where it runs: Hosted by the maker; model provider stated for the whole companyThe only sentence found is about the maker as a whole and names no product, so check on the page whether it covers this one.; where it can run only on some plans or optionsNothing found covers the product as a whole; what was found holds only for the plans, options or regions named. (Enterprise, Pro).
Details: What the maker's own pages state, not a compliance determination, unverified after 2026-12-23: trust page, trust.factory.ai.
What the maker's own pages said on the dates shown, not a compliance determination.
factory.com home page(the product's own site, from our list of products; not read for these lines)
The readings behind this page
Our summary of the vendor's pages as of the dates shown on each line (2026-09-24 to 2026-10-24); confirm on the vendor's page.
Models from different providers in one session
A Factory subagent (custom droid) has a model of its own, which it can inherit from the parent session or swap for another model tuned for the task. (docs.factory.com page, read 2026-10-22)
In a custom droid's model field, a BYOK custom model is named by the prefix custom: followed by the value of the model field in the user's config, for instance custom:gpt-4o-mini, and not by its display name. (docs.factory.com page, read 2026-10-22)
Factory's custom droids, its subagents, can inherit the parent session's model or run a different one suited to the task. (docs.factory.com page, read 2026-10-21)
Several endpoints, built in (no proxy)
Factory (Droid CLI) allows the customer to use their own OpenAI or Anthropic keys, or to connect to open source model providers, or to run models locally on their hardware. (docs.factory.com page, read 2026-10-22)
You add custom models to the customModels array in the ~/.factory/settings.json file. (docs.factory.com page, read 2026-10-22)
Factory (Droid CLI) lets the customer run models on their own hardware using an OpenAI-compatible server, and then point baseUrl at it. (docs.factory.com page, read 2026-10-21)
A model on your machine
You run models on hardware you own, using an OpenAI-compatible server, and set baseUrl to point at it. (docs.factory.com page, read 2026-10-22)
Local and cloud in one session
Custom Models in /model show saved models, which are labeled with their displayName. (docs.factory.com page, read 2026-10-22)
Factory's page says the Droid CLI and its desktop app, both of which read the local settings.json, offer personal custom models, and that these models are absent from the hosted web or mobile platforms of Factory. (docs.factory.com page, read 2026-10-22)
What a local model must meet
Factory's article says a good chat reply from a model endpoint does not show that it copes with tool calls, with a longer context, or with repeated exchanges. (factory.com page, read 2026-10-23)
Factory's custom-models page says that for a local Ollama server the context window should be raised to 32k or more, and gives starting the server with OLLAMA_CONTEXT_LENGTH=32000 as an example. (docs.factory.ai page, read 2026-10-21)
Model Size Consideration : Agentic coding tasks show significantly lower performance for models with under 30 billion parameters. (docs.factory.ai page, read 2026-10-21)
Plan, policy and billing
Enterprise Controls and Managed Settings restrict provider access, base URLs, and custom models at the org level. (docs.factory.ai page, read 2026-10-21)
A separate model for planning and for doing
Factory's DeepSeek article says Factory lets you switch models for each task instead of tying you to one provider. (factory.com page, read 2026-10-23)
Factory's GLM article says that in Missions, where an orchestrator hands work to worker and validator agents, GLM can take the worker role, set through --worker-model glm-5.2, and a stronger model can do the validation. (factory.com page, read 2026-10-23)
Works with other products
Factory (Droid CLI) connects to OpenRouter, Fireworks, Together AI, Ollama, and vLLM, as well as most open-source providers. (docs.factory.com page, read 2026-09-24)
About the product
Factory's bring-your-own-key page says the Droid CLI accepts the user's own OpenAI or Anthropic keys, can reach any provider of open-source models, and can run models on the user's own local hardware. (docs.factory.com page, read 2026-10-24)
Our reading of vendors' pages, as of the dates shown. Confirm on the vendor's page before relying on any line that cites it. To report an error write to report@crinaro.ai