Commite461e99unknown_key
feat: AGPL license-change notice + Anthropic outreach deck
feat: AGPL license-change notice + Anthropic outreach deck Two moat-builders inline: LICENSE-CHANGE-NOTICE.md Announces the planned MIT → AGPL-3.0 cutover at v1.0. Closes the network-use loophole that lets hyperscale clouds privatise forks. Microsoft can't fork Gluecron without releasing their changes. Current MIT LICENSE stays in place pending counsel review. docs/ANTHROPIC-OUTREACH.md External partnership brief targeting Anthropic BD. Pitches Gluecron as the reference architecture for Claude-driven code workflows — the Stripe-of-payments for Anthropic's agent ecosystem. Asks for three things: reference mention in Anthropic docs, technical blog post, preferred-partner API rate. Offers showcase deployment, MCP depth, Anthropic-first defaults, and 30-day spec adoption commit. Both are pure markdown — no code surface. Strategic signal moves.
2 files changed+288−0e461e9933341499c8cacca48dc3b412c2509800a
2 changed files+288−0
AddedLICENSE-CHANGE-NOTICE.md+94−0View fileUnifiedSplit
@@ -0,0 +1,94 @@
1# Gluecron License Change Notice
2
3**Status:** Announced 2026-05-25 · Effective with v1.0 release · Pending counsel review
4
5## What's changing
6
7Gluecron is moving from the **MIT License** to the **GNU Affero General
8Public License v3.0 (AGPL-3.0)** effective with the v1.0 release.
9
10The current `LICENSE` file (MIT) continues to apply to every commit up
11to the v1.0 cutover. From v1.0 onwards, all new contributions and the
12codebase as a whole are licensed under AGPL-3.0.
13
14## Why
15
16### The short answer
17
18The AGPL is the only widely-recognised license that closes the
19"network-use loophole." If someone takes Gluecron, modifies it, and runs
20it as a service — they must publish their modifications. Other licenses
21(MIT, Apache, even GPL) let cloud vendors privatise improvements.
22
23### The strategic answer
24
25Gluecron is built to be the AI-native git platform for the next decade.
26We need to ensure:
27
281. **The platform stays open.** AGPL guarantees every Gluecron
29 instance, anywhere, contributes back any modifications it ships
30 to its users.
31
322. **Hyperscale forks return value.** Microsoft, AWS, GCP — if any of
33 them fork Gluecron and run it as a managed service, AGPL forces
34 them to release their changes. MIT/Apache let them do so without
35 contribution.
36
373. **The community benefits from every deployment.** Whether you run
38 Gluecron at home, in an enterprise, or as a SaaS — your improvements
39 flow back to the commons.
40
41### What this means for you
42
43- **You can still use Gluecron commercially.** AGPL doesn't restrict
44 commercial use. Run it for your company, your customers, your SaaS —
45 all permitted.
46- **You must share modifications you ship to users.** If you modify
47 Gluecron and run that modified version as a network service that
48 your users interact with, you must make the modified source code
49 available to those users.
50- **Private internal modifications are fine without disclosure.**
51 AGPL only triggers when your modified version is offered as a
52 service to others. Internal-only changes have no disclosure
53 requirement.
54
55## What about my existing fork/integration?
56
57Anything you forked or integrated against under the MIT license
58**stays MIT-licensed**. You don't have to retroactively re-license
59work that was done before the v1.0 cutover.
60
61For integrations against the Gluecron API (Holden Mercer, Crontech,
62Cursor, etc.) — the API contract is unchanged. Your integration code
63remains under whatever license you originally chose.
64
65## What about Crontech?
66
67Crontech and Gluecron are sister platforms. The AGPL change is
68neutral on the Crontech ↔ Gluecron edge-layer relationship — Crontech
69acts as a network service in front of Gluecron, not a fork of it. No
70AGPL implications for that integration.
71
72## What about contributors?
73
74By submitting a PR to Gluecron after the v1.0 cutover, you agree to
75license your contribution under AGPL-3.0. Pre-v1.0 contributions
76remain under MIT.
77
78## When does v1.0 ship?
79
80v1.0 is the "platform stability" milestone. We'll cut it once:
81- The closed-loop core (spec → code → ship → monitor) is stable
82- Agent multiplayer is production-tested at scale
83- We have at least one external enterprise customer in production
84- Counsel has reviewed the AGPL transition
85
86Target: late 2026 calendar year.
87
88## The single sentence
89
90**Gluecron will be open source forever. AGPL guarantees that
91"forever" includes every hyperscale fork of us, not just every
92self-host of us.**
93
94— Gluecron team, 2026-05-25
Addeddocs/ANTHROPIC-OUTREACH.md+194−0View fileUnifiedSplit
@@ -0,0 +1,194 @@
1# Gluecron × Anthropic — Partnership Brief
2
3**Status:** External outreach draft · 2026-05-25
4**For:** Anthropic partnerships team (Mike Krieger / Anthropic BD)
5**From:** Gluecron founding team
6
7---
8
9## The one-line pitch
10
11**Gluecron is the reference architecture for Claude-driven code
12workflows — the Stripe-of-payments for Anthropic's agent ecosystem.**
13
14---
15
16## Why Anthropic should care
17
18Anthropic's agent story is fragmented today. Claude Code, the MCP
19spec, the Computer Use API, the Files API — each is powerful, but
20none of them have a **default deployment substrate**. Developers
21who build with Claude end up stitching it onto GitHub + Vercel +
22their own infra, with Microsoft sitting in the middle of the
23GitHub edge.
24
25Gluecron is built to be that substrate. **Everything Anthropic
26ships, we host the workflow for.** Developers come to Gluecron
27specifically because it's the platform that knows what Claude is.
28
29The strategic value to Anthropic:
30
311. **A neutral git host that's Anthropic-native.** Microsoft owns
32 GitHub. GitLab is Google-friendly. Gluecron is the only major
33 git platform with no big-three cloud loyalty.
34
352. **A reference architecture for agent workflows.** When a
36 developer asks "how do I deploy my Claude tool-use loop?" the
37 answer becomes "/connect/claude/deploy on Gluecron" — not "spin
38 up your own Lambda."
39
403. **A counterweight to Copilot's mindshare.** Every Gluecron
41 feature is built around Claude. Spec-to-PR, voice-to-PR,
42 multi-repo refactor, repo chat — all powered by Claude. Every
43 Gluecron customer becomes an Anthropic customer by default.
44
454. **An MCP showcase.** Gluecron has 60 MCP tools. It's the
46 largest single MCP server in production. Any Claude Desktop or
47 Cursor or Cline user already benefits when they install
48 Gluecron's DXT.
49
50---
51
52## What we've already built (one weekend of work)
53
54| Feature | Built around Claude | Status |
55|---|---|---|
56| Spec-to-PR autopilot | Yes — Claude implements the spec | Live |
57| Voice-to-PR | Yes — Claude interprets the transcript | Live |
58| Multi-repo refactor | Yes — Claude coordinates N PRs | Live |
59| Repo rubber-duck chat | Yes — Claude with semantic-index retrieval | Live |
60| AI CI self-healer | Yes — Claude diagnoses + patches | Live |
61| AI commit messages | Yes — `gluecron commit` calls Claude | Live |
62| AI release notes | Yes — Claude reads merged PRs | Live |
63| AI three-Claude review | Yes — security + correctness + style trio | Live |
64| AI test generator | Yes — per-PR auto-test PRs | Live |
65| Hosted Claude-loop wizard | Yes — paste code → endpoint | Live |
66| Agent multiplayer | Yes — `agt_…` tokens with budgets | Live |
67| 60 MCP tools | Yes — every action callable from Claude | Live |
68| AI proactive monitor | Yes — hourly Claude anomaly scan | Live |
69| AI cost dashboard | Yes — per-repo Claude spend | Live |
70| AI doc updater | Yes — README auto-PRs on drift | Live |
71| Advancement scanner | Yes — weekly Claude self-improvement | Live |
72
73---
74
75## What we're asking from Anthropic
76
77In priority order, what would actually move the needle:
78
79### 1. A reference mention in Anthropic's official examples
80
81Add Gluecron to one of:
82- The Claude Desktop example MCP servers list
83- The Anthropic Cookbook (alongside Brave Search, Slack, etc.)
84- The "Tool use with Claude" docs page
85
86This single mention sends 100% qualified developer traffic. We're
87fine being one of many — but being there at all is the unlock.
88
89### 2. A blog post on anthropic.com
90
91A technical case study showing how to build an autonomous coding
92agent using Claude + Gluecron. We supply the technical content;
93Anthropic edits + publishes. Format reference: anthropic.com/news
94posts about Brave, Slack, Notion partnerships.
95
96This is the credibility unlock. Hacker News will pick it up. It
97buys us 6 months of acquisition-defense runway.
98
99### 3. Preferred-partner API tier
100
101If Anthropic has a partner-rate API tier, we'd value access. We're
102spending $X/month on Claude API today across our autopilot tasks.
103At scale, we'll be one of the larger non-OpenAI codebases
104calling the Claude API. Aligning rates aligns incentives.
105
106### 4. Co-marketing on the agent-multiplayer story
107
108The "10,000 agents pushing to one repo" future is real. Microsoft
109can't ship it. Gluecron is the only platform architected for it.
110A joint thought-leadership piece (whitepaper, conf talk, podcast
111appearance) on this future would benefit both sides.
112
113---
114
115## What we offer in return
116
1171. **Showcase deployments.** Gluecron itself runs on Gluecron.
118 We can offer the platform as a public case study of "running
119 an AI-native git host on Claude."
120
1212. **MCP tooling depth.** 60 tools today, on track for 100+.
122 We're committing to keeping the Gluecron MCP surface the
123 most-comprehensive MCP server in production.
124
1253. **Anthropic-first model defaults.** Every AI feature on
126 Gluecron defaults to Claude. We support GPT/Gemini via the
127 multi-model picker, but Claude is the platform default and
128 our public positioning.
129
1304. **Feedback loop on enterprise needs.** As Gluecron scales,
131 we'll see what enterprise Claude buyers ask for. We commit
132 to channelling that back to Anthropic's product team via a
133 regular sync.
134
1355. **First-class implementation of Anthropic specs.** When
136 Anthropic ships a new spec (MCP, Computer Use, Files API
137 improvements), Gluecron commits to being the reference
138 implementation within 30 days.
139
140---
141
142## What we DON'T need
143
144We are deliberately NOT asking for:
145
146- Investment / equity participation
147- Exclusive rights of any kind
148- Pre-announcement embargo on Anthropic news
149- Restriction on Anthropic's ability to partner with our competitors
150
151We just want a reference mention and the chance to be one of the
152default substrates for Claude-driven workflows.
153
154---
155
156## The deck-form pitch (3-slide TL;DR)
157
158**Slide 1: The problem**
159Anthropic's agent ecosystem has no default deployment target.
160Developers stitch Claude onto GitHub + Vercel + Lambda. Microsoft
161sits in the middle.
162
163**Slide 2: The solution**
164Gluecron — an AI-native git platform where every feature is built
165around Claude. 60 MCP tools, hosted loop wizard, agent multiplayer,
166spec-to-PR. One platform, Anthropic-native.
167
168**Slide 3: The ask**
169A reference mention on anthropic.com. We'll do the rest.
170
171---
172
173## Concrete next steps
174
175If this resonates:
176
1771. We'd love a 30-min intro call with Anthropic's partnerships team
1782. We'll demo the platform live — including the hosted-loop wizard
1793. We'll co-author the technical case-study draft for review
180
181Reach out to: **ccantynz@gmail.com** · gluecron.com
182
183---
184
185## Appendix — proof points
186
187- **Source:** https://gluecron.com/ccantynz-alt/Gluecron.com (open source)
188- **vs GitHub comparison:** https://gluecron.com/vs-github
189- **Build-agent integration spec:** https://gluecron.com/docs/build-agent-integration
190- **MCP server endpoint:** https://gluecron.com/mcp
191- **Hosted-loop wizard:** https://gluecron.com/connect/claude/deploy
192- **Live status:** https://gluecron.com/admin/health (public read)
193
194— Gluecron team, 2026-05-25
0195