The Problem
I remember the exact moment it happened. I had just shipped a new feature to a personal project — something I was genuinely proud of. I spent hours documenting it in a README, explaining the technical details, highlighting the challenges we overcame.
Then I posted on LinkedIn. The response was... underwhelming. Two likes, a handful of comments asking about one line of code, and crickets from anyone who wasn't in my immediate network. I spent 20 minutes crafting the post, poured my energy into it, and got maybe 10 minutes of engagement in return. It felt like shouting into the void.
The problem wasn't the content. It was the formatting. The post read like a technical spec, not a story. The jargon drove away the people who should have been most excited. The bullet points made it look like documentation, not a narrative.
And here's the honest truth: I didn't know how to fix it. I'm a developer, not a writer. I knew how to write code, not how to craft a LinkedIn post that would actually resonate with people.
But I noticed the same thing happening to other open-source maintainers I followed. People shipping incredible work, documenting it beautifully, but posting to LinkedIn and getting nothing in return. The gap between "this code is impressive" and "this is a story worth following" was real — and it was holding developers back from building genuine audiences.
The Solution
So I started building a tool. Not an AI. Not a text generator. Something simpler.
A transformer. Something that would take your README, your changelog, your PR description — and transform it into LinkedIn-worthy posts. I'd parse the content, identify the key points, strip out the jargon, and structure it into multiple story angles: the milestone announcement, the behind-the-scenes story, the lessons learned, the technical-but-friendly breakdown.
And crucially, I wanted to keep it client-side. No server. No data collection. No sign-ups. Just paste your content, click generate, and get your posts. Your code, your content, your story — on your terms.
"To help every developer, maintainers, and open-source creator tell their story on LinkedIn — not just their code."
We believe that technical work deserves recognition. Not just from other developers — from the wider world. From hiring managers, from users, from anyone who might benefit from the tools and projects we build.
And we believe that the tools themselves should make this easier. Not harder. We've built DevPost to be fast, simple, transparent, and respectful of your time and privacy.
Because the people building the future deserve to be seen.
Open Source Maintainers
You ship incredible tools, but your posts don't get the attention they deserve. We help you frame your releases as stories people want to follow.
Indie Hackers
Building in public, but not sure how to tell your story? We translate your progress into engaging LinkedIn posts that attract customers and collaborators.
Software Engineers
Career-switchers, junior devs, senior engineers — everyone needs to communicate their work to non-technical audiences. We help you bridge that gap.
Startup Founders
You're building something people need, but your technical updates get buried. We help you share milestones that matter to your users and investors.
Students & Learners
You're learning, building, and shipping. We help you document your journey in a way that attracts mentors, collaborators, and opportunities.
Engineering Teams
You're shipping internal projects that have value beyond your company. We help you publicize them as thought leadership that builds your personal brand.
What Makes Us Different
You might be wondering: "There are AI tools out there that generate LinkedIn posts. What makes DevPost different?"
Three things.
We're Transparent
We use rule-based templates, not a black-box AI. You can read our logic. You can audit our output. No hidden costs, no surprise API calls.
We're Client-Side Only
Your content never leaves your browser. We don't collect data, we don't track you, we don't have user accounts. Privacy by design.
We Understand Code
Other tools generate generic "Lorem Ipsum" style posts. We actually parse your README, detect your features, and understand your context. Because we were built by developers, for developers.
We're not trying to replace your voice. We're trying to help you find it. The tool does the heavy lifting — formatting, structure, clarity. You bring the passion, the authenticity, the insight. We help it shine.
Clarity First
Jargon drives people away. We strip it out. We rephrase complex technical concepts into plain language. We structure your story so it's easy to follow. Because the goal isn't to impress with vocabulary — it's to connect with real people.
Credit to Developers
You're the one doing the work. You're the one shipping the code. You're the one solving hard problems. The tool helps you tell that story. The recognition should go to you — not to some generic AI output. We build in credit where credit's due.
No Data Harvesting
We don't track you. We don't collect your content. We don't have analytics. We don't sell your data. Your content stays yours, always. We're building a community, not a customer list.
Free for Everyone
Every developer should have access to this tool, regardless of whether they're a solo maintainer or a Fortune 500 engineering team. We're building for the community — not for profit. That's why DevPost will always be free.
Respect for Privacy
If you wouldn't paste your README into ChatGPT, you shouldn't have to paste it into our tool either. That's why we're client-side only. No server, no cookies, no tracking. Your privacy is your right — and our responsibility.
Same Pain Points
We've been in your shoes. We've struggled to get engagement. We've wondered if anyone actually cares about what we're building. We built this because we needed it — and we're glad you're using it too.
Open Source Friendly
Whether you're maintaining a project with 10 stars or 10,000, we see you. We appreciate you. We built this for the people who make the open-source ecosystem work.
Always Evolving
We're constantly iterating based on user feedback. We listen to what works, what doesn't, and we build it. This is your tool, too — not just ours.