Muriki
All modules
Coming soon

Muriki Projects

The team's work, with no side spreadsheet.

projects is where work stops being yours and becomes the team's: backlog, fixed-length cycles, roadmap and the support queue. Tasks that already live in focus join the board without becoming copies — it's the same record, seen by the team.

Get access
Backlog12
MUR-33

Workspace onboarding

BacklogMediumMB
MUR-34

Search by subject

BacklogLowGT
This cycle5
MUR-24

Ship the early access

To doHighGT
MUR-36

Calendar MCP server

To doUrgentAL
In progress2
MUR-25

Offline sync with Yjs

In progressUrgentGT
MUR-28

Team invite by link

BlockedHighMB
Done8
MUR-27

The focus timeline

DoneMediumAL
what it will do

From the backlog to what shipped.

  • Prioritised backlog

    One queue, owner and priority in sight, instead of three spreadsheets that disagree.
  • Fixed-length cycles

    Closed scope per period, and whatever didn't fit returns to the backlog on its own.
  • Board by stage

    The columns the team actually uses, with each card carrying status, priority and owner.
  • Quarterly roadmap

    The big deliveries on a timeline, tied to the tasks that make them up.
  • Team capacity

    How much is already committed before taking one more — without counting on your fingers.
  • Service desk with SLAs

    Tickets with agreed response times, a queue by priority and a warning before it runs out.
  • Tickets open by link

    The customer follows and replies without an account or an install.
  • Workflow automations

    When a task changes state, whatever should happen next happens on its own.
  • Cycle analytics

    What came in, what went out, what stalled — with nobody writing a report on Friday.
integrations

What it will reach.

Integrations arrive with the module. All of them go through MCP, the open protocol the rest of the market is adopting.

  • GitHub

    An open PR becomes a task and closes itself on merge, branch tied to the issue.

  • Slack

    Blockers and tightening deadlines reach the channel before they turn into problems.

  • Microsoft Teams

    People who live in meetings get the urgent one where they already are.

  • Figma

    An approved screen shows up on the board with the frame link and current status.

  • Email

    A request arriving by email becomes a ticket in the queue, clock already running.

Is your team in the next wave?

Access opens in waves, as the modules become ready. People on the list go first.

No spam. One email when early access opens.

I already have an account