Starko

Customer feedback in. Merged pull requests out.

Starko is a product factory. It collects what customers say in support conversations and session replays, turns it into sized, costed recommendations, lets a coding agent build the ones you accept, and verifies the result before you merge. You pay per merged pull request. Click around the dashboard below.

Start for freeGet a demo
v2.starko.one/dashboard/improvements
Improvements
72%

Improvements

What Starko AI found in your visitors’ sessions, what you decided, and what it cost.

Statistics

Accepting a row starts a run with the credit cap shown. Declining costs nothing.

Proposed · 30 days

23

Accepted · 30 days

17

Shipped · 30 days

14

Declined · 30 days

6

Credits spent

1,840

Visitors spared

412

Decisions, last 30 days

Inputs to the factory: every support channel you already use, session replays from your product, and the Starko widget on your site.

  • WhatsApp
  • Email
  • Slack
  • Instagram
  • Viber
  • Telegram
  • Messenger
  • Intercom
  • Discord
  • Linear
  • GitHub issues

Three strokes.
Three stages.

Most of what customers tell you never becomes a change. Starko runs every message, email, Slack thread and rage-click through the same loop: collect it, decide whether it is worth building, ship it as a merged pull request. The mark is that loop drawn once.

  1. 01

    Collect

    184 conversations · 41 session replays this week

    WhatsApp, email, Slack, Instagram and the website widget land in one inbox. Starko AI answers what the knowledge base covers and files a ticket for the rest, linked to the customer and company.

  2. 02

    Decide

    23 recommendations · 17 accepted · 6 declined

    Repeated friction becomes a recommendation: bug or improvement, Small, Medium or Large, with the visitors behind it and a credit cap. You accept or decline each one. Nothing is built until you do.

  3. 03

    Ship

    14 merged pull requests · 412 visitors spared

    An accepted recommendation becomes a run: a coding agent works in a sandbox, a reviewer agent checks the diff, and a pull request with evidence waits for your merge. Merge closes the ticket.

How the factory works Four stages, one loop, a human at the merge button.

Starko does not replace your coding agent; it operates it. Claude Code, Codex or Cursor writes the code. Starko decides what to build, writes the brief, runs the sandbox, reviews the output and keeps the ledger.

Collect

01

Every channel and session replay

0 conversations · 41 replays this week

Recommend

02

Sized, costed, tied to customers

Build

03

A coding agent in a sandbox

Verify

04

Tests, evidence, reviewer agent

  1. Test
  2. Evidence
  3. Review

Intake
and channels

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
Thread#customer-success
  • le
    lena 10:52 AM

    Anyone else seeing the WhatsApp template picker crash when a template has no body? Two customers hit it today.

  • di
    didier 10:53 AM

    Yes, Acme reported it too. Picker also lists 41 stale templates; there is no way to delete them.

  • en
    ena 10:55 AM

    That is three customers this week. Can we get this into the factory before Friday?

@Starko file this as a bug, link Acme, and start a run
Aa

Recommendations
and decisions

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 decisions
2 open recommendations
Improvement · SmallProposed 7 visitorsStarko - Main development

Recommendation: make the search box visible on the help-center home

up to 200 credits
Bug · SmallIn progress 2 visitorsStarko - Main development

Bug: ticket reply fails when the attachment is larger than 10 MB

up to 250 credits 40 used
Open
Improvement · SmallMergedStarko - Main development

Recommendation: explain the empty state on the Projects page

up to 80 credits 31 used PR
Open
Ask anything…

Sessions
and sandboxes

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. Claude Code, Codex or Cursor under the hood; Starko runs the loop.

Learn more about sessions and sandboxes
v2.starko.one/dashboard/tickets/4f2c…
Tickets/STK-432
72%

Template picker crashes when a template has no body

In Progress HighSV Stefan Vukmanović Marko Petrović · Acme d.o.o.Bugstarko-me/starko-v2
DescriptionStarko AI
Starko AI Running · 4m 12s starko/fix-d2728b0c-ad880fSVEP #432 Console Changes Preview End session Stop
Run · Oct 24, 10:58 · #432
Worked for 1m 48s
  1. searching whatsapp-template
  2. reading components/functional/whatsapp-template-picker.tsx
  3. reading actions/connections/whatsapp.ts
  4. running npm test -- whatsapp-template
Reproduced it. 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.
Same PR is fine. Make sure a deleted template drops out of the picker in an open composer, and add tests for both.
You· Read · 11:02
Current session · Oct 24, 11:02
Worked for 2m 24s
  1. editing actions/connections/whatsapp.ts
  2. writing components/functional/whatsapp-template-manager.tsx
  3. writing tests/whatsapp-template-manager.test.tsx
  4. running npm run lint && npm run typecheck && npm test
Added a null guard in the picker and a permission-gated template manager with a confirm dialog. Deleting removes the template on Meta and the local mirror row, then invalidates the picker query so it disappears from every send and broadcast flow. 8 new tests, 212 pass. Pushing to PR #432 now.
Also mask the template body in the evidence screenshots, it has customer names.
You· Queued · Send now
Working for 14s running git push origin starko/fix-d2728b0c
Tell Starko AI what to do next…
Enter queues · ⌘Enter steers · Shift+Enter new line

Review
and merge

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 merge
starko-me/starko-v2#432

feat(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 -62

Run

Open ticket
Reviewer revisePR openCI: passingFeature · mediumprompt v14

Reproduction

Reproduced

Picker listed 41 stale templates; no delete affordance anywhere in the UI.

Verification

13 commands run in the sandbox

Agent’s claim: deletion removes the template on Meta and the local mirror row; the picker drops it from every send and broadcast flow.

  • npm run lint

    ✔ 0 problems

    exit 0
  • npm run typecheck

    tsc --noEmit · 0 errors

    exit 0
  • npm test -- whatsapp-template

    Tests: 8 passed, 8 total

    exit 0
  • npm run test:e2e -- template-manager

    3 passed · deleted a template in the seeded sandbox

    exit 0

Reviewer agent

Risk: medium
Side effects: lowCompatibility: lowPerformance: lowVerdict: reviseAuto-revised

Planning
and monitoring

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 monitoring
v2.starko.one/dashboard/projects/whatsapp
Projects/WhatsApp templates
72%
NOVDECJAN
2916233061320274111825
WhatsApp templates
Delete
Sync status
Attachments over 10 MB
Chunked upload
Invoices and VAT
EU VAT line
Proration
Projects empty states
Templates
Custom SSO for Acme

Starko 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
Merged 41 PR open 7 Closed unmerged 4 No fix 3 Needs info 4 Running 3
TicketTaskOutcomeStarted
Delete a WhatsApp templateFeature · mediumRunning6 min ago
Ticket reply fails above 10 MBBug · smallPR open1 h ago
Explain the empty Projects stateFeature · smallMergedyesterday
Invoice PDF missing VAT lineBug · smallMergedyesterday
Annual plan prorationFeature · largeNeeds info2 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.

Bring your own coding agent Starko operates the agent you already use.

Starko is not a model. It is the system around the model: it decides what to build, writes the brief, provisions the sandbox, reviews the diff, and tracks what happened after the merge.

  • Claude CodeAnthropic
  • CodexOpenAI
  • CursorCursor agents
  • GitHubPRs, checks, merge

Self-hosted models and bare-metal runners available on Enterprise.

of Starko pull requests get merged
85%
software teams shipping with Starko
18
channels feeding one factory
11
charged for anything that doesn't merge
$0

Pricing The unit of billing is a merged pull request.

Collecting feedback, AI answers and recommendations are free. Each run has a credit cap you see before you accept it. A pull request that is closed without merging costs nothing.

Merged #418Explain the empty state on the Projects page31 credits billed

Free

$0
forever

Collect feedback, answer questions from your knowledge base, and see the recommendations Starko would build.

Start for free
  • All channels and the website widget
  • AI answers from your knowledge base
  • Recommendations with size and credit cap
  • Up to 2 seats

Factory

Most teams
Per merged PR
no seats, no minimums

Accept recommendations and let runs build, review and open pull requests. Billed per merged PR.

Get a demo
  • Everything in Free
  • Runs in isolated sandboxes with a credit cap
  • Reviewer agent, evidence and in-app merge
  • Automatic revise on review or red CI
  • Unlimited seats

Enterprise

Custom
annual

Self-hosted models, dedicated runners and a partner program for your customers.

Talk to us
  • Everything in Factory
  • 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

01Teams will ship more software than they can maintain by hand.
02The best roadmap signal is already in support conversations and session replays.
03A product should be able to fix and improve itself, with a person approving each merge.
Built by the team behind Starko support, used on Starko itself.

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.

Start for freeGet a demo