Hiring certified engineers
IP ownership when a vendor builds your Claude agent
If the prompts, evals, and MCP servers do not live in your git from day one, you are renting a demo. Here is the IP rule we sign before week one, and what to reject in a vendor contract.
July 6, 2026/3 min read/Claude Certified Engineers
IP ownership on a Claude build is not a legal footnote. It is whether you can still run, eval, and change the agent after the vendor's Slack channel goes quiet.
Our rule is simple, and it is in the FAQ on this site because buyers ask it first: you own it, entirely. The code lives in your repository from day one. IP transfer is signed before week one begins. No platform tax, no vendor lock-in, no hosted black box you have to keep renting.
If a shop will not sign that, do not start. You will spend six weeks furnishing their demo environment.
What "yours" has to include
Ownership is not "we emailed you a zip." On a production agent it means, in your git and your accounts:
- Application code and infrastructure as you already run it (AWS, GCP, Azure, VPC).
- System prompts and the loader that production uses. Not a copy in a vendor Notion.
- Tool JSON Schemas and MCP servers you can deploy.
- Golden eval cases, runner, and CI job.
- Guardrail config, review-queue service, tracing.
- Runbook for on-call. How to freeze a prompt. How to replay a failed case.
We meet your stack rather than importing ours. Claude via Anthropic API, Bedrock, or Vertex. TypeScript and Python. That is so the handoff is a PR, not a migration.
What vendors try instead
Patterns we see when we inherit a stalled pilot:
- Prompts live in the vendor's playground. You have screenshots.
- The MCP server runs on their laptop, or a shared "accelerator" you cannot fork.
- Eval is a Google Sheet they own.
- "IP is yours" in the MSA, but the only runnable system is their hosted copilot with a per-seat fee.
Legal language without a repo is theater. Ask for the clone URL on day zero. If they need a week to "stand up an environment," they are not planning to work in yours.
Security and IP are the same conversation
A vendor who insists on admin credentials in a shared tenant is not only a security problem. They are building a system you cannot take over. Constrained service accounts, your secrets manager, your logging. See the MCP security review. Regulated work (HIPAA, SOC 2, SOX, privilege-aware legal, public sector isolation) ships with a compliance architecture document. That document is yours too.
How this changes the buy
On a six-week build, week six is transfer: runbook, eval suite, pipelines, your team trained. On Embedded, the engineer is in your repo every month, which makes the IP question almost boring. On an audit, the deliverable is a plan and baselines in your systems, not a private score we keep.
If you are comparing shops, ignore the model-name drop. Ask where the code will live on Friday of week one. If the answer is not your git, you are not buying engineers. You are buying a cage.
Questions
- Who owns the IP on a Claude Certified Engineers engagement?
- You do, entirely. The code lives in your repository from day one, and IP transfer is signed before week one begins. No platform tax, no vendor lock-in, no hosted black box you have to keep renting.
- What should we refuse in a Claude vendor contract?
- Work that only exists in the vendor's cloud, prompt libraries you cannot export, eval sets they keep, and MCP servers you cannot run. If handoff is a PDF, you do not own the system.
- Does using Claude, Bedrock, or Vertex change IP ownership?
- No. Model APIs are a utility. Your prompts, tools, data pipelines, and evals are the product. Those must be in your git, on your cloud accounts, under your keys.