hasarakMinimalModern

For open source maintainers

Keep maintainers on the same page.

Talk through pull requests in threads, keep the contributor guide and release checklist as pages, and let your scripts post release notes through the MCP server.

Start freeSee pricing
Hasarak's web app: the #platform channel about a blocked deploy, with its thread open on the right ending in a summary of cause, fix and open follow-up.

  • A thread per pull request

    Discuss each PR or release in its own thread; the inbox brings back the replies and mentions that involve you.

  • Release checklists as pages

    Task lists, tables and Mermaid diagrams, edited together, one click from the channel where the release is discussed.

  • Your bots become connectors

    A connector is one HTTP endpoint in any language, or any MCP server you already run.

  • Start on the Free plan

    Maintainer teams of up to 10 can use Hasarak for free.

Built for the review loop

A lot of maintainer chat is “is #412 merged yet?” Give each PR or release its own thread and the answer stays next to the question, while the channel stays readable. A GitHub connector that replies to PR links with their title, state and size is built and coming to the hosted app.

Write the docs where you talk

Governance notes, the release process and triage rules don’t belong in a pinned message. Pages hold them with task lists, tables and diagrams, maintainers edit them together, and any message can link to one.

Automate with the tools you already write

Maintainers script everything. The workspace is an MCP server, so any MCP client or script can post release notes or update a page through one typed API. Anything more involved, like reacting to new messages, is a connector: one HTTP endpoint that Hasarak calls. See integrations.

Related

Keep maintainers on the same page.

Start free