PINKTURKEY platform access and the capabilities listed for the plan. That is the number on the cards below.
Per developer, monthly
Start on your own. The team plan is there when there is a team.
Plan fees cover PINKTURKEY platform access and the capabilities listed for the plan. Model consumption follows the limits and terms disclosed before purchase — there is no unlimited-use promise anywhere on this page.
- Individual first, fully self-serve
- No unlimited-use promise
- Enterprise starts with a pilot
ONE PLATFORM FOUNDATION
PUBLICDiscover
ACCOUNTCommercial control
WORKSPACEGoverned work
OWNEROperate
IdentityEvidenceAI policyAudit
Three things, charged separately
Platform access, model consumption and enterprise adoption are not the same line.
Keeping them apart is the only way the number on the plan card means anything. Each is stated before you buy, not after.
Eligible models, fair-use boundaries, provider constraints and any separately chargeable usage are disclosed before purchase or pilot activation.
Enterprise scope begins with a pilot covering authority, data boundaries, model policy, evidence goals and operating responsibilities.
Plan
Individual
For one developer who wants to know what is currently governing their codebase, and to stop retired decisions reaching the agent.
$29.00per month
- Private engineering workspace
- Governed specification records
- Billing and invoice self-service
- Platform-managed AI model route
AI usageEligible platform-managed route; limits and additional usage terms are disclosed before activation.
SupportStandard account, billing and operational support path.
AdoptionSelf-service account and monthly subscription.
Operating scopeIndividual professional
Start IndividualRecommended
Business
For a team that needs the same answer shared: one set of records in force, one governed context, one place requests and changes arrive.
$199.00per month
- Up to 25 account members
- Up to 3 governed workspaces
- Workspace member and role management
- Eligible AI model selection
AI usageEligible workspace model selection; provider and usage terms are disclosed before activation.
SupportStandard account, billing and operational support path.
AdoptionSelf-service account with governed team workspaces.
Operating scopeTeam / organization
Start BusinessPlan
Enterprise
For organisations that need governed AI development across teams and workspaces, with evidence and release authority that can be audited.
$799.00per month
- Up to 250 members by default
- Up to 10 workspaces by default
- Cross-workspace overview
- Configurable governance limits
- Controlled pilot onboarding and enterprise operating review
- Bounded pilot onboarding and operating review
AI usageModel policy, provider boundaries and usage terms are defined through the pilot and commercial review.
SupportOperating expectations and support path are agreed during enterprise review.
AdoptionControlled pilot before broader estate rollout.
Operating scopeEnterprise estate
Talk to us about a pilotCompare operating scope
Choose the control model and adoption path your work needs.
Commercial entitlement defines available capability. User permissions and workspace scope still decide who can use it. AI consumption and third-party terms remain explicit before activation.
| Capability | Individual | Business | Enterprise |
|---|---|---|---|
| Account members | Up to 1 | Up to 25 | Up to 250 |
| Workspace model | Private workspace, administration hidden | Visible governed workspaces | Visible governed workspaces |
| Workspace creation | Not exposed | Up to 3 | Up to 10 |
| AI model control | Platform-managed eligible route | Eligible workspace model selection | Eligible workspace model selection |
| AI usage terms | Eligible platform-managed route; limits and additional usage terms are disclosed before activation. | Eligible workspace model selection; provider and usage terms are disclosed before activation. | Model policy, provider boundaries and usage terms are defined through the pilot and commercial review. |
| Cross-workspace oversight | Not exposed | Not exposed | Included |
| Billing, payments & invoices | Self-service | Self-service | Self-service |
| Support path | Standard account, billing and operational support path. | Standard account, billing and operational support path. | Operating expectations and support path are agreed during enterprise review. |
| Adoption path | Self-service account and monthly subscription. | Self-service account with governed team workspaces. | Controlled pilot before broader estate rollout. |
What you actually see
Administration appears when you have someone to administer.
Every account sits on the same work boundary. On Individual the administration surface stays out of your way entirely; it appears as the plan gives you people and workspaces to manage.
A private workspace with no tenant or administration vocabulary anywhere in the normal journey.
Members, roles, visible workspaces and eligible model selection, within the configured limits.
Use broader limits, cross-workspace oversight and configurable governance controls where the commercial contract permits them.
AI model governance
Product behavior stays separate from a single model provider.
PINKTURKEY resolves logical model eligibility through platform policy. Public plan presentation cannot grant a provider, model or capability by itself.
Provider-neutral by design
Individual uses the platform-managed eligible route. Business and Enterprise can select among eligible logical model aliases when subscription entitlement and workspace policy allow it.
Billing & lifecycle
Payment confirmation and product authority remain separate.
Paddle acts as Merchant of Record for applicable subscription transactions. PINKTURKEY activates commercial state only from trusted provider evidence and keeps billing history available at the account boundary.
Monthly subscriptionPayment historyInvoice historyCancellation path
Prices are in USD and renew monthly until cancelled. Applicable taxes are calculated at checkout by Paddle. Plan fees cover PINKTURKEY platform access and the listed entitlements. AI model consumption, third-party services and additional usage may be limited or charged separately when disclosed before purchase. Review the Terms, Refund Policy and Privacy Policy before purchase.
Before you compare
What PINKTURKEY is not.
A clear boundary is faster to evaluate than a long feature list, and it is the part most products leave out.
Not a pipeline tool
No build orchestration, no deployment management, no infrastructure. Whatever ships your code keeps shipping it.
Not a coding agent
PINKTURKEY governs what the agent is told. The agent you already use writes the code.
Not general-purpose work management
It covers software development: requests, changes, incidents and the records that constrain them. Nothing outside that, deliberately.
Commercial clarity
Know what the plan covers before you activate it.
What does the monthly fee cover?
Platform access and the capabilities listed for the selected plan. Taxes are calculated at checkout where applicable.
Is model consumption included without limits?
No. No unlimited-use promise is implied anywhere. Eligible model access, fair-use boundaries, provider constraints and any separately chargeable usage are disclosed before purchase or pilot activation.
Some capabilities are marked In build. Am I paying for those?
You are paying for what is Available today. The status table on the product page is kept current against the delivery plan for exactly this reason — if something you need is In build, ask before you subscribe rather than after.
Which coding agents does this work with?
PINKTURKEY assembles and sends the context; it does not replace your agent. The integration path is open to any agent that accepts a prompt, and the currently supported list is confirmed during sign-up.
What happens to my source code?
What leaves the repository, what reaches a model provider and what is retained are set out in the privacy notice. Read it before connecting a repository — it is written to be read, not to be agreed to.
What support is included?
Individual and Business use the standard account, billing and operational support path with a two working day response target. Enterprise support is agreed during the pilot.
How does Enterprise adoption start?
With a bounded pilot that defines scope, data boundaries, model policy, evidence goals, operating responsibilities and the commercial path before anything is committed.
Can an Individual account expand later?
Yes. The upgrade preserves the account and the underlying work identity; team capabilities appear after verified activation.
Enterprise
Larger estates start with a bounded pilot, not a plan.
The pilot fixes the use case, data boundary, model policy, evidence target and support path before anything is rolled out. It is the slower route on purpose.
Choose the next step
Create an account, or scope an enterprise pilot.
Individual and Business go straight through the account journey. Enterprise starts with one bounded delivery flow and explicit operating terms.