LazyRelay
Social media scheduling with Proof-of-Publish verification
LazyRelay is a social media scheduling tool built around Proof-of-Publish: instead of just trusting a "scheduled" status, LazyRelay verifies and shows you real confirmation that each post actually went live on the platform. Plan, schedule, and publish across your social accounts with visibility into what actually happened, not just what was supposed to happen.
Features
- Proof-of-Publish verification that a post actually went live, not just that it was accepted
- Schedule and publish across multiple social platforms from one dashboard
- Uses official platform APIs, no fragile browser automation
- Public API and MCP server for AI-agent workflows
Use Cases
- Solo founders and small teams who need to stay active on social media without babysitting every post
- Agencies managing multiple client accounts who need proof a scheduled post actually published
- Anyone who's been burned by a scheduler silently failing without telling them
Comments
Hey Fazier! I built LazyRelay after getting burned by a scheduler that silently failed a post and never told me. "Scheduled" isn't the same as "published," so LazyRelay actually checks and confirms a post is live before calling it done. Happy to answer any questions about how the verification works.
The failure mode worth naming is that a 200 from the platform API is not proof either: a post can be accepted and then held for review, quietly limited, or left with media that never finished transcoding. Re-reading the permalink unauthenticated, once at publish time and again a few minutes later, is a much harder claim than the API said OK. And since agencies are a stated use case, storing that permalink plus the fetch timestamp as an exportable audit trail seems like the part they would actually pay for.
Premium Products
Sponsors
Buy
Makers
Makers
Comments
Hey Fazier! I built LazyRelay after getting burned by a scheduler that silently failed a post and never told me. "Scheduled" isn't the same as "published," so LazyRelay actually checks and confirms a post is live before calling it done. Happy to answer any questions about how the verification works.
The failure mode worth naming is that a 200 from the platform API is not proof either: a post can be accepted and then held for review, quietly limited, or left with media that never finished transcoding. Re-reading the permalink unauthenticated, once at publish time and again a few minutes later, is a much harder claim than the API said OK. And since agencies are a stated use case, storing that permalink plus the fetch timestamp as an exportable audit trail seems like the part they would actually pay for.
Premium Products
New to Fazier?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2025. All Rights Reserved