What is build in public and why should I do it?

Building in public means sharing your development journey on social media as you build your product. It helps you grow an audience, get early feedback, build credibility, and create marketing momentum before you even launch.

How does Makrly generate posts from my commits?

When you push code to GitHub, Makrly reads your commit messages and code changes. Our AI analyzes what you built, filters out mundane commits, and generates engaging social media posts tailored for each platform.

Is my code safe? What permissions do you need?

Yes, your code is safe. We only request read-only access to your repositories. We can't modify your code, create branches, or make any changes. We only read commit messages and diffs to understand what you're building.

Can I use my own AI API key?

Yes! You can bring your own API key from OpenAI, Anthropic Claude, Google Gemini, or other providers through OpenRouter. This gives you full control over which AI model generates your posts.

Which platforms are supported?

Currently, Makrly generates posts optimized for X (Twitter), LinkedIn, and Facebook. Each platform gets a different version tailored to its audience and format.

Legacy placements now show accurate stats seamlessly

Older placements without aggregated data now fall back to fresh impression and click counts, so you always see the latest stats regardless of data age.

We’ve improved how stats are displayed for your placements, especially the older ones that haven’t yet been processed into daily summaries. Previously, those placements might have shown incomplete or missing data.

Always see your placement stats
Now, if the system doesn’t find aggregated daily stats for a placement, it automatically falls back to the raw impression and click records. This means all your placements, new or legacy, will reliably show accurate performance data.

This update helps give you a complete and continuous view of how your banners are performing over time, without worrying about gaps caused by data processing delays.