GITHUB-BACKED • AI-READY

Your project's memory,
versioned in GitHub.

Plain .md files. Clean browser editor. Your own AI agents read, write, and maintain it — via Git or a simple API.

Before you click "Create a wiki — free":
• You'll sign in with Google (this creates your free Wikispring account — no GitHub account needed to start).
• We (via our bot) create a new private GitHub repo for you called wikispring-yourname.
• You get a friendly editor + the ability to upload your existing .md memory files right away (your files replace our starter templates on name clash).
• Free forever for solo use. No credit card.
How it works GitHub
Solo free forever. Dedicated private repo created for you on GitHub.
📦

Git-native

Every wiki is a real private GitHub repo. Full history, branches, diffs, clone locally, or edit on GitHub. No lock-in, ever.

🤖

Your AI, your keys

Agents use the API (or direct Git) with your Claude/GPT keys. We never run inference. You control the loops that archive, groom, and humanize.

✍️

Human-first Markdown

Deliberately simple: headings, lists, links, code, basic tables. One-line stubs for cards. Works for both people and agents.

🔐

Chinese-wall by design

Dedicated memory repo (recommended) or submodule. Your project code and your long-term memory stay cleanly separated.

A hosted memory layer for projects that ship with AI. Each wiki is plain Markdown files in a GitHub repo you own. Edit in the browser or locally. Give your agents a clean API (or let them commit directly) so they can maintain the backlog, archive resolved work, and keep the docs human-readable over time.

Questions

FAQ

How does the Git integration work? Each Wiki Space is a private GitHub repo. The browser editor (CodeMirror) reads/writes .md files via GitHub API and commits changes. You can also edit locally by cloning the repo, or directly on GitHub — everything stays in sync via Git. Full history, branches, and diffs are native Git features.

Can my AI agents use their own subscriptions? Yes — that's a core design. The API is designed so you prompt your Claude/GPT/etc. agents to do maintenance (archive resolved items, update backlogs, humanize text, etc.). Wikispring just orchestrates and commits via Git. This keeps our costs low and gives you full control.

What about the 56 messy Claude .md files problem? Drop them in, connect your agents, and let maintenance loops clean, archive resolved work, and keep things human-friendly and trackable over time.

What markup is supported in the editor? Deliberately simple and human/AI-friendly: headings, numbered/bulleted lists, links (including [[wiki links]]), code blocks, and basic pipe tables (no column widths or advanced styling). Every file starts with a one-line "stub" summary for easy UI cards and previews.

How do AI agents access the memory layer? Paid users generate API keys scoped to their space. The API lets agents list files, read raw .md content, and write updates (which become Git commits). We provide example prompts in the docs so you can use your own agents without us running the inference.

Can I use my existing GitHub repo? Yes — connect an existing private repo during space creation (via GitHub OAuth/App). New spaces can auto-create a repo for you.

Simple pricing

Pricing

Solo
Free
1 wiki space • full editor • Git sync • basic API access
Humans (per collaborator)
$10/mo
$10/month per human • Access through the Wikispring editor (no direct GitHub repo access)
API Access
$20/mo
$20/month • Generate API keys so your own agents can read/write the .md files

Billed monthly. Free tier always available for solo use. GitHubFAQPrivacy