Bin collection info and calendars for the UK
Clean wrapper for existing open-source scrapers, but lacks unique features.

Stateless architecture means your GitHub data is never stored on their servers.
Developers, project managers using GitHub Projects
GitHub Calendar · Cronitor · Placker
I built Projects Calendar because I wanted a way to visualize my GitHub Project deadlines (issues and PRs) in my native calendar app without the privacy trade-offs of typical sync tools.
Most integrations require a persistent database to store your project data. I took a different approach:
100% Stateless: The app has no database. It doesn't store your tasks or deadlines.
On-the-fly Processing: When your calendar app (Google, Apple, or Outlook) requests an update, the service fetches data directly from the GitHub GraphQL API in real-time, generates the .ics feed, and purges the raw data from memory immediately after.
Security: Authentication tokens are encrypted using AES-256-GCM.
Tech Stack: Built with a Rust (Axum) backend to handle requests with high performance and low memory footprint. The UI is Vue 3.
The goal was "Privacy by Design." If you revoke access on GitHub, there is literally no trace of your project data left on the server because it was never saved in the first place.
I’d love to hear your thoughts on this stateless approach for third-party integrations and any feedback on the calendar sync performance.
Clean wrapper for existing open-source scrapers, but lacks unique features.
Works fine, but ESPN and FIFA already offer calendar feeds for matches.
iCal feeds for sunrise/sunset and lunar phases—elegant, zero friction, works in any calendar.
Quick Rust CLI extracting Lovable projects, but it's a one-off convenience tool.
Yet another AI PM copilot in a space Asana and Monday already own.
Automates changelog generation from GitHub activity, but changelog tools already exist.