Factory
Desktop app for Mac, Windows and Linux. Agents run on your computer, on your own server or in the vendor's cloud.
Product websitefactory.ai Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Yes
- Phone
- Phone browser
- Command line
- Yes
- Agents
- Not listed
- Your subscription
- Works with your own plan
- Agents run
- On your computer, on your own server and in the vendor's cloud
- Laptop closed
- Keeps going
- Isolation
- Worktree
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Yes
- Built-in issues
- Not listed
- Pull requests
- Yes
- Review screen
- Yes
- Team
- Shared sessions, roles and SSO
- Self-hosting
- Yes
- Licence
- Custom terms
- Price from
- Free
- How it charges
- Free plan, subscription, per seat, usage-based, per machine or compute and bring your own key
- Paid plans from
- $11–20/month
Receipts
- Checked
- · oldest answer 2026-11-07
- Findings
- 42 published · 35 cross-checked by a second agent · read them all
- Sources
- 24 public pages on 3 sites: docs.factory.ai, docs.factory.com, factory.com
- Screenshot
- docs.factory.ai, retrieved · first party docs · shows appearance, not capability
- Data
- /products/factory.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
Source and scope for Where you use itAccounts and subscriptions
The recurring Free plan supports native ChatGPT and GitHub Copilot sign-in, OpenRouter, provider API keys and custom endpoints. Enterprise airgap model endpoints remain a separate deployment scope.
Source and scope for Accounts and subscriptionsWhere agents run
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
Source and scope for Where agents runHow work is kept apart
A new worktree creates its own branch from a selected base by default. Factory-managed worktrees isolate each session checkout on local machines or connected Droid Computers. Worktrees have separate working files but share Git history.
Source and scope for How work is kept apartParallel work
The orchestrator divides areas among agents working in parallel.
Source and scope for Parallel workScheduled runs
Factory App Automations supports cron-style recurring runs. Slack messages, GitHub events and HTTP webhooks start Droid sessions; GitHub automations run in GitHub Actions.
Source and scope for Scheduled runsGit and pull requests
Workstreams track PRs opened or worked on by the orchestrator and agents. PR tabs show comments and review threads. The PRs tab groups Open, Draft, Closed and Merged requests.
Source and scope for Git and pull requestsLicence and source
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
Source and scope for Licence and sourcePrice
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | Yes |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | Yes |
| CLI | Yes |
| Coding agents: Claude Code | Unknown |
| Coding agents: Codex | Unknown |
| Coding agents: Cursor Agent | Unknown |
| Coding agents: Gemini CLI | Unknown |
| Coding agents: OpenCode | Unknown |
| Coding agents: Pi | Unknown |
| Coding agents: Grok | Unknown |
| Coding agents: Aider | Unknown |
| Coding agents: Antigravity | Unknown |
| Use my subscription | Yes |
| Where agents run: On your computer | Yes cross-checked |
| Where agents run: On your own server | Yes cross-checked |
| Where agents run: In the vendor's cloud | Yes cross-checked |
| Workspace isolation: Git worktree | Yes cross-checked |
| Workspace isolation: Container | Unknown |
| Workspace isolation: VM or microVM | Unknown |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes cross-checked |
| Native issue tracking | Unknown |
| Unattended triggers | Yes cross-checked |
| Shared prompting | Yes |
| Team roles | Yes cross-checked |
| SSO | Yes cross-checked |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes cross-checked |
| Product license: Apache-2.0 | No. Custom terms cross-checked |
| Product license: MIT | No. Custom terms cross-checked |
| Product license: GPL-3.0 | No. Custom terms cross-checked |
| Product license: GPL-3.0-or-later | No. Custom terms cross-checked |
| Product license: AGPL-3.0 | No. Custom terms cross-checked |
| Product license: AGPL-3.0-or-later | No. Custom terms cross-checked |
| Product license: Elastic License 2.0 | No. Custom terms cross-checked |
| Product license: Custom terms | Yes. Custom terms cross-checked |
| Product license: Proprietary | No. Custom terms cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Unknown |
| Free access | Yes |
| Starting price: Free | Yes. Free |
| Starting price: Up to $20/month | No. Free |
| Starting price: $21–40/month | No. Free |
| Starting price: $41–100/month | No. Free |
| Starting price: Over $100/month | No. Free |
| Starting price: Contact for pricing | No. Free |
| Pricing model: Free, no paid plan | No |
| Pricing model: Free plan | Yes |
| Pricing model: Subscription | Yes |
| Pricing model: Per seat | Yes |
| Pricing model: Usage-based | Yes |
| Pricing model: Per machine or compute | Yes |
| Pricing model: Bring your own key | Yes |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | No. $11–20/month |
| Paid plans from: $10 or less/month | No. $11–20/month |
| Paid plans from: $11–20/month | Yes. $11–20/month |
| Paid plans from: $21–40/month | No. $11–20/month |
| Paid plans from: $41–100/month | No. $11–20/month |
| Paid plans from: Over $100/month | No. $11–20/month |
| Paid plans from: Contact sales | No. $11–20/month |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes cross-checked |
| Open-source license | No. Custom terms cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Yes. $11–20/month |
| Paid plan up to $40/month | Yes. $11–20/month |
| Any phone client | Yes |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Desktop os: Native Linux x64/ARM64 App install script or .deb package is now linked alongside Mac and Windows downloads.
- Mobile apps: The complete surface list offers browser-based Web & Mobile rather than native iOS or Android apps.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: The complete product-surface list includes Factory App downloads for macOS, Windows and Linux x64/ARM64, Droid CLI, and Web & Mobile through any browser at app.factory.ai. The mobile path explicitly needs nothing installed; no native phone app is offered in that list.
Web client: Yes
Web client
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Desktop os: Native Linux x64/ARM64 App install script or .deb package is now linked alongside Mac and Windows downloads.
- Mobile apps: The complete surface list offers browser-based Web & Mobile rather than native iOS or Android apps.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: The complete product-surface list includes Factory App downloads for macOS, Windows and Linux x64/ARM64, Droid CLI, and Web & Mobile through any browser at app.factory.ai. The mobile path explicitly needs nothing installed; no native phone app is offered in that list.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Desktop os: Native Linux x64/ARM64 App install script or .deb package is now linked alongside Mac and Windows downloads.
- Mobile apps: The complete surface list offers browser-based Web & Mobile rather than native iOS or Android apps.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: The complete product-surface list includes Factory App downloads for macOS, Windows and Linux x64/ARM64, Droid CLI, and Web & Mobile through any browser at app.factory.ai. The mobile path explicitly needs nothing installed; no native phone app is offered in that list.
Phone access: Phone browser: Yes
Phone access: Phone browser
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
CLI: Yes
CLI
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
Use my subscription: Yes
Use my subscription
Typed value: Yes.
The recurring Free plan supports native ChatGPT and GitHub Copilot sign-in, OpenRouter, provider API keys and custom endpoints. Enterprise airgap model endpoints remain a separate deployment scope.
- Agent subscriptions: Free explicitly permits signing in with ChatGPT or GitHub Copilot.
- Api accounts: Free explicitly permits own API keys or a custom endpoint.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
Where agents run: On your computer: Yes cross-checked
Where agents run: On your computer
Typed value: Yes.
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Local: Workstream machines may be the local computer, configured remote computers or fresh cloud machines.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosted, hybrid, provisioning, payer, resources, region, expiry. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
Where agents run: On your own server: Yes cross-checked
Where agents run: On your own server
Typed value: Yes.
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Byo remote: User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature.
- Managed cloud: Droid Computers are Factory-managed persistent remote environments.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosted, hybrid, provisioning, payer, resources, region, expiry. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
Where agents run: In the vendor's cloud: Yes cross-checked
Where agents run: In the vendor's cloud
Typed value: Yes.
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Byo remote: User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature.
- Managed cloud: Droid Computers are Factory-managed persistent remote environments.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosted, hybrid, provisioning, payer, resources, region, expiry. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
Workspace isolation: Git worktree: Yes cross-checked
Workspace isolation: Git worktree
Typed value: Yes.
A new worktree creates its own branch from a selected base by default. Factory-managed worktrees isolate each session checkout on local machines or connected Droid Computers. Worktrees have separate working files but share Git history.
- Branch: A new worktree creates its own branch from a selected base by default.
- Worktree: Factory-managed worktrees isolate each session checkout on local machines or connected Droid Computers.
- Code separation: Worktrees have separate working files but share Git history.
- Unknown after the targeted first-party documentation, release and repository pass: checkout, container, vm, os_sandbox, filesystem, process, network, secrets, security_boundary. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory creates separate Git checkouts and branches, with ephemeral or persistent lifecycles and setup profiles. Non-Git folders can start without worktrees; isolation is file separation, not a security sandbox.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
The orchestrator divides areas among agents working in parallel.
- Concurrent tasks: The orchestrator divides areas among agents working in parallel.
- Parallel work: first-party sources in this pass did not establish concurrent_sessions, quotas, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
Coordinator: Yes cross-checked
Coordinator
Typed value: Yes.
A lead orchestrator delegates to Droid sessions; each agent reports progress, blockers and results and can be opened directly. The orchestrator asks agents for updates and sends additional work. Agents report completion, blockers and changed assumptions to the orchestrator. Mission Control coordinates agents after a user-approved mission plan. Agents are grouped by Waiting on you, Working or Idle with latest activity. The orchestrator reuses agents for related work. /migrate starts a bounded job after human plan approval.
- Roles: A lead orchestrator delegates to Droid sessions; each agent reports progress, blockers and results and can be opened directly.
- Orchestration owner: Mission Control coordinates agents after a user-approved mission plan.
- Unknown after the targeted first-party documentation, release and repository pass: model_harness_effort, cross_harness, activation, authentication, retained_results. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
Factory App Automations supports cron-style recurring runs. Slack messages, GitHub events and HTTP webhooks start Droid sessions; GitHub automations run in GitHub Actions.
- Schedules: Factory App Automations supports cron-style recurring runs.
- Events: Slack messages, GitHub events and HTTP webhooks start Droid sessions; GitHub automations run in GitHub Actions.
- Unattended triggers: first-party sources in this pass did not establish recurring_tasks, completion_conditions, scheduler_location, overlaps, retries, client_independence. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
-
Finding: The legacy Software Factory overview now presents Automations, with scheduled, Slack, GitHub Actions and webhook triggers.
Shared prompting: Yes
Shared prompting
Typed value: Yes.
Slack delegation supports follow-up instructions in one active session thread or dedicated code channel. The code channel gives the team a shared place to instruct the same session; channel sessions run as the service account.
- Coprompting: Users in the active Factory Slack conversation send follow-up instructions into that session, including the team code channel.
- Permissions: Organization app permissions and Slack code-channel availability apply; DMs use personal identity and channels use the service account.
- First-party documentation review only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Finding: Factory receives follow-up messages/attachments in an active Slack session. A code channel is dedicated to one Factory session so the team can work in it; users send further instructions there. Channel sessions run as the service account; DMs run as the person. Code channels depend on Slack availability and app permissions.
Team roles: Yes cross-checked
Team roles
Typed value: Yes.
Owner, Manager and User have distinct organization permissions. Owners and Managers administer members. Business lists SSO and SAML/SCIM provisioning. SSO and directory synchronization map IdP groups to Factory roles. Directory membership changes propagate to Factory; end-to-end immediate session revocation was not tested.
- Organization roles: Owner, Manager and User have distinct organization permissions.
- Membership: Owners and Managers administer members.
- Provisioning: SSO and directory synchronization map IdP groups to Factory roles.
- Revocation: Directory membership changes propagate to Factory; end-to-end immediate session revocation was not tested.
- Unknown after the targeted first-party documentation, release and repository pass: project_roles, task_roles, unauthorized_access, plan_scope. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Owner controls the organization and billing. Manager administers members, settings and service accounts. User cannot override locked organization settings. SAML/OIDC and directory synchronization map groups to roles.
SSO: Yes cross-checked
SSO
Typed value: Yes.
Owner, Manager and User have distinct organization permissions. Owners and Managers administer members. Business lists SSO and SAML/SCIM provisioning. SSO and directory synchronization map IdP groups to Factory roles. Directory membership changes propagate to Factory; end-to-end immediate session revocation was not tested.
- Sso: Business lists SSO and SAML/SCIM provisioning.
- Unknown after the targeted first-party documentation, release and repository pass: project_roles, task_roles, unauthorized_access, plan_scope. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
Workstreams track PRs opened or worked on by the orchestrator and agents. PR tabs show comments and review threads. The PRs tab groups Open, Draft, Closed and Merged requests.
- Pull requests: Workstreams track PRs opened or worked on by the orchestrator and agents.
- Comments: PR tabs show comments and review threads.
- Product state: The PRs tab groups Open, Draft, Closed and Merged requests.
- Unknown after the targeted first-party documentation, release and repository pass: branches, worktrees, commits, ci_response, rebase, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
Review interface: Yes cross-checked
Review interface
Typed value: Yes.
The PRs tab lists each workstream PR with its checks and review activity. PR tabs offer Diff, Walkthrough and Validation views. The Conversation view shows PR description and comments.
- Pending reviews: The PRs tab lists each workstream PR with its checks and review activity.
- Change understanding: PR tabs offer Diff, Walkthrough and Validation views.
- Comments: The Conversation view shows PR description and comments.
- Unknown after the targeted first-party documentation, release and repository pass: evidence_navigation, request_changes, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
Product license: Apache-2.0: No. Custom terms cross-checked
Product license: Apache-2.0
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: MIT: No. Custom terms cross-checked
Product license: MIT
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: GPL-3.0: No. Custom terms cross-checked
Product license: GPL-3.0
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: GPL-3.0-or-later: No. Custom terms cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: AGPL-3.0: No. Custom terms cross-checked
Product license: AGPL-3.0
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: AGPL-3.0-or-later: No. Custom terms cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: Elastic License 2.0: No. Custom terms cross-checked
Product license: Elastic License 2.0
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: Custom terms: Yes. Custom terms cross-checked
Product license: Custom terms
Typed value: Yes. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Product license: Proprietary: No. Custom terms cross-checked
Product license: Proprietary
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
Enterprise Custom Deployments can run all of Factory inside the customer network using the dedicated airgap build. Airgap builds make no requests to Factory services during agent use; users configure models, MCP and other endpoints. Humans can download shared-folder documents or copy their contents. Humans upload files or folders as workstream references. Airgap Mode skips sign-in and does not require a Factory account.
- Self hosting: Enterprise Custom Deployments can run all of Factory inside the customer network using the dedicated airgap build.
- Vendor dependencies: Airgap builds make no requests to Factory services during agent use; users configure models, MCP and other endpoints.
- Account independence: Airgap Mode skips sign-in and does not require a Factory account.
- Unknown after the targeted first-party documentation, release and repository pass: formats, cancellation, history_portability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Enterprise custom airgap deployments run all Factory inside the customer network. The full local harness skips sign-in, sync, Factory telemetry and crash reporting. It uses configured model endpoints and an optional customer collector, with cloud features unavailable.
Free access: Yes
Free access
Typed value: Yes.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: Free: Yes. Free
Starting price: Free
Typed value: Yes. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: Up to $20/month: No. Free
Starting price: Up to $20/month
Typed value: No. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: $21–40/month: No. Free
Starting price: $21–40/month
Typed value: No. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: $41–100/month: No. Free
Starting price: $41–100/month
Typed value: No. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: Over $100/month: No. Free
Starting price: Over $100/month
Typed value: No. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Starting price: Contact for pricing: No. Free
Starting price: Contact for pricing
Typed value: No. Free.
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Ongoing free: The Free plan is $0/month and bring-your-own inference, not trial-only credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Pricing model: Free, no paid plan: No
Pricing model: Free, no paid plan
Typed value: No.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Pricing model: Free plan: Yes
Pricing model: Free plan
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Included usage: Paid plans use rolling 5-hour, 7-day and 30-day rate limits; numerical quota sizes are not fixed here.
- Credits: Extra Usage credits have a $10 minimum and no expiration.
- Overages: Extra Usage continues beyond included limits while enabled and funded.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Compute cost: Factory Standard Credits account for cloud-environment compute as well as model usage.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
Pricing model: Subscription: Yes
Pricing model: Subscription
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Pricing model: Per seat: Yes
Pricing model: Per seat
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Pricing model: Usage-based: Yes
Pricing model: Usage-based
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Included usage: Paid plans use rolling 5-hour, 7-day and 30-day rate limits; numerical quota sizes are not fixed here.
- Credits: Extra Usage credits have a $10 minimum and no expiration.
- Overages: Extra Usage continues beyond included limits while enabled and funded.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Compute cost: Factory Standard Credits account for cloud-environment compute as well as model usage.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
Pricing model: Per machine or compute: Yes
Pricing model: Per machine or compute
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Included usage: Paid plans use rolling 5-hour, 7-day and 30-day rate limits; numerical quota sizes are not fixed here.
- Credits: Extra Usage credits have a $10 minimum and no expiration.
- Overages: Extra Usage continues beyond included limits while enabled and funded.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Compute cost: Factory Standard Credits account for cloud-environment compute as well as model usage.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
Pricing model: Bring your own key: Yes
Pricing model: Bring your own key
Typed value: Yes.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Included usage: Paid plans use rolling 5-hour, 7-day and 30-day rate limits; numerical quota sizes are not fixed here.
- Credits: Extra Usage credits have a $10 minimum and no expiration.
- Overages: Extra Usage continues beyond included limits while enabled and funded.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Compute cost: Factory Standard Credits account for cloud-environment compute as well as model usage.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Model cost: Free supports own subscription/key inference; managed usage consumes credits.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
Paid plans from: No paid plan: No. $11–20/month
Paid plans from: No paid plan
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: $10 or less/month: No. $11–20/month
Paid plans from: $10 or less/month
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: $11–20/month: Yes. $11–20/month
Paid plans from: $11–20/month
Typed value: Yes. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: $21–40/month: No. $11–20/month
Paid plans from: $21–40/month
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: $41–100/month: No. $11–20/month
Paid plans from: $41–100/month
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: Over $100/month: No. $11–20/month
Paid plans from: Over $100/month
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plans from: Contact sales: No. $11–20/month
Paid plans from: Contact sales
Typed value: No. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Keeps going with laptop closed: Yes cross-checked
Keeps going with laptop closed
Typed value: Yes.
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Client disconnect: Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes.
- Other device continuation: Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosted, hybrid, provisioning, payer, resources, region, expiry. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Environment and managed Droid Computer agents continue when the laptop closes. Local agents stop when the desktop app quits; user remote computers must remain online.
Open-source license: No. Custom terms cross-checked
Open-source license
Typed value: No. Custom terms.
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Client license: Factory application software is governed by a limited custom internal-use license in Individual Terms.
- Server license: Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
Paid plan up to $20/month: Yes. $11–20/month
Paid plan up to $20/month
Typed value: Yes. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Paid plan up to $40/month: Yes. $11–20/month
Paid plan up to $40/month
Typed value: Yes. $11–20/month.
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Interval: At the 7 November check, Pro is $20/month, Plus $100/month, Max $200/month; Teams is $60/month per team plus $40/month per seat.
- Workspace fees: Teams has a separate $60 monthly team charge, with up to ten seats.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
Any phone client: Yes
Any phone client
Typed value: Yes.
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Browser: app.factory.ai provides browser sessions through cloud sync and Droid Computers.
- Mobile browser: The Web & Mobile section describes browser access rather than a native mobile app.
- Cli: Droid CLI installers cover macOS, Linux and Windows; npm and Homebrew options are listed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
factory:ACC-01: Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
factory:ACC-01
Factory App now offers macOS, Windows and Linux desktop installers. Droid CLI is separate. The complete Web & Mobile path uses a browser at app.factory.ai and needs nothing installed.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
-
Finding: The complete product-surface list includes Factory App downloads for macOS, Windows and Linux x64/ARM64, Droid CLI, and Web & Mobile through any browser at app.factory.ai. The mobile path explicitly needs nothing installed; no native phone app is offered in that list.
factory:ACC-03: The recurring Free plan supports native ChatGPT and GitHub Copilot sign-in, OpenRouter, provider API keys and custom endpoints. Enterprise airgap model endpoints remain a separate deployment scope.
factory:ACC-03
The recurring Free plan supports native ChatGPT and GitHub Copilot sign-in, OpenRouter, provider API keys and custom endpoints. Enterprise airgap model endpoints remain a separate deployment scope.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Enterprise custom airgap deployments run all Factory inside the customer network. The full local harness skips sign-in, sync, Factory telemetry and crash reporting. It uses configured model endpoints and an optional customer collector, with cloud features unavailable.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
factory:ACC-04: Non-Git folders can start sessions without a worktree. The worktree workflow requires a Git repository, not a hosted Git remote. The App creation wizard selects owner, provider, repository/setup options and optionally a Ready Environment, with live provisioning progress. cross-checked
factory:ACC-04
Non-Git folders can start sessions without a worktree. The worktree workflow requires a Git repository, not a hosted Git remote. The App creation wizard selects owner, provider, repository/setup options and optionally a Ready Environment, with live provisioning progress.
- Unknown after the targeted first-party documentation, release and repository pass: first_task_setup, hosted_git, prerequisite_guidance, byo_vps_onboarding. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
-
Finding: Factory creates separate Git checkouts and branches, with ephemeral or persistent lifecycles and setup profiles. Non-Git folders can start without worktrees; isolation is file separation, not a security sandbox.
factory:ACC-05: Droid CLI supports terminal use and headless exec; exact operation parity remains uncollected. droid computer list, ssh and port-forward are documented computer operations. cross-checked
factory:ACC-05
Droid CLI supports terminal use and headless exec; exact operation parity remains uncollected. droid computer list, ssh and port-forward are documented computer operations.
- Programmable access: first-party sources in this pass did not establish api, sdk, mcp_server, webhooks, authentication, stability. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
-
Finding: Factory offers Mac and Windows desktop installers, CLI installation on three OS families and browser access through session sync and remote computers.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
factory:PLAN-01: Automation starters include Ticket to PR and Error Triage; external tracker authority was not tested. cross-checked
factory:PLAN-01
Automation starters include Ticket to PR and Error Triage; external tracker authority was not tested.
- Intake and external tracker relationship: first-party sources in this pass did not establish local_creation, prompt_intake, external_import, authoritative_tracker, stable_ids, sync, supported_edits, external_roundtrips. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
-
Finding: The legacy Software Factory overview now presents Automations, with scheduled, Slack, GitHub Actions and webhook triggers.
factory:PLAN-02: /missions creates a plan with features, milestones and success criteria before approval. The orchestrator works with the user to agree the /migrate outcome and plan. Messages can add work or change direction within the existing workstream. cross-checked
factory:PLAN-02
/missions creates a plan with features, milestones and success criteria before approval. The orchestrator works with the user to agree the /migrate outcome and plan. Messages can add work or change direction within the existing workstream.
- Unknown after the targeted first-party documentation, release and repository pass: acceptance_criteria, revisions, implementation_links, restart_persistence. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
-
Finding: The orchestrator delegates to agents, briefs them, sends follow-up work, interrupts turns and collects results. Agents show waiting/working/idle states. /migrate requires an approved plan and displays progress.
factory:PLAN-03: Mission features are grouped into milestones; arbitrary hierarchy and dispatch enforcement were not tested. cross-checked
factory:PLAN-03
Mission features are grouped into milestones; arbitrary hierarchy and dispatch enforcement were not tested.
- Hierarchy, dependencies and evolving scope: first-party sources in this pass did not establish epics, blockers, readiness, enforcement, state_propagation, task_to_epic, identity_retention, workflow_constraints. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
factory:PLAN-04: The shared folder contains plans, findings and deliverables readable and writable by all agents across machines. cross-checked
factory:PLAN-04
The shared folder contains plans, findings and deliverables readable and writable by all agents across machines.
- Shared context and memory: first-party sources in this pass did not establish instructions, skills, memory, scope, provenance, correction, deletion, freshness, takeover_continuity. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
factory:PLAN-06: The documented native CVE Tasks tab has persistent task IDs and states, plans, PRs and a timeline, but is explicitly limited Private Preview. Publicly available native issue tracking elsewhere is unestablished.
factory:PLAN-06
The documented native CVE Tasks tab has persistent task IDs and states, plans, PRs and a timeline, but is explicitly limited Private Preview. Publicly available native issue tracking elsewhere is unestablished.
- First-party documentation review only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Finding: The native CVE-remediation Tasks tab has task IDs, states, plans, PRs, decisions and a timeline, distinct from the fix-droid session. The page explicitly marks it Private Preview with limited availability and requires contacting the account team. This does not establish publicly distributed native issue tracking.
factory:COORD-01: The orchestrator divides areas among agents working in parallel. cross-checked
factory:COORD-01
The orchestrator divides areas among agents working in parallel.
- Parallel work: first-party sources in this pass did not establish concurrent_sessions, quotas, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
factory:COORD-02: The workstream orchestrator assigns an area and brief to each agent. The orchestrator splits the goal into areas and starts the corresponding workers. cross-checked
factory:COORD-02
The workstream orchestrator assigns an area and brief to each agent. The orchestrator splits the goal into areas and starts the corresponding workers.
- Unknown after the targeted first-party documentation, release and repository pass: human_assignment, claims, queues, duplicate_prevention, ownership_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: The orchestrator delegates to agents, briefs them, sends follow-up work, interrupts turns and collects results. Agents show waiting/working/idle states. /migrate requires an approved plan and displays progress.
factory:COORD-03: A lead orchestrator delegates to Droid sessions; each agent reports progress, blockers and results and can be opened directly. The orchestrator asks agents for updates and sends additional work. Agents report completion, blockers and changed assumptions to the orchestrator. Mission Control coordinates agents after a user-approved mission plan. Agents are grouped by Waiting on you, Working or Idle with latest activity. The orchestrator reuses agents for related work. /migrate starts a bounded job after human plan approval. cross-checked
factory:COORD-03
A lead orchestrator delegates to Droid sessions; each agent reports progress, blockers and results and can be opened directly. The orchestrator asks agents for updates and sends additional work. Agents report completion, blockers and changed assumptions to the orchestrator. Mission Control coordinates agents after a user-approved mission plan. Agents are grouped by Waiting on you, Working or Idle with latest activity. The orchestrator reuses agents for related work. /migrate starts a bounded job after human plan approval.
- Unknown after the targeted first-party documentation, release and repository pass: model_harness_effort, cross_harness, activation, authentication, retained_results. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: The orchestrator delegates to agents, briefs them, sends follow-up work, interrupts turns and collects results. Agents show waiting/working/idle states. /migrate requires an approved plan and displays progress.
factory:COORD-04: Factory App Automations supports cron-style recurring runs. Slack messages, GitHub events and HTTP webhooks start Droid sessions; GitHub automations run in GitHub Actions. cross-checked
factory:COORD-04
Factory App Automations supports cron-style recurring runs. Slack messages, GitHub events and HTTP webhooks start Droid sessions; GitHub automations run in GitHub Actions.
- Unattended triggers: first-party sources in this pass did not establish recurring_tasks, completion_conditions, scheduler_location, overlaps, retries, client_independence. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
-
Finding: The legacy Software Factory overview now presents Automations, with scheduled, Slack, GitHub Actions and webhook triggers.
factory:COORD-05: The UI stops an individual agent turn. Humans can message the orchestrator or agent during active work. The Agents tab groups agents awaiting a human question or tool approval. cross-checked
factory:COORD-05
The UI stops an individual agent turn. Humans can message the orchestrator or agent during active work. The Agents tab groups agents awaiting a human question or tool approval.
- Unknown after the targeted first-party documentation, release and repository pass: pause, resume, notifications, escalation, visible_errors, chat_terminal_parity, retained_history. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: The orchestrator delegates to agents, briefs them, sends follow-up work, interrupts turns and collects results. Agents show waiting/working/idle states. /migrate requires an approved plan and displays progress.
factory:COORD-06: Agents are separate Droid sessions reporting to one workstream orchestrator. The Agents tab groups sessions waiting on the user. Opening an agent reveals its conversation, tools and changes. cross-checked
factory:COORD-06
Agents are separate Droid sessions reporting to one workstream orchestrator. The Agents tab groups sessions waiting on the user. Opening an agent reveals its conversation, tools and changes.
- Unknown after the targeted first-party documentation, release and repository pass: fleet_fixture, dependencies, workload, navigation_errors, fixture_mode. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: The orchestrator delegates to agents, briefs them, sends follow-up work, interrupts turns and collects results. Agents show waiting/working/idle states. /migrate requires an approved plan and displays progress.
factory:COORD-07: The guide recommends starting a new Mission for structured work rather than converting a long-running ordinary session. cross-checked
factory:COORD-07
The guide recommends starting a new Mission for structured work rather than converting a long-running ordinary session.
- Workflow flexibility and orchestration visibility: first-party sources in this pass did not establish quick_task, presets, natural_language, agent_configuration, in_run_changes, live_roles, retained_relationships, discoverability, auth_friction. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
factory:RUN-01: Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits. cross-checked
factory:RUN-01
Workstream machines may be the local computer, configured remote computers or fresh cloud machines. User-managed VPS, VMs and on-prem computers connect through the separate Remote Control feature. Droid Computers are Factory-managed persistent remote environments. Agents on environment computers or Factory-managed Droid Computers keep working after the controlling laptop closes. Remote work remains accessible while its execution host is online; local agents stop when the desktop app quits.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosted, hybrid, provisioning, payer, resources, region, expiry. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: Environment and managed Droid Computer agents continue when the laptop closes. Local agents stop when the desktop app quits; user remote computers must remain online.
factory:RUN-02: A new worktree creates its own branch from a selected base by default. Factory-managed worktrees isolate each session checkout on local machines or connected Droid Computers. Worktrees have separate working files but share Git history. cross-checked
factory:RUN-02
A new worktree creates its own branch from a selected base by default. Factory-managed worktrees isolate each session checkout on local machines or connected Droid Computers. Worktrees have separate working files but share Git history.
- Unknown after the targeted first-party documentation, release and repository pass: checkout, container, vm, os_sandbox, filesystem, process, network, secrets, security_boundary. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory creates separate Git checkouts and branches, with ephemeral or persistent lifecycles and setup profiles. Non-Git folders can start without worktrees; isolation is file separation, not a security sandbox.
factory:RUN-03: Persistent worktrees never clean up automatically; ephemeral worktrees are eligible unless a session is pinned. Managed computers auto-pause while idle and resume for a new session; files, packages, services and configuration persist. cross-checked
factory:RUN-03
Persistent worktrees never clean up automatically; ephemeral worktrees are eligible unless a session is pinned. Managed computers auto-pause while idle and resume for a new session; files, packages, services and configuration persist.
- Unknown after the targeted first-party documentation, release and repository pass: client_disconnect, worker_crash, service_restart, transcript_reload, process_reconnect, state_reconstruction, context_loss, duplicate_actions, manual_repair, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
-
Finding: Factory creates separate Git checkouts and branches, with ephemeral or persistent lifecycles and setup profiles. Non-Git folders can start without worktrees; isolation is file separation, not a security sandbox.
factory:RUN-04: A computer may start from a successful Environment snapshot; later Environment rebuilds do not mutate the existing computer. cross-checked
factory:RUN-04
A computer may start from a successful Environment snapshot; later Environment rebuilds do not mutate the existing computer.
- Development environment reliability: first-party sources in this pass did not establish dependencies, caches, services, ports, secrets, duplicate_installs, collisions, remote_setup, automatic_repair. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
factory:RUN-05: Workstream agents stop at plan or organization usage limits until reset. The usage guide explicitly says agents stop once their applicable usage limit is reached. cross-checked
factory:RUN-05
Workstream agents stop at plan or organization usage limits until reset. The usage guide explicitly says agents stop once their applicable usage limit is reached.
- Unknown after the targeted first-party documentation, release and repository pass: time_limits, turn_limits, token_limits, timeouts, retries, provider_failures. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Usage shows total credits, agent counts and per-session model/cost shares. A 90% banner warns before agents stop at plan/org limits. Default routing can use additional machines or fresh environment computers.
factory:RUN-06: App connection states include connecting, connected and error; induced-failure consistency was not tested. cross-checked
factory:RUN-06
App connection states include connecting, connected and error; induced-failure consistency was not tested.
- Truthful status and operational statistics: first-party sources in this pass did not establish logs, traces, failure_reasons, usage_export, task_stats, agent_stats, project_stats, time_stats, approval_status, reconnect_consistency, performance_method, responsiveness. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
-
Finding: Factory-managed persistent computers retain packages, files, services and configuration. User-managed hosts use a separate Remote Control route.
factory:RUN-07: Workstream Usage lists each session credit consumption and its share of total. The workstream breakdown includes agent sessions. A workstream shows its total credits. A banner appears at 90% of the usage allowance. Usage breaks down credits by session and model. cross-checked
factory:RUN-07
Workstream Usage lists each session credit consumption and its share of total. The workstream breakdown includes agent sessions. A workstream shows its total credits. A banner appears at 90% of the usage allowance. Usage breaks down credits by session and model.
- Unknown after the targeted first-party documentation, release and repository pass: task_cost, harness_aggregation, billed_vs_estimated, tokens, subscription_allowance, provider_reconciliation, compute_cost, refresh_delay, export. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Usage shows total credits, agent counts and per-session model/cost shares. A 90% banner warns before agents stop at plan/org limits. Default routing can use additional machines or fresh environment computers.
factory:RUN-08: Workstream defaults describe additional machines for orchestrator routing. Workstream agents share the normal Factory allowance and organization limits. cross-checked
factory:RUN-08
Workstream defaults describe additional machines for orchestrator routing. Workstream agents share the normal Factory allowance and organization limits.
- Unknown after the targeted first-party documentation, release and repository pass: concurrency, queues, cpu_ram, backpressure, check_reuse, check_deduplication, bounded_tests, cancellation, fairness, recovery. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Usage shows total credits, agent counts and per-session model/cost shares. A 90% banner warns before agents stop at plan/org limits. Default routing can use additional machines or fresh environment computers.
factory:TEAM-01: Slack delegation supports follow-up instructions in one active session thread or dedicated code channel. The code channel gives the team a shared place to instruct the same session; channel sessions run as the service account.
factory:TEAM-01
Slack delegation supports follow-up instructions in one active session thread or dedicated code channel. The code channel gives the team a shared place to instruct the same session; channel sessions run as the service account.
- First-party documentation review only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Finding: Factory receives follow-up messages/attachments in an active Slack session. A code channel is dedicated to one Factory session so the team can work in it; users send further instructions there. Channel sessions run as the service account; DMs run as the person. Code channels depend on Slack availability and app permissions.
factory:TEAM-02: Owner, Manager and User have distinct organization permissions. Owners and Managers administer members. Business lists SSO and SAML/SCIM provisioning. SSO and directory synchronization map IdP groups to Factory roles. Directory membership changes propagate to Factory; end-to-end immediate session revocation was not tested. cross-checked
factory:TEAM-02
Owner, Manager and User have distinct organization permissions. Owners and Managers administer members. Business lists SSO and SAML/SCIM provisioning. SSO and directory synchronization map IdP groups to Factory roles. Directory membership changes propagate to Factory; end-to-end immediate session revocation was not tested.
- Unknown after the targeted first-party documentation, release and repository pass: project_roles, task_roles, unauthorized_access, plan_scope. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
-
Finding: Owner controls the organization and billing. Manager administers members, settings and service accounts. User cannot override locked organization settings. SAML/OIDC and directory synchronization map groups to roles.
factory:TEAM-04: Enterprise owners can inspect organization administrative events. Managed settings updates have revision-tracked before/after differences. Audit events identify the acting human or service principal. Structured audit entries record actors and timestamps; tamper-proof retention was not established. cross-checked
factory:TEAM-04
Enterprise owners can inspect organization administrative events. Managed settings updates have revision-tracked before/after differences. Audit events identify the acting human or service principal. Structured audit entries record actors and timestamps; tamper-proof retention was not established.
- Unknown after the targeted first-party documentation, release and repository pass: approvals, discussion, decisions, cross_session_persistence, export, mutability, retention. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Enterprise owners see organization audit events with actor, source, target, payload and timestamp. Events include role/settings/key/integration changes, not an assertion of complete agent-decision history.
factory:TEAM-05: The PRs tab lists each workstream PR with its checks and review activity. PR tabs offer Diff, Walkthrough and Validation views. The Conversation view shows PR description and comments. cross-checked
factory:TEAM-05
The PRs tab lists each workstream PR with its checks and review activity. PR tabs offer Diff, Walkthrough and Validation views. The Conversation view shows PR description and comments.
- Unknown after the targeted first-party documentation, release and repository pass: evidence_navigation, request_changes, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
factory:SHIP-01: Workstream shared files retain plans, notes, findings and reports. Files supports list/grid, folder browsing, search and type filters. A linked shared file opens in the workstream Files tab. Shared documents sync across machines and reappear when disabled shared folders are reenabled. Workers save their findings in the orchestrator-designated shared folder. cross-checked
factory:SHIP-01
Workstream shared files retain plans, notes, findings and reports. Files supports list/grid, folder browsing, search and type filters. A linked shared file opens in the workstream Files tab. Shared documents sync across machines and reappear when disabled shared folders are reenabled. Workers save their findings in the orchestrator-designated shared folder.
- Unknown after the targeted first-party documentation, release and repository pass: diffs, screenshots, recordings, previews, test_outputs, reviewer_outputs, revision_links, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: Orchestrator and workers share synchronized plans, findings and deliverables across machines. Humans upload files/folders and download outputs. Organization controls can disable shared folders separately from message sync.
factory:SHIP-02: Missions describe user-facing QA validation and self-correction, requiring an automated scriptable application setup. Validation workers check each mission milestone. Milestone validation tests agreed work; requirement conflict detection and immutable approval gates remain unestablished. Mission settings can disable QA validation. cross-checked
factory:SHIP-02
Missions describe user-facing QA validation and self-correction, requiring an automated scriptable application setup. Validation workers check each mission milestone. Milestone validation tests agreed work; requirement conflict detection and immutable approval gates remain unestablished. Mission settings can disable QA validation.
- Unknown after the targeted first-party documentation, release and repository pass: lint, types, ci, required_checks, failure_blocking, requirement_conflicts, enforced_policy. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Missions plan features and milestones before orchestrated execution, with validation that depends on a scriptable repository environment.
-
Missions Planning and Validation
Finding: Milestones trigger validation workers; QA validation can be disabled in mission settings. Planning estimates count feature and validation workers but are not measured cost guarantees.
factory:SHIP-03: Workstreams track PRs opened or worked on by the orchestrator and agents. PR tabs show comments and review threads. The PRs tab groups Open, Draft, Closed and Merged requests. cross-checked
factory:SHIP-03
Workstreams track PRs opened or worked on by the orchestrator and agents. PR tabs show comments and review threads. The PRs tab groups Open, Draft, Closed and Merged requests.
- Unknown after the targeted first-party documentation, release and repository pass: branches, worktrees, commits, ci_response, rebase, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
factory:SHIP-04: A PR tab has a Merge button and status. Independent enforcement of exact-revision authority was not tested. cross-checked
factory:SHIP-04
A PR tab has a Merge button and status. Independent enforcement of exact-revision authority was not tested.
- Unknown after the targeted first-party documentation, release and repository pass: approve, release, deploy, exact_revision, authority_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
factory:SHIP-05: Workstream PRs can be opened in-product, on the Git host, or copied as links. PR rows retain merged/closed status, checks and review-thread counts. cross-checked
factory:SHIP-05
Workstream PRs can be opened in-product, on the Git host, or copied as links. PR rows retain merged/closed status, checks and review-thread counts.
- Unknown after the targeted first-party documentation, release and repository pass: commit_links, build_links, deployment_links, retained_evidence, rollback, revert, stale_approval_invalidation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
factory:SHIP-06: Workstream PRs are grouped by lifecycle state. The PR list groups Open, Draft, Closed and Merged requests. GitHub rows offer open-for-review, draft, close and reopen actions. cross-checked
factory:SHIP-06
Workstream PRs are grouped by lifecycle state. The PR list groups Open, Draft, Closed and Merged requests. GitHub rows offer open-for-review, draft, close and reopen actions.
- Unknown after the targeted first-party documentation, release and repository pass: summaries, risk_size_filters, findings, artifacts, request_changes, exact_revision_approval, dependency_queues, stale_approval_invalidation, check_deduplication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Workstreams list open, draft, closed and merged PRs with checks and review counts. PR tabs show diffs, walkthrough, validation, review and merge actions; GitHub supports draft/close/reopen actions.
factory:OWN-01: Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license. cross-checked
factory:OWN-01
Factory application software is governed by a limited custom internal-use license in Individual Terms. Factory retains service IP under its custom service terms; this is separate from any public SDK license.
- Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory grants a limited internal-use service/software license, reserves service IP and restricts modification and source discovery. Main application licensing is custom rather than the license of any separate SDK.
factory:OWN-02: Enterprise Custom Deployments can run all of Factory inside the customer network using the dedicated airgap build. Airgap builds make no requests to Factory services during agent use; users configure models, MCP and other endpoints. Humans can download shared-folder documents or copy their contents. Humans upload files or folders as workstream references. Airgap Mode skips sign-in and does not require a Factory account. cross-checked
factory:OWN-02
Enterprise Custom Deployments can run all of Factory inside the customer network using the dedicated airgap build. Airgap builds make no requests to Factory services during agent use; users configure models, MCP and other endpoints. Humans can download shared-folder documents or copy their contents. Humans upload files or folders as workstream references. Airgap Mode skips sign-in and does not require a Factory account.
- Unknown after the targeted first-party documentation, release and repository pass: formats, cancellation, history_portability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Orchestrator and workers share synchronized plans, findings and deliverables across machines. Humans upload files/folders and download outputs. Organization controls can disable shared folders separately from message sync.
-
Finding: Enterprise custom airgap deployments run all Factory inside the customer network. The full local harness skips sign-in, sync, Factory telemetry and crash reporting. It uses configured model endpoints and an optional customer collector, with cloud features unavailable.
factory:OWN-03: Airgap execution and files remain inside the customer network, subject to its infrastructure egress rules. Model traffic can go directly to configured enterprise provider APIs or gateways. The hosted control plane can retain authentication, administrative and operational logs. Operational log retention and residency depend on the customer engagement; customer sandbox logs use customer policy. Retention and residency for Factory-hosted logs are documented in the Trust Center and can be tuned per engagement; Factory Private keeps sandbox code and telemetry in the customer environment. This page names no specific regions. In the Enterprise airgap build, Factory telemetry and crash reports are disabled; with no customer collector configured, the telemetry pipeline does not run. This does not establish a complete connected-build opt-out. Airgap model requests go only to user-configured model endpoints.
factory:OWN-03
Airgap execution and files remain inside the customer network, subject to its infrastructure egress rules. Model traffic can go directly to configured enterprise provider APIs or gateways. The hosted control plane can retain authentication, administrative and operational logs. Operational log retention and residency depend on the customer engagement; customer sandbox logs use customer policy. Retention and residency for Factory-hosted logs are documented in the Trust Center and can be tuned per engagement; Factory Private keeps sandbox code and telemetry in the customer environment. This page names no specific regions. In the Enterprise airgap build, Factory telemetry and crash reports are disabled; with no customer collector configured, the telemetry pipeline does not run. This does not establish a complete connected-build opt-out. Airgap model requests go only to user-configured model endpoints.
- Unknown after the targeted first-party documentation, release and repository pass: credentials, artifacts, deletion, training, subprocessors, telemetry_disclosure, telemetry_defaults, consent_prompt. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Enterprise custom airgap deployments run all Factory inside the customer network. The full local harness skips sign-in, sync, Factory telemetry and crash reporting. It uses configured model endpoints and an optional customer collector, with cloud features unavailable.
-
Finding: Managed and default Private control planes are Factory-hosted. Private sandboxes stay in the customer VPC. Operational logs, session storage and provider traffic have separate retention and routing controls.
factory:OWN-04: Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
factory:OWN-04
Factory has a recurring Free plan and paid subscriptions from $20/month. Optional Extra Usage uses prepaid credits consumed by model and cloud-compute usage; own subscription/key routes remain available.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
-
Finding: Individual sessions consume credits based on model and cloud-compute usage. Extra Usage is prepaid credits with a $10 minimum and no expiration. Free supports ChatGPT/GitHub Copilot sign-in and own provider keys/custom endpoints.
factory:OWN-06: Workstreams is beta on Pro, Plus, Max and Teams, explicitly not yet Business or Enterprise, checked 7 November 2026. cross-checked
factory:OWN-06
Workstreams is beta on Pro, Plus, Max and Teams, explicitly not yet Business or Enterprise, checked 7 November 2026.
- Availability and support: first-party sources in this pass did not establish access_restrictions, support, response_commitments, release_activity, status_history, deprecation, export_options. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
-
Finding: Workstreams beta coordinates a persistent orchestrator, agents, shared files and PRs; available plans explicitly exclude Business and Enterprise at this check.
factory:OWN-07: Factory lists ISO 27001 and ISO 42001; exact certified entities and product scope require the reports. Factory states SOC 2 Type II certification. Trust Center provides report access. Public vendor statements were read; underlying reports, issuer and audit period were not inspected. cross-checked
factory:OWN-07
Factory lists ISO 27001 and ISO 42001; exact certified entities and product scope require the reports. Factory states SOC 2 Type II certification. Trust Center provides report access. Public vendor statements were read; underlying reports, issuer and audit period were not inspected.
- Unknown after the targeted first-party documentation, release and repository pass: iso_issuer, iso_validity, soc2_scope, soc2_period, verification_date. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Factory lists SOC 2 Type II, ISO 27001 and ISO 42001 and links its Trust Center for reports, architecture and subprocessors. Underlying assurance documents were not inspected.
factory:OWN-08: Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
factory:OWN-08
Factory now offers a recurring $0/month Free plan using the user inference account or keys; paid plans remain available separately.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.
-
Finding: A recurring Free plan costs $0/month with bring-your-own inference: sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect API keys/custom endpoints. Paid recurring plans start at $20/month; the complete plan list has no one-time purchase.
factory:OWN-09: Business and Enterprise require a quote; exact rolling usage limits and computer costs were not established by the plan cards. cross-checked
factory:OWN-09
Business and Enterprise require a quote; exact rolling usage limits and computer costs were not established by the plan cards.
- Pricing transparency: first-party sources in this pass did not establish units, included_limits, overages, compute_markup, model_markup, minimum_commitment, cancellation, transparency_classification. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
-
Finding: Pro is $20/month, Plus $100 and Max $200; Teams adds a team fee and seats, while managed computers start in Plus.