How Scaup Works on GitHub Sites

What Scaup does on your GitHub site

After you connect your GitHub repository, Scaup builds a monthly growth plan and runs improvements on a daily schedule. It works by reading and editing files in your repository — the same way a developer would:

• Update page titles and meta descriptions in your page files (Markdown frontmatter, HTML meta tags, JSX/TSX head components, Astro page files).
• Create new content files — blog posts, articles, or new pages — committed directly to your repository.
• Improve body content on existing pages where the structure is clear enough to edit safely.

Scaup works with Next.js, Astro, Nuxt, Hugo, Jekyll, and other static or server-rendered frameworks hosted via GitHub.

How Scaup connects

Scaup connects through GitHub's official OAuth app flow. During setup, you are redirected to GitHub to approve Scaup's access and choose which repositories it can see. Scaup only accesses repositories you explicitly grant access to — it cannot see anything else in your GitHub account.

How changes go live

Scaup commits changes to your repository's default branch. It does not deploy your site — that is handled by whatever CI/CD pipeline you already have set up (GitHub Actions, Vercel, Netlify, etc.). The moment Scaup pushes a commit, your existing pipeline picks it up and deploys as normal.

If you have branch protection rules or required review checks on your default branch, Scaup's commits will be subject to those rules too.

What files Scaup edits

Scaup only edits content files it can safely parse and understand: Markdown (`.md`, `.mdx`), HTML, JSX, TSX, and Astro page files. It reads frontmatter and meta tag values to understand what a page is about, then writes back to those same fields.

Scaup does not touch layout files, configuration files (`next.config.js`, `astro.config.mjs`, etc.), lock files, compiled output, or binary assets.

Requirements

• Your site must be hosted from a GitHub repository.
• Scaup needs read and write access to the repository — this is set during the OAuth connection step.
• A paid Scaup subscription is required to use the improvement engine.

What Scaup does not do

• Deploy your site — it commits to the repository and leaves deployment to your existing pipeline.
• Modify configuration files, layout templates, or shared components.
• Create or merge pull requests — all commits go directly to your default branch.
• Delete any existing files.
• Access repositories you did not grant access to during setup.
• Inject any tracking scripts, advertising code, or third-party services.

Disconnecting Scaup

To revoke Scaup's access, go to GitHub → Settings → Applications → Authorized GitHub Apps and revoke Scaup. You can also disconnect from within the Scaup dashboard under Site Settings.

Revoking access stops all future commits. It does not undo changes that have already been committed and deployed.

Questions or issues

Email [email protected] and we'll get back to you within one business day.