The product factory that ships what your customers want.
Starko turns every customer experience into a real product improvement, built and verified for you to merge.
Free plan includes $20 of Starko AI usage a month14 visitors hesitated on the help-center home this week looking for search (session replays), and 3 asked about it in the widget.
Customers reach you on the widget, email, WhatsApp and Instagram. Slack threads and GitHub issues become tickets too, and fixes land as pull requests on GitHub or GitLab.
- Website widget
- Slack
- GitHub issues
Everything between a complaint and a merge.
One inbox for every customer
The website widget, email, WhatsApp and Instagram land in one place. The AI assistant answers from your knowledge base and hands over when needed.
Fixes you approve, with a price
Starko AI watches session replays for friction and proposes a fix with its size, the visitors behind it and an estimate. Nothing runs until you accept.
Runs a crew of agents
Larger work splits across up to five agents. A crew review checks their pull requests together and combines them into one.
Works where your team talks
Mention @Starko in Slack to start fixes and check on runs. Every change asks for your approval first.
Evidence on every pull request
Before and after screenshots, your test command re-run in the sandbox, and a reviewer agent’s verdict.
How the factory works
Four stages, one loop, a human at the merge button.
Starko AI, Starko's own coding agent, writes the code in a sandbox running your app. Starko decides what to build, writes the brief, verifies the output, reviews it and keeps the ledger.
Collect
Every channel and session replay
Recommend
Sized, costed, tied to customers
Build
A coding agent in a sandbox
- Test
- Evidence
- Review
Verify
Tests, evidence, reviewer agent
Intake and channels
Every conversation becomes a ticket.
Conversations from WhatsApp, email, Slack, Instagram and your website widget become tickets with a customer, a priority and a type. Starko answers what it can from the knowledge base and routes the rest to the right project.
Learn more about intake and channels- lelena 10:52 AM
Anyone else seeing the WhatsApp template picker crash when a template has no body? Two customers hit it today.
- dididier 10:53 AM
Yes, Acme reported it too. Picker also lists 41 stale templates; there is no way to delete them.
- enena 10:55 AM
That is three customers this week. Can we get this into the factory before Friday?
Recommendations and decisions
Nothing is built until you accept it.
Repeated friction becomes a recommendation: bug or improvement, sized Small, Medium or Large, with the visitors behind it and a credit cap. You accept or decline from Home or the Improvements page, and nothing is built until you do.
Learn more about recommendations and decisionsRecommendation: make the search box visible on the help-center home
Bug: ticket reply fails when the attachment is larger than 10 MB
Recommendation: explain the empty state on the Projects page
Sessions and sandboxes
Watch the agent work, and steer it.
An accepted recommendation starts a run in an isolated sandbox with your real toolchain. Watch the agent work, send it files, steer it mid-run, or let the foreman in Slack keep you posted. Starko AI writes the code; Starko runs the loop.
Learn more about sessions and sandboxesTemplate picker crashes when a template has no body
- searching
whatsapp-template - reading
components/functional/whatsapp-template-picker.tsx - reading
actions/connections/whatsapp.ts - running
npm test -- whatsapp-template
TemplatePicker reads template.body.length before checking the body exists; a template with no body throws on render. I also found 41 stale templates in the picker and no way to delete them, which is what Ana asked for. I will fix the crash first and add a delete action in the same pull request unless you want them separate.- editing
actions/connections/whatsapp.ts - writing
components/functional/whatsapp-template-manager.tsx - writing
tests/whatsapp-template-manager.test.tsx - running
npm run lint && npm run typecheck && npm test
git push origin starko/fix-d2728b0cReview and merge
Every pull request brings its own proof.
Every pull request opens inside Starko with its own proof: what was reproduced, every command the sandbox ran with its exit code, the reviewer agent's risk verdict, and the checks. Merge from the same panel; the ticket closes and the customer is told.
Learn more about review and mergefeat(whatsapp): add the ability to delete a WhatsApp template
starko-ai[bot]·updated 20 hours ago· Open
mainstarko/fix-d2728b0c-ad880f 9 files+1,354 -62Run
Open ticketReproduction
Reproduced
Picker listed 41 stale templates; no delete affordance anywhere in the UI.
Verification
13 commands run in the sandboxAgent’s claim: deletion removes the template on Meta and the local mirror row; the picker drops it from every send and broadcast flow.
- exit 0
npm run lint✔ 0 problems
- exit 0
npm run typechecktsc --noEmit · 0 errors
- exit 0
npm test -- whatsapp-templateTests: 8 passed, 8 total
- exit 0
npm run test:e2e -- template-manager3 passed · deleted a template in the seeded sandbox
Reviewer agent
Risk: mediumPlanning and monitoring
See what ships, and what it cost.
Projects carry their tickets on a timeline coloured by delivery state: planned, running, pull request open, merged. Templates seed a project with its ticket distribution, and the ledger below tells you what every run cost.
Learn more about planning and monitoringStarko AI
Every fix run, what came of it, and what it cost: the ledger behind the @starko agent.
Merged PRs
41
Merge rate
85%
merged ÷ runs that opened a PR
Time to merge
3h 40m
median, run start → merge
Billed / merged PR
$18.20
platform cost $6.90
Outcomes
62 runs · 55 opened a PR · 9.4M tokens · $745 billed at list price · $283 platform cost| Ticket | Task | Outcome | Started |
|---|---|---|---|
| Delete a WhatsApp template | Feature · medium | Running | 6 min ago |
| Ticket reply fails above 10 MB | Bug · small | PR open | 1 h ago |
| Explain the empty Projects state | Feature · small | Merged | yesterday |
| Invoice PDF missing VAT line | Bug · small | Merged | yesterday |
| Annual plan proration | Feature · large | Needs info | 2 d ago |
Runs, outcomes and cost
Every run is accounted for.
An accepted recommendation becomes a run: reproduce the problem, implement the change, let the reviewer agent check it, open a pull request. A revise verdict or red CI re-dispatches the run within a cap you set. The Starko AI ledger shows each run's trigger, outcome, CI state and cost, next to merge rate and time to merge.
- Runs in parallel across many tickets, not one sprint at a time.
- Per-project autonomy policy: auto-dispatch small fixes, ask on large ones.
- Merge rate, time to merge and cost per merged PR, always visible.
The coding agent is built in
Starko AI writes the code. Starko runs everything around it.
There is no agent to bring or configure. Starko decides what to build, writes the brief, sets up the sandbox, has Starko AI reproduce and fix the problem, re-runs your tests, reviews the diff, and tracks what happened after the merge.
- 01Starko AI
Reproduces, fixes, verifies
- 02Sandbox
Your app, running
- 03Reviewer
A second opinion
- 04GitHub
PRs, checks, merge
- of Starko pull requests get merged
- 85%
- software teams shipping with Starko
- 18
- channels feeding one factory
- 6
- charged for anything that doesn't merge
- $0
Pricing
Start free. Upgrade when Starko is doing more of the work.
The Free plan is permanent and needs no credit card. Paid plans include more AI usage and more automated Starko AI runs each month, with extra usage billed on demand.
Free
Answer customers, track tickets, see what breaks and try the factory with a few Starko AI runs each month.
Start for free- Inbox and AI answers from your knowledge base
- Ticketing
- Session replays and page errors
- Recommendations
- A few Starko AI runs each month to try the factory
Standard and Pro
Most teamsFor teams that let Starko AI work tickets every week and want more room to run.
Get a demo- Everything in Free
- More AI usage included
- More automated Starko AI runs each month
- Extra usage billed on demand
Enterprise
Self-hosted models, dedicated runners and a partner program for your customers.
Talk to us- Everything in paid plans
- Self-hosted models and bare-metal runners
- SSO, audit log, data residency
- Partner and reseller program
- Dedicated support
Why a factory
Coding agents made writing code cheap. Deciding what to write, proving it works, and closing the loop with the customer who asked did not get cheaper. That is the part Starko automates.
Starko started as a support inbox for software companies with thousands of business customers. The requests those customers made were the roadmap; the factory is what happens when the inbox can act on them.
Three assumptions behind the product
FAQ
Questions teams ask before they switch it on.
Connect a channel and a repository
Turn the support queue into a build queue.
Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.