The partnerships team launched the CockroachDB Integrations Hub, with 34 partners including Anthropic, OpenAI, Cursor, LangChain, CrewAI, Vercel and Confluent. But the list only arrives inside a script. A reader that takes the page as delivered, which is how many AI crawlers and coding-agent fetch tools work, gets "Showing 0 partners" and "No partners match these filters". The Partners Locator does the same. The new partner marketer is asked to make CockroachDB "visible and well-positioned within AI and cloud ISV ecosystems", and the developer PMM to win when "coding agents themselves now evaluate and choose databases". An agent asked "does CockroachDB work with LangChain and Vercel?" currently reads an empty directory.
First action
Fetch /product/partner-integrations/ with curl and confirm the HTML says "Showing 0 partners".
How to measure it
Integration pages cited by AI assistants for "CockroachDB + partner" questions
- Now
- –
- Target
- 20 of 34
- By
- 90 days
Steps
Confirm
Fetch both pages without JavaScript and record what comes back.
Web Engineering 1 hour
Server-render the list
Partner name, category, description and link in the HTML.
Web Engineering 3 days
Write a page template
What it does, quickstart, code, quote, partner link.
Sr. Partner Marketing Manager 2 days
Publish the AI six
Anthropic Claude Code, Cursor, LangChain, CrewAI, OpenAI, Vercel.
Principal Partner Solutions Architect 2 weeks
Add to discovery
Sitemap, llms.txt and internal links from the product AI page.
Web Engineering 1 day
Ask partners to link
From their docs and marketplaces.
Sr. Partner Marketing Manager 2 weeks
Measure
Indexing, referrals and AI citations per page.
Marketing Operations Manager monthly
Why it works
Render the partner list on the server so the HTML carries every partner name, category, short description and link, and keep the filters as an enhancement. Then give each integration its own page (what it does, a quickstart, a code sample, the partner's quote, a link to the partner's listing) and add those pages to the sitemap and llms.txt. Start with the AI partners: Anthropic Claude Code, Cursor, LangChain, CrewAI, OpenAI and Vercel.
Partner pages are what both search engines and agents use to answer "does X work with Y", and each page gives the partner something to link to and co-promote.
Ready to use
ChecklistIntegration page checklist
[ ] Partner list present in the page HTML (no JavaScript needed) [ ] One page per integration with quickstart and code sample [ ] Partner quote and link to the partner's listing [ ] Page in sitemap.xml and llms.txt [ ] Linked from /product/ai/ and the relevant docs page [ ] Partner asked to link back [ ] Monthly check: indexed, cited by assistants, referral sign-ups
Risks and how to handle them
Partners want approval of copy
Send each draft to the partner with a one-week review window.
34 pages is a lot
Ship the template first and fill pages in order of developer demand.
Evidence
- Your websiteThe Integrations Hub (/product/partner-integrations/) and the Partners Locator (/partners/tech/) send their partner lists only inside a script; the page text a reader gets without running JavaScript says "Showing 0 partners" and "No partners match these filters". The script holds 34 partners, among them Anthropic, OpenAI, Cursor, LangChain, CrewAI, Vercel, Netlify, Confluent, Datadog, Snowflake, Teleport and Temenos. Apart from the cloud providers, IBM and Red Hat, no partner has its own page in the sitemap.Source
- HiringSr. Partner Marketing Manager (posted August 25, 2026): owns go-to-market "across cloud, AI, and ISV ecosystems"; by 90 days, "a repeatable go-to-market playbook for new partner integrations, active co-marketing programs running with at least two ISV partners"; success means "Every major partner integration has a go-to-market plan and supporting content before or at launch" and "CockroachDB is visible and well-positioned within AI and cloud ISV ecosystems".Source
- HiringStaff Product Marketing Manager, Developer Experience (posted August 26, 2026): owns "the moment a developer (or their agent) first meets CockroachDB and decides whether to build on it", including "agent-driven discovery, MCP and agent-facing surfaces, and the reality that coding agents themselves now evaluate and choose databases"; "If an agent doesn't pick us at activation, nothing downstream happens"; also owns the migration story ("AI Migration Assistant and the MOLT tooling") and "quickstarts, docs, sample apps".Source
- HiringPrincipal Partner Solutions Architect: in the past year the partnerships team "launched the ISV Technology Partner Program, shipped live integrations with LangChain, Anthropic Claude Code, Confluent, and Datadog", deepened "a global IBM OEM relationship" and "launched the CockroachDB Integrations Hub"; "Our AWS Strategic Collaboration Agreement is evolving into a systematic AI ISV acquisition engine"; the role builds "integration walkthrough videos, quickstart demos, and co-marketing launch packages".Source
- Your websiteProduct AI page: "The system of record for agentic memory"; lists a "Fully Managed MCP Server", a "CockroachDB Agentic Skills Repo", the "ccloud CLI: Agent-Ready Database CLI", a "CockroachDB Developer Pluging for Claude" (sic), a plugin for Cursor and LangChain providers. The MCP server docs give setup steps for Claude Code, Cursor, Cline, GitHub Copilot and Codex. The pricing page has a "Copy markdown" button.Source