Lindy's own use-cases page lists the jobs a team hands over, from triaging support to logging invoices. Kortix is the open-source AI Operating System that runs the same jobs as sessions, each landing as a change request.
Lindy's own use-cases page groups the jobs by team; each card shows that job as a Kortix session.
A session reads the tickets, groups them by cause, and drafts the replies in a change request a person reviews.
A session reads the call notes, edits the account records, and lands the edits as a diff you can read.
+2 −2
A session pulls the invoices, reconciles them against the ledger, and lands the log as a spreadsheet.
| Vendor | Invoiced | Logged |
|---|---|---|
| Northwind | 1,225 | 1,182 |
| Globex | 180 | 198 |
| Total | 1,405 | 1,380 |
A session reads what merged, drafts the changelog, and opens it as a change request for review.
Lindy's use-cases page groups the work by team. Under "the jobs teams hand over first" it lists tracking competitors, watching a pipeline, and building the staff meeting deck. Everyday productivity covers catching up, planning the week, and prepping meetings. Marketing, Sales, Customer Support, Operations and Finance, and Product and Engineering each carry their own list: checking ad spend, running the deal-won handoff, triaging the support queue, logging invoices, and chasing stale pull requests.
On Kortix, each of those jobs is a session. Kortix is the open-source AI Operating System: your agents, their skills, your company memory, and every connector in one git repo you own. A session runs one agent in its own sandbox on a branch named after the session; the agent commits and opens a change request a person reviews.
project (git repo + kortix.yaml)└─ session ──> a cloud computer on a branch └─ the agent works └─ change request ──> you review and merge ──> mainThe report, the updated record, and the drafted reply survive as files next to the instructions that produced them, so the team reads them, diffs them, and rolls any of it back.
Lindy keeps the work in its cloud and holds approvals on actions with outside impact, per its own pages. On Kortix the work lands in a repo your team reads first, and each tool an agent may touch is set to Allow, Ask, or Block. When the data has to stay on the team's own network, self-hosting runs the same open-source stack on your own box and is free. The other options are compared on Lindy alternatives, the team case is on Lindy for teams, and the money question is on is Lindy worth it.
Short answers about the jobs, where the work lands, and the open-source option.
Lindy's own use-cases page lists the jobs by team, from tracking competitors and watching a pipeline to triaging support, logging invoices, and writing the changelog.
Each job is a session on its own cloud computer. The agent returns finished work as files and lands it as a change request a person reviews.
No. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free, and the managed cloud is the hosted option.
In one git repo you own, as plain files today you can read, diff, and roll back. The wider field is on the Lindy alternatives page.
Start with one session, one agent, and one change request.
Open source · Any model, your keys · Self-host, VPC, or on-prem