Update service licensing documentation for CD V3.0 model - custom stage execution changes

[thisrohangupta]

Documentation Update for Licensing V3

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

• Please describe your changes: __________________________________
• Jira/GitHub Issue numbers (if any): ______________________________
• Preview links/images (Internal contributors only): __________________

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

• Successful preview build.
• Code owner review.
• No merge conflicts.
• Release notes/new features docs: Feature/version released to at least one prod environment.

[thisrohangupta]

Summary

Updates the CD service licensing documentation to reflect the new V3.0 licensing model changes, specifically focusing on the enhanced custom stage execution tracking.

Key Changes Made

🚀 V3.0 Model Features

• Custom Stage Aggregation: Implemented pooled execution model (2000 executions = 1 service license)
• Enhanced Documentation: Added dedicated V3.0 section explaining improvements
• Customer Migration Info: Clear guidance on automatic V3.0 migration

📊 Updated Content Sections

• "Pipelines with no Service": Updated to explain V3.0 aggregation approach
• Service Tracking Table: Modified to show V2 → V3.0 evolution
• Customer FAQs: Added V3.0-specific questions and answers
• Migration Details: Added seamless transition information

💰 Business Impact

• Cost Predictability: Eliminates unexpected license spikes
• Fair Usage Model: Aligns billing with actual platform value
• Customer Benefits: Typically reduces license consumption for custom stage users

Technical Details

• Maintains all existing functionality and performance
• No configuration changes required for customers
• Automatic migration from V2 to V3.0
• Backward compatibility preserved

Documentation Quality

• ✅ Clear examples with specific numbers
• ✅ Customer-focused FAQ section
• ✅ Consistent formatting and style
• ✅ Technical accuracy verified

Type of Change

• Documentation update
• Feature enhancement documentation
• Bug fix
• Breaking change

Checklist

• Documentation follows existing style guidelines
• All technical details are accurate
• Customer impact clearly explained
• Examples are helpful and realistic
• FAQ addresses common concerns
• Migration information is clear

Related Work

This documentation update supports the V3.0 licensing model launch and should be coordinated with:

• Sales team communication rollout
• Customer success team training
• Product marketing messaging

[bot-gitexp-user]

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://686599506d4f6b0c6901cd4d--harness-developer.netlify.app