sintaxi/surge

CLI for the surge.sh CDN

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on July 26th, 2014
Open Issues & Pull Requests: 214 (+0)
GitHub issues: Enabled
Number of forks: 156
Total Stargazers: 3,056 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.3 hours
Mean response time: 22.8 days
90th percentile: 35.8 days
Tracked items: 65

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 543 days
Stale 30+ days: 25
Stale 90+ days: 23

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Surge is a CLI tool for publishing static websites to a global CDN.

Surge solves the problem of deploying static content quickly and reliably across multiple regions. It works by accepting a local directory path and domain name, then distributing the site to ten regions globally. The tool is built on an API-first architecture where every CLI feature is also accessible programmatically, enabling integration into automated workflows and CI/CD pipelines without requiring separate implementations.

Surge suits developers and teams publishing static sites who want straightforward deployment without infrastructure management. The free plan offers unlimited custom domains and unlimited deployments, making it practical for both staging environments and production use. The API-first design makes it particularly valuable for scenarios requiring programmatic control, such as automated content pipelines or systems that need to deploy multiple sites at scale.

The project maintains active development with regular updates to its codebase and documentation. The tool receives ongoing refinement to its deployment workflow and user interface based on feedback from its user base.