Which .NET Viewer License Do You Really Need? A Complete Guide
Which .NET Viewer License Do You Really Need? A Complete Guide
When you finally ship a clean, version‑controlled API, the next hurdle is often the documentation viewer. The feature set is usually spot‑on, but the licensing model can be a hidden snag that stalls adoption across teams, partners, or customers.
In this article we demystify the three core licensing options for the Doconut .NET documentation viewer—Developer, Site, and SDK—and give you a practical decision‑making framework so you can select the right plan the first time.
Table of Contents
- Why Licensing Matters for API Docs
- The Developer License – Ideal for Small Teams
- The Site License – Scaling Documentation Across Portals
- The SDK License – Embedding the Viewer in Your Own Product
- Decision Matrix: Quick Checklist
- Final Thoughts & Next Steps
Why Licensing Matters for API Docs {#why-licensing-matters-for-api-docs}
- Compliance: Incorrect licensing can trigger audit flags and unexpected fees.
- Performance: Certain plans unlock advanced rendering pipelines (OpenAPI 3.0, Swagger, RAML) and real‑time collaboration that keep docs snappy.
- Scalability: As your organization grows, the cost model should evolve without forcing a complete re‑architect of the documentation pipeline.
Choosing the wrong license not only inflates costs but can also limit capabilities—such as Git sync across repositories, role‑based editing, or white‑label branding—critical for modern DevOps workflows.
The Developer License {#the-developer-license}
Who Should Consider It?
- Solo developers or small squads (1‑5 engineers) building an internal tool or a proof‑of‑concept.
- Teams that need just one viewer instance embedded in a single application.
- Projects where the documentation is tightly coupled to a single codebase.
Core Features
| Feature | What It Means for Your Project |
|---|---|
| Native API spec rendering | Supports OpenAPI, Swagger, RAML out‑of‑the‑box with full syntax highlighting. |
| Live collaborative editing | Real‑time co‑authoring limited to one project; ideal for quick iteration. |
| Unlimited searchable docs | Indexes all markdown, HTML, or YAML files within the project for instant lookup. |
| Git sync | One‑to‑one repository sync—push changes, pull updates, and keep version history in line with code. |
Pricing Snapshot
- $199 per developer per year (flat fee).
- No per‑seat or per‑instance surcharges.
When to Walk Away
If you anticipate:
- Multiple documentation sites (customer portals, external partner docs), or
- Scaling beyond a single repository,
the Developer License will quickly become a cost bottleneck.
Analogy: Think of it as a single‑serve coffee pod—perfect for one cup, but you’ll need a whole machine for a bustling office.
The Site License {#the-site-license}
Who Should Consider It?
- Enterprise teams that run several internal tools, public API portals, or a knowledge base accessed by hundreds of users.
- Companies needing consistent branding and unified access control across all documentation touchpoints.
Core Features
| Feature | Benefit |
|---|---|
| Unlimited viewer instances | Deploy the viewer on any number of web sites, intranets, or SaaS portals. |
| Centralized license management | Dashboard to assign, revoke, and audit licenses across the organization. |
| Team‑wide live editing with RBAC | Fine‑grained roles (author, reviewer, admin) enforce governance. |
| Multi‑repo Git integration | Connect monorepos or disparate repos and keep every doc set in sync. |
| Priority support & SLA | 24‑hour response window, guaranteeing minimal downtime. |
Pricing Snapshot
- Base: $4,999 per year for up to 20 sites.
- Additional sites: $250 per site per year.
When It Pays Off
- You operate a public developer portal that needs to stay in sync with production APIs.
- Your internal knowledge base is a single point of truth for dozens of teams.
- The cost of manual documentation updates outweighs the subscription fee.
Analogy: It’s the jump from a single‑car garage to a full‑size parking lot—room to scale without pulling over each time.
The SDK License {#the-sdk-license}
Who Should Consider It?
- Vendors building commercial products that embed the .NET viewer (e.g., desktop IDEs, cloud consoles, on‑premise platforms).
- Teams that require white‑labeling and full source access to tailor the viewer to their brand.
Core Features
| Feature | What It Unlocks |
|---|---|
| Full source access | Modify rendering pipeline, UI components, or integrate proprietary authentication. |
| Unlimited distribution | Ship the viewer to any number of end‑user installations without per‑seat fees. |
| White‑labeling | Remove Doconut branding, apply custom themes, and control the look‑and‑feel. |
| Dedicated technical account manager | Direct line for integration guidance, performance tuning, and roadmap alignment. |
Pricing Snapshot
- One‑time fee: $12,499 for perpetual rights.
- Optional maintenance: $2,999 per year (covers updates, security patches, and support).
When It’s the Right Choice
- Your product’s value proposition hinges on in‑app documentation (e.g., a Visual Studio extension that shows API spec inline).
- You need unrestricted distribution—the viewer travels with every copy of your software.
- Brand consistency and source‑level customization are non‑negotiable.
Analogy: Buying the engine block for your own car—expensive upfront, but you own the powertrain outright and can drive as far as you like.
Decision Matrix: Quick Checklist {#decision-matrix}
| Question | Recommended License | Why |
|---|---|---|
| How many distinct places will the viewer appear? | Developer → 1‑2 locations Site → 3+ locations | Site License removes per‑instance limits. |
| Do you need to ship the viewer to end‑users? | SDK | Unlimited distribution and white‑labeling. |
| Is branding or source‑code access required? | SDK | Full source access and brand removal. |
| What is your preferred cost model? | Developer → annual per‑seat Site → annual site‑wide SDK → one‑time upfront | Aligns with budgeting cadence. |
Tip: Keep this matrix handy in a project brief or sprint planning document; it quickly surfaces the right license without the need for back‑and‑forth with sales.
Final Thoughts & Next Steps {#final-thoughts}
Choosing the correct .NET viewer license is not a “one‑size‑fits‑all” decision. It rests on three pillars:
- Scope of deployment – single app vs. multiple portals vs. product integration.
- Distribution requirements – internal use only or bundled with a commercial offering.
- Budget cadence – recurring annual spend vs. an upfront capital investment.
By aligning your team’s workflow, growth trajectory, and financial constraints with the features listed above, you can avoid costly license upgrades down the line and keep documentation flowing smoothly.
Ready to lock in the right license?
- Visit doconut.com/pricing and use the interactive selector.
- Download the License Selector Worksheet to map your answers from the decision matrix.
- If you need a deeper dive, schedule a 15‑minute design call with our solutions engineers for a live demo of collaborative editing, API spec rendering, and Git sync.
Happy documenting, and may your APIs be as well‑served as your license!