The backlog assistant your security team can verify.
G-Code breaks epics into child work items and drafts thin tickets in your organisation's own house style. It runs in your own Azure subscription, and nothing is written to Azure DevOps until a person approves it.
What it is, and where it runs.
A chat panel in every work item
It reads the open work item and, where your admin allows, related source code. It proposes edits and child items shaped by your own skills library.
You host it
Your platform team deploys it into your own Azure subscription. There is no vendor-hosted instance or vendor tenant in the path.
You bring the model
Point it at your own Microsoft Foundry deployment or your own Anthropic account. Both are first-class choices.
It can stay in your tenant
On the Foundry path, content never leaves your Azure tenant. On the Anthropic path it reaches Anthropic, and we say so.
GeekIt is never in the data path. Check it yourself.
No work items, code, prompts, output, identities or usage counts reach any system we control, on either path.
No analytics, crash reporter or usage reporting. Your own provider bills you for inference.
Against a public key inside your deployment. Nothing calls us at install, at runtime or at renewal.
Run a network inspection at install, in normal use or at renewal. You won't find a call to GeekIt.
Stated plainly, side by side.
Both are fully supported. They differ in what they need and where your content goes.
| Compare | Microsoft Foundry Default | Anthropic |
|---|---|---|
| What it needs | An existing Foundry model deployment | An Anthropic account and an API key |
| Setting it up | A Foundry deployment, a quota request and an Azure AI capacity approval | None of the Foundry steps. The quickest way to evaluate |
| Where content goes | Stays inside your Azure tenant and cloud agreement | Leaves your tenant and reaches Anthropic, under Anthropic's terms |
| Billing | On your existing Azure agreement | A separate Anthropic account and invoice |
| Content reaches GeekIt | ✓ Never | ✓ Never |
| Content stays in tenant | ✓ Yes | No |
| Long-lived credential | ✓ None. Managed identity only | A key, kept in your own Key Vault |
Anthropic is not GeekIt. Content sent on the Anthropic path goes to Anthropic, not to us.
A person approves every change.
Open a work item
Choose the AI Assistant tab on any epic, feature or story in Azure Boards.
Ask for what you need
Break down an epic, tighten acceptance criteria or draft a ticket in your house style.
Review, then write
Nothing is written to Azure DevOps until you review the proposal and approve it.
Simple to buy. Checked in your tenant.
- A paid product with bring-your-own licence. One licence covers every Azure DevOps organization under the tenants we agree.
- We invoice you directly, not through the Visual Studio Marketplace.
- Inference is billed by your own provider. We don't meter or bill model usage.
- A replacement licence takes effect without a redeploy or restart.
Run it in your own tenant.
Tell us about your Azure DevOps organisation and we'll send a quote. Already a customer? The support guide explains who can fix what.