Cofounder vs Kortix: Which Work Can Run Unattended?
Compare Cofounder and Kortix on recurring starts, workflow execution, approval controls and the checks behind finished work.
Founder, Task Machine
Cofounder and Kortix differ on a practical question: which parts of an agent job can start without you? Cofounder publishes scheduled app jobs and social posts. Kortix documents scheduled and webhook-triggered agents, but its JavaScript workflow tool requires a person’s message to begin.
A recurring job can need both an automatic start and a coordinated sequence of agents. Verify those separately. A product can support schedules and saved workflows without allowing a schedule to start that workflow tool.
Company services with an agent you choose
Cofounder’s introduction presents tools your existing agent can reach through Model Context Protocol (MCP), a command-line interface or an API. Company services include email, customer records, repositories, hosting and databases. It suits a builder whose immediate problem is connecting an agent to the services needed to run a company.
Shared company knowledge gives the agent context for later work. Roadmap milestones help identify what to do next, and selected companies can use larger plans and assigned Tasks. Those Tasks can belong to a person or Cofounder and retain notes, conversations and links.
The Tasks documentation makes a narrower promise about follow-ups: a follow-up date records when attention is needed, but does not schedule execution. Your agent needs another instruction to check due work. Do not treat that date as a recurring-job control.
Repository configuration and scripted coordination
Kortix organizes shared agents, tools and memory as repository files. Its developer documentation describes JavaScript workflows that coordinate agents with parallel calls and pipelines. Saved scripts accept arguments and can be reused.
My Kortix proposes a workflow plan before multiple agents run, and you approve it. The plan card shows phases, agent count and progress. For developers who want coordination expressed in scripts, that gives a concrete artifact to inspect before execution.
Kortix also documents agent teams with a lead and a shared task list. Teams are experimental, off by default and last only for the lead’s session. They should not be mistaken for permanent teams with ongoing ownership across sessions.
Separate triggers from workflow entry points
Cofounder lists app jobs and workflows, but its public guides do not describe defining repeatable processes with explicit steps, branches or conditions. Supported hosts can receive event notifications. The guides do not establish outside events or webhooks starting the agent work itself.
Kortix’s guide describes schedules and signed webhook triggers that start an agent, plus loops that wake an existing session with its history. Connector events are experimental and off by default. However, a trigger, reminder or another session cannot start its JavaScript workflow tool, which needs a person’s own message.
That boundary can decide a weekly research pipeline. If you need an event to launch coordinated scripted stages, confirm the supported route before adopting the script as the job’s entry point. Kortix also limits a triggered session’s wait for a person to 30 minutes, after which it stops, so unattended approvals need an explicit operating plan.
Approval scope and result checks need separate tests
Cofounder offers Ask before going live for administrator approval of staging-to-live changes. Its agent guides request permission before purchases, provisioning or money movement, except for free managed setup. Its verifier documentation also describes rubric checks that can improve a deliverable before returning it.
Those verifiers are in limited rollout, and production access is off until enabled for that environment. For product implementation, the verifier's coverage excludes private workflows and live integrations it cannot exercise. A successful rubric check therefore needs to be read alongside its coverage boundary.
Kortix uses Allow, Ask and Block rules for connector actions. Review holds a specific call for a person to approve or deny, and changing the call requires another approval. Experimental Goals, off by default, use a separate verifier session that did none of the work, checking every done criterion and sending anything short of all passes back for revision.
Both publish ways to hold actions and inspect results, but the features have different availability and scope. For an email campaign, evaluate permission to send separately from checking whether the proposed audience and content satisfy your brief. Neither product’s public docs describes permission-change proposals based on your approval history.
Budget for the services you will actually use
Cofounder’s pricing guide starts plans at $40 a month, all as usage credit, and unused credit rolls over. For Google and Meta ads, the published charge is ad spend plus 10%. Your agent provider’s subscription or model charges remain separate from Cofounder service credits.
Kortix’s pricing page lists Free with 500 monthly credits on the first workspace. Credits starts at $50 a month for 5,000 credits shared by unlimited members. Compute and models bill separately, managed models add 5.5%, and own-key usage adds 5% above $1,000 a month.
Kortix accepts your own provider keys or a supported subscription on every plan, and its guide also covers subscription-funded model calls. Those model calls do not consume Kortix credits, but computer usage still does. List the runtime and model charges separately when evaluating a sample job.
Cofounder and Kortix, point by point
These answers cover the same questions for both products, with a source and check date attached to each. Read the explanation alongside each label, especially where availability is restricted.
Both columns answer the same questions from each company's public pages. Yes means the company publishes the capability the question asks about, Partly means something narrower, No means it says it does not offer it, and Not published means its public pages do not describe it. Every answer links to its source and shows when we last checked it. The oldest check on this page was November 13, 2026.
| What you compare | Cofounder | Kortix |
|---|---|---|
| Goals |
Cofounder
Partly
The roadmap tracks milestones and recommends the next one. Larger goal plans and their action tasks are available to selected companies, but the docs do not describe an agent owner tracking a goal's measurable metrics. |
Kortix
Yes
Kortix describes agents running a search program that tracks queries, rewrites declining pages and measures results. Its Goals feature assigns an agent to done criteria and scheduled wakes, but is experimental and off by default. |
| Leads |
Cofounder
Partly
Agents read shared company context, recent events and the recommended roadmap milestone. The docs do not describe lead or owner roles coordinating work across goals, projects or teams. |
Kortix
Yes
An agent team has a lead that splits work, coordinates teammates through a shared task list and combines their answers. Teams are experimental, off by default and exist only for the lead's session rather than as saved teams. |
| Tasks |
Cofounder
Yes
Selected companies can assign tasks to Cofounder or a person and keep notes, conversations and links. |
Kortix
Partly
Agent teams have numbered tasks with owners, status and dependencies, while sessions keep the conversation. Its docs do not establish work records that both people and agents can own with their own discussion or history. |
| Recurring work |
Cofounder
Partly
Cofounder describes scheduled jobs for your app and scheduled social posts. A task follow-up date does not schedule work automatically. Its docs do not describe starting work from outside events or webhooks. |
Kortix
Yes
Triggers start agents on schedules or signed webhooks, and loops wake existing sessions with their history. Connector events are also available experimentally and are off by default. |
| Workflows |
Cofounder
Partly
Cofounder lists scheduled jobs and workflows for your app. Its public guides do not describe defining repeatable multi-step processes with steps, branches or conditions. |
Kortix
Yes
JavaScript workflows coordinate agents through parallel calls and pipelines, and saved scripts can run again with arguments. The workflow tool starts only from a person's message, not a trigger or reminder. |
| Autonomy |
Cofounder
Yes
Ask before going live requires an administrator to approve changes moving from staging to live, and requested reviews and approvals are collected on Home. Agent guides also call for approval before buying, provisioning or moving money, with an exception for free managed setup. |
Kortix
Yes
Allow, Ask and Block rules control connector actions, and Review collects held approvals. A person approves or denies the exact action, and a changed call needs a new approval. |
| Learned autonomy |
Cofounder
Not published
Agents follow guides about approvals and report progress. The docs describe no evidence-based proposals to change an agent's autonomy from approval history. |
Kortix
Not published
Its public docs describe editable action rules and a reflection agent that improves skills and instructions, but no proposals to change an agent's permissions based on approval history. |
| Memory |
Cofounder
Yes
The company Library holds shared files such as customer notes and decisions, which agents read for later work and users can read and edit. The docs do not describe automatic lessons from corrections or restorable notes across agent and project scopes. |
Kortix
Yes
Agents keep memory as editable Markdown files in Drive and read it at the start of later tasks. My Kortix saves preferences and corrections, and you can ask what it remembers or tell it to forget something. |
| Planning |
Cofounder
Yes
An agent suggests tasks from the roadmap and waits for you to pick. Selected companies can keep larger goal plans in the Library and create tasks for concrete actions. The docs do not describe reviewing acceptance criteria before every run. |
Kortix
Yes
My Kortix proposes a workflow plan in conversation before running multiple agents. You approve it first, and its card shows phases, agent count and progress. |
| Intake |
Cofounder
Partly
Supported hosts can receive webhook notifications for incoming CRM emails, texts, forms and social interactions. The docs do not describe routing those incoming requests to an owner or agent. |
Kortix
Yes
Signed webhook triggers route outside events to a chosen agent or existing session. Software Factory can receive issues and failures into a ticket store and give each ticket a worker. |
| Connectors |
Cofounder
Yes
Your agent uses Cofounder through MCP, a command-line interface or an API, and supported hosts can subscribe to event notifications. The docs do not describe installing arbitrary services as custom connectors that start workflows. |
Kortix
Yes
Kortix publishes a catalog of 3,000+ apps plus MCP, OpenAPI and raw HTTP connections. You can add custom connectors, and signed webhooks start agent work. |
| Models |
Cofounder
Partly
You connect your own agent, including Claude, ChatGPT, Codex or Cursor. Cofounder does not document automatic model selection for each task or step. |
Kortix
Partly
You choose a workspace default, pin a model to an agent or select one per session. Ordered fallback models handle failures, but its docs do not describe automatic model selection based on each task or step. |
| Cloud or your own computer |
Cofounder
Yes
Cofounder sandboxes let your agent edit files and run code on web and mobile. On desktop, it can use a sandbox or the terminal in your desktop app. |
Kortix
Yes
Kortix offers its hosted cloud and a self-hosted deployment. You can also connect your own computer through the desktop app for filesystem, shell or screen access, with access controlled on that computer. |
| Your own subscription |
Cofounder
Yes
Cofounder connects to your own Claude Code or Codex agent through MCP. Your agent provider's subscription or model usage charges are separate from Cofounder's service credits. |
Kortix
Yes
Every plan accepts your own provider keys or a ChatGPT subscription. The guide also documents Claude Pro and Max subscriptions, whose model calls use no Kortix credits. |
| Pricing |
Cofounder
Yes
Plans start at $40 a month, all as usage credit, and unused credit rolls over. Google and Meta ads cost ad spend plus 10%. |
Kortix
Yes
Free includes 500 monthly credits on the first workspace. Credits starts at $50 a month for 5,000 credits shared by unlimited members. Managed models add 5.5%. Own-key usage adds 5% above $1,000 a month. Compute and models bill separately. |
| Correctness |
Cofounder
Yes
Limited-rollout verifiers create or improve deliverables and return them after rubric checks pass. Product implementation checks exclude private workflows and live integrations the verifier cannot exercise. |
Kortix
Yes
Experimental Goals use a separate verifier session that did none of the work. It checks every done criterion as pass, fail or inconclusive, and anything short of all passes sends the goal back to work. |
For software work
| What you compare | Cofounder | Kortix |
|---|---|---|
| Code review rules |
Cofounder
Not published
Agents can check and push repository changes. The docs describe no code review against repository rules. |
Kortix
Partly
Software Factory verifies changes and adds independent review before a merge gate. Its docs do not specify code review against repository rules. |
| Adversarial review |
Cofounder
Not published
Limited-rollout verifiers evaluate deliverables against rubrics. The docs describe no independent second review of risky code changes. |
Kortix
Yes
Software Factory puts an independent review after the worker's verification and feedback, before a merge gate. Its docs do not describe a separate high-risk change classification for that review. |
| Risk rating |
Cofounder
Not published
Repository status shows the production branch, last deployment and open pull requests. The docs describe no merge-risk rating for a change. |
Kortix
Not published
Its developer docs allow risk labels on submitted Review items, but do not describe a rating of a code change before merge. |
| Pull requests |
Cofounder
Partly
Repository status shows open pull requests, and the agent can change and check code. The repository guide describes direct pushes to the production branch. The docs do not describe agents working on pull requests with review feedback. |
Kortix
Yes
Software Factory assigns tickets to workers that verify changes and open pull requests with demos, followed by feedback, independent review and a merge gate. A person merges unless automatic merging is configured. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Cofounder and Kortix are named only to identify them, and there is no relationship between the companies. Has something changed? Tell us.
Who each one suits
Pick Cofounder if you want to keep your agent and give it company services, shared knowledge and a roadmap. Confirm access to Tasks and verifiers because both are restricted during rollout. Its follow-up dates still require you to ask for a due-work check.
Pick Kortix if repository-based configuration, reusable JavaScript coordination and hosted or self-hosted deployment fit your team. The workflow tool’s human-start requirement is the limit to resolve first for unattended work. Experimental Goals and teams also need explicit evaluation before becoming dependencies.
Where Task Machine fits
Task Machine connects recurring starts to defined Workflows, with ordered steps, branches, approvals and result verifiers. Schedules and service events can start Tasks or Workflows, and a recurring job keeps a stable root Task with separate occurrence history. That answers the entry-point question for a team that wants recurring execution and its review path on the same work record.
Task Machine is the wrong pick if you need Cofounder's managed product stack, because its docs do not describe a managed product stack that provisions your business hosting and database together. See Switch from Cofounder to Task Machine. Use Task Machine vs Cofounder and Task Machine vs Kortix to map one scheduled job’s start, approval pause and failed-check retry before choosing its home.