One API Key, Zero GitHub: Publish with Managed Git

Today we're shipping managed Git publishing: create a site with one command, get a private LiteStartup-hosted repository, clone it, and every git push goes live automatically. One API key. No GitHub account, no OAuth screen, no second credential to juggle.

The friction we removed

Until now, publishing with LiteStartup Skills meant bringing your own public git repo: create it on GitHub, make it public, push, then bind it. That works, but it asks a lot before you write a single word — an account on another platform, a public repo whether you wanted one or not, and an authorization dance.

We wanted the AI-native path to be truly one step: "launch a site for my domain" → start writing.

How it works

Ask your AI editor (with the LiteStartup Skill installed):

Create a site for acme.com — a minimal homepage, a blog, and docs.

Behind the scenes LiteStartup:

1. Creates a private Git repository on our managed Git service for your domain
2. Seeds it with a starter theme (website/, blog/, docs/, changelog/)
3. Hands your editor a clone URL

You clone it and start editing. The only credential involved is your LiteStartup API key — it's used as the git credential automatically and never written into the repo or the remote URL.

git clone https://git.litestartup.com/<your-repo>.git
# edit blog/hello.md ...
git push        # → published to your site automatically

That's it. Push, and the changed pages are live — no separate sync command.

Deleting content, safely

Because your repo is the source of truth, removing a file and pushing unpublishes that page — and it's fully recoverable: add the file back, push, and it returns. To protect you from accidents (a deleted directory, the wrong branch), a push that would take down an unusually large slice of your site is held for a quick confirmation instead of applying automatically.

Prefer your own GitHub repo?

That path is still fully supported. If you'd rather keep content in your own public GitHub / GitLab / Gitee repository, bind it as before — managed Git is simply the new default for anyone who just wants to start writing.

Both ways, the workflow is the same: write in your editor, push, done.

— The LiteStartup Team