Makrly auto-generates your product communications from GitHub commits. Connect your repo and get: social posts for X, LinkedIn, Threads, Bluesky, and Facebook; an auto-updating changelog with embeddable widget; an AI-generated FAQ from your URLs; a public idea board where users vote on features; and a shareable roadmap. Free forever for public repos.

How does Makrly generate posts from my commits?

Makrly reads your commit messages, filters out trivial ones, and uses AI to generate platform-specific posts in your voice. A 2-minute quiz captures your tone so posts sound like you, not generic marketing copy.

How does the changelog work?

Enable auto-mode and every commit or merged PR becomes a changelog entry. Embed the widget on your site with a single script tag. Customize themes, colors, position, and trigger icon. Users can react to entries and subscribe via RSS.

Is my code safe? What permissions do you need?

Yes, your code is safe. We only request read-only access to your repositories. We read commit messages and file names — never your source code. We can't modify your repo or push changes. Revoke access from GitHub settings anytime.

Can I use my own AI API key?

Yes! Bring your own key from OpenAI, OpenRouter, or Straico. Choose from 40+ models including GPT-4o, Claude, Llama, and more. Pay pennies per generation directly to your provider — we never charge per post.

Your changelog entries now read clearer and stay accurate

We rewrote how changelog entries get generated so they're easier to read, and we fixed a few bugs that were making stats and regeneration unreliable.

You know how sometimes changelog entries can feel a bit wordy or hard to scan? We gave the whole writing style a refresh. Now your entries come out in plain, punchy language — short sentences, clear action words, and the important stuff up front. We also added more variety so entries feel less repetitive.

We also squashed a few annoying bugs. If you ever hit "regenerate" on an entry, it was getting a little confused and could end up slightly off — that's fixed now and stays crisp every time. The file stats (like how many lines changed) were also showing zeros even when real changes happened, so now those numbers actually reflect what really changed in your code. And when there's nothing meaningful to show, we just skip the stats instead of cluttering things up with a bunch of zeroes.