Humans take seats. Agents don’t.
Pay for active human contributors. Connect your coding agents without adding seats. Every plan includes pooled AI capacity for GitNative-provided intelligence.
Free
For individuals and small teams getting their work connected.
£0.00
Free workspace
Connected agents don’t take seats
- Up to 2 active human contributors
- Tickets, projects and roadmaps
- GitHub delivery and collaboration
- Workspace roles and scoped agent access
- 120 video call minutes/month per workspace
Developer
For engineering teams moving work forward together.
£6.00
per active human contributor / month
Connected agents don’t take seats
- Everything in Free
- Billed by active human contributors
- Pooled workspace AI capacity
- Existing workspace usage controls
- 1,000 video call minutes/month per workspace
Pro
Compliance includedFor teams that need more AI capacity and compliance controls.
£10.00
per active human contributor / month
Connected agents don’t take seats
- Everything in Developer
- More pooled AI capacity
- Compliance documents and audit exports
- Data region controls
- 5,000 video call minutes/month per workspace
Prices shown in GBP for United Kingdom. Checkout is billed in GBP. Existing tax treatment applies.
Keep the context behind your work available to your team and its agents. Pay for active human contributors. Connect your coding agents without adding seats. Every plan includes pooled AI capacity for GitNative-provided intelligence.
Free includes 1,000 monthly credits per workspace. Developer includes 10,000 and Pro includes 50,000 monthly credits per billed human contributor, pooled across the workspace.
Core agent access and normal Git activity do not consume AI credits. Ordinary reads, writes and stored context retrieval remain included. New embeddings, summaries and model-backed synthesis use AI capacity when authorised.
Paid AI overage is not yet available. The proposed price for additional approved AI usage is £1 per 10,000 credits, charged proportionally. Overage is optional, off by default and will require an agreed monthly spending cap. Free has no paid overage. External coding-agent subscriptions and separately priced hosted developer runtimes are separate.
Credits are not agent counts, commits, raw API calls or a promise of one useful task. Included credits expire monthly without rollover. Annual subscriptions also refresh their AI allowance monthly. Connected agent identities have no seat charge or identity ceiling; workspace request, concurrency, storage and execution safeguards still apply.
How AI credit estimates work
Estimates reserve the maximum input and output cost before execution. Unused capacity is released after verified usage. Each model execution adds 0.1 credit for processing. Cached input is charged at the same published input rate; returning a stored result without inference is free.
| Model | Input / 1,000 tokens | Output / 1,000 tokens |
|---|---|---|
| gpt-oss-120b | 20 credits | 40 credits |
| qwen3-30b-a3b-fp8 | 4 credits | 20 credits |
| glm-4.7-flash | 4 credits | 24 credits |
| llama-4-scout-17b-16e-instruct | 16 credits | 48 credits |
For example, 1,000 input tokens and 200 output tokens on GPT OSS 120B use 28.1 credits. Requests are limited to a conservative input bound of 24,000 units, 4,096 output tokens and eight model steps. BGE embeddings use 4 credits per 1,000 submitted UTF-8 bytes plus 0.1 credit per execution. Automated audio processing and external synthesis are paused until their usage adapters are verified; stored transcripts and ordinary retrieval remain available.
Rate card: workers-ai-2026-09-v1. Invoice amounts are rounded once at aggregation, not per request.
Questions before you connect the work.
Who is GitNative for?
Software engineering teams, technical founders, engineering managers, tech leads, developers, QA, and technical product partners who need delivery context grounded in code, tickets, decisions, and meetings.
What makes it developer-first?
GitHub activity remains a primary delivery signal. Planning, meetings, support, bugs, and agent workflows connect back to branches, pull requests, commits, ownership, QA, and releases instead of sitting in a separate status layer.
Does it replace our ticket system?
GitNative can replace Jira or another ticket tracker for engineering teams, and it can connect Jira or Linear during a gradual transition. Tickets stay linked to decisions, meetings, projects, bugs, releases, and source activity.
What gets automated first?
A focused starting point is meeting-to-ticket or decision-to-project work: capture the source, review related work and a suggested owner, then approve the update before it changes a workspace record.
How does pricing work?
Start free for up to 2 active contributors. Developer and Pro plans bill only for active contributors, with Pro required for compliance controls.