DevinFourteen vendor portals, one pass, every renewal drafted
A companion opens all fourteen, comes back with fourteen dated lines and a link apiece, and leaves the request to each vendor drafted and waiting on a click. Devin is Cognition’s AI software engineer.
That is the half of an engineering week nobody ships a tool for. The incident timeline scattered across three dashboards. The twenty tickets hiding three bugs. The invoice paid in one system and open in the other.
Strawberry is an agentic browser for macOS and Windows, working the logged-in web: the applicant tracker, the ad account, the supplier portal, the dashboard with an export button and no API. Consequential steps stop at a card.
Devin is aimed at the codebase. Cognition’s docs put it plainly: “Devin is the AI software engineer, built to help ambitious engineering teams crush their backlogs”, with the rule of thumb that a task doable in about three hours is probably one Devin can handle. It runs in the cloud at app.devin.ai, there is a CLI, you can tag it in a Slack or Teams thread, and it picks work up from Jira and Linear tickets.
| Devin | Strawberry | |
|---|---|---|
| What it is built for | “Devin is the AI software engineer, built to help ambitious engineering teams crush their backlogs”, per Cognition’s docs | The browser-shaped work sitting between the repository and the CRM |
| What comes back | Work on a backlog ticket, ending in code your team reviews | A state change inside the tool itself, with the tab still open to show what changed |
| Its browser | Embedded, so you can “watch Devin browse through documentation, test web applications it builds, download/upload information, and more” | The whole product: your tabs, your sessions, a companion clicking in them |
| Where you talk to it | app.devin.ai, a CLI, an embedded IDE, and “tagging Devin on a Slack or Teams thread”, with work picked up from Jira and Linear tickets | A chat panel beside the tabs, on your own desktop |
| Acting inside accounts you are already signed into | Not a dimension its docs describe: the embedded browser is there to check the software it built (as of this writing) | The premise of the product: the applicant tracker, the ad account, the supplier portal you are signed into |
| Recurring work | Scheduling is not described in its getting-started docs, as of this writing | Routines on a daily time, an interval, a cron expression, or an app trigger such as a new email, each with its own run history |
| Approval before a consequential action | The engineering review process: you read the diff before it merges | A card naming the exact send, change or payment before it happens, and Ask Always mode for every step |
| Task size it is aimed at | Its docs offer the rule of thumb that a task doable in about three hours suits Devin | A pass across forty logged-in tabs that would otherwise cost you an afternoon of clicking |
Do these two overlap at all?
Thinly, and in one place: both drive a browser.
Devin’s is embedded so it can check that the thing it built loads. A companion’s browser is the entire product.
What is each one built for?
A companion, when the deliverable is a state change in a web app.
Engineers lose Thursday afternoons to this: chasing the vendors whose renewals are due, copying an incident timeline out of three dashboards into a doc, reading twenty tickets to find the three bugs underneath.
Devin is built for the diff. Backlog tickets, migrations, framework upgrades, the review queue, the tests nobody wrote. Those come with an engineering review process attached.
Where the unautomated hours are
Between the repository and the CRM, in work that never gets a ticket, which is why it never got automated. Finished runs of this shape are at /real-runs, and the same work sorted by team is at AI for operations teams.
- Ops: 14 vendor portals, one renewal date each, none of them exported anywhere.
- Recruiting: 40 applicants in the tracker, a public profile to read for each, eleven worth a call.
- Finance: the invoice marked paid in one system and open in the other, nine times over.
- Support: the same three questions arriving in twenty tickets, needing three replies rather than twenty.
What it costs
Free to download with credits to start, paid plans from $20/month, details on pricing. Devin’s docs mention individual and team plans, and their pricing page would not load while this page was being written, so read it there.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents