Build in Public. Be Seen.
DayBy.dev turns your daily progress into a living public profile and CV. Fast. No bloat. Just outcomes, momentum, and proof.
See it in action
From Claude Code to published post in seconds.
You ship. Claude documents.
While you're coding, just ask Claude to draft a post about what you built. The MCP server sanitizes everything locally before it goes anywhere.
You stay in control.
Claude shows you the draft. You confirm. Nothing goes live without your say. Then it's published in under a second.
Live on your DayBy profile.
Every post builds your public CV. Recruiters and collaborators see your momentum in real-time, not a static resume.
Wired up Temporal.io workflows for async job orchestration
Replaced raw Sidekiq jobs with Temporal workflows for the AI article pipeline. Retries, timeouts, and state are now handled by the workflow engine instead of custom glue code...
Generate a card. Post to Instagram.
One click generates a 1080x1440 card ready to share on Instagram, X, or LinkedIn. Show your work where people actually see it.
Your blog. Anywhere.
Every post is API-accessible. Embed your DayBy feed on your personal site, portfolio, or any other project. One token, full control.
View full API docsThe new way
Post progress as you go. DayBy.dev formats it into a clean public page and a living CV. Consistent, searchable, and designed to be seen.
The old way
Profiles get bloated. Updates are slow. Your best work is buried. People can't see your momentum or what you shipped yesterday.
With DayBy.dev vs. Without
With DayBy.dev
- Daily progress becomes a public feed and living CV
- Only the essentials: shipped work, commits, drafts
- Built to be seen by collaborators, investors, recruiters
- Launch in minutes. No custom site required.
Without
- Generic profile, hard to find real progress
- Updates are infrequent and scattered
- Signal buried under fluff and long bios
- Slow to ship your own site; momentum fades
Building is half the work. Making sure people know it exists is the other half.