
Bitly
URL shortening and link management service for creating concise, trackable links with analytics
Discover top open-source software, updated regularly with real-world adoption signals.

Serverless URL shortener hosted entirely on GitHub Pages
A minimal, free URL shortener that runs on GitHub Pages, using GitHub issues as a lightweight database—no servers, no maintenance, clean short links like ccb.wtf/1.

The GitHub Pages URL Shortener provides a completely serverless way to create short links. By leveraging GitHub Issues as a lightweight, version‑controlled datastore, each issue title stores the destination URL while the issue number becomes the short path (e.g., ). The solution runs entirely on static GitHub Pages, requiring no backend infrastructure or ongoing maintenance.
ccb.wtf/1To deploy, fork the repository, enable GitHub Pages on the main branch, and optionally add a CNAME file for a custom domain. Adjust the PATH_SEGMENTS_TO_SKIP and GITHUB_ISSUES_LINK variables in 404.html to match your domain and repository. New short URLs are created by opening an issue whose title contains the full target URL. The built‑in JavaScript fetches the issue via the GitHub API and redirects visitors instantly. While the approach is inexpensive and ideal for personal or low‑traffic projects, it relies on GitHub API rate limits and lacks built‑in analytics, making it less suitable for high‑volume or enterprise scenarios.
When teams consider GitHub Pages URL Shortener, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Project documentation linking
Provide concise, memorable links to docs hosted on GitHub Pages
Conference speaker slides
Create short URLs for slide decks that can be shared on social media
Personal portfolio branding
Map custom domain short links to portfolio pages without extra hosting costs
CLI tool integration
Generate short URLs via issue creation for automated release notes
It stores the target URL as the title of a GitHub issue; the 404.html script fetches the issue via the GitHub API and redirects.
No, everything runs client‑side on GitHub Pages.
Yes, by forking the repo, adding a CNAME file, and updating the configuration variables as described.
Rate limits on the GitHub API, no built‑in analytics, and the approach is considered hacky—not recommended for production‑critical services.
Open a new issue in the repository; set the issue title to the full URL you want to shorten. The issue number becomes the short path.
Project at a glance
DormantLast synced 4 days ago