Diana Pricing and Economic Model
The economics of Diana are intentionally structured around two separate components:
- The Diana Platform (Infrastructure Layer)
- AI Token Consumption (Intelligence Layer)
Separating these two components allows Diana to maintain transparent pricing, sustainable economics, and flexibility as the AI infrastructure market evolves.
1. The Diana Platform
Modern software teams typically rely on a stack of tools that includes:
- Code repositories (GitHub / GitLab)
- Task and project management systems (Jira, Linear, Trello)
- CI/CD infrastructure
- Hosting environments
- Storage and artifact management
In practice, these services usually cost between $300 and $500 per month per project, often across several providers.
Diana consolidates these capabilities into a single integrated environment designed specifically for AI-assisted software development.
The base platform includes:
- Repository management
- Task and project management
- CI/CD pipelines
- Application hosting
- 200 GB of storage
- 8 GB of RAM allocated to the production environment
The goal of Diana is not simply to replicate existing tools, but to integrate them into an environment optimized for AI-driven development workflows.
2. AI Token Consumption
Unlike traditional SaaS products, AI systems require computational resources that vary depending on how intensively the system is used.
To make usage predictable, Diana offers token consumption packages.
The base allocation includes:
- 8 million tokens per month
This was designed based on a realistic developer workflow.
A typical development session may consume approximately:
- 8,800 tokens per hour
Assuming a focused 8-hour development window, this represents:
- 70,400 tokens per working day
Under these assumptions, a well-managed project can comfortably operate within the base allocation.
However, workloads can vary significantly depending on the tasks performed, such as large refactors, architecture reviews, or security audits.
Market Reality: AI Token Pricing Volatility
Our internal analysis revealed an important market dynamic.
Many AI providers are currently subsidizing token usage as part of aggressive market acquisition strategies.
In some extreme cases, providers are effectively subsidizing up to 90% of the computational cost.
While this temporarily lowers prices across the industry, it creates significant long-term uncertainty for companies building products on top of these APIs.
For this reason, Diana will not subsidize token consumption.
Instead, Diana will implement transparent and sustainable models for token usage.
Token Consumption Models
Diana will support multiple models for token consumption depending on the needs of the customer.
Option 1 — Bring Your Own AI Key (BYOK)
Customers provide their own API key from providers such as Anthropic or OpenAI.
Advantages:
- Full transparency in AI costs
- No markup on tokens
- Eliminates pricing risk for Diana
This option is particularly attractive for technical teams and enterprise environments.
Option 2 — Managed Tokens (Cost + Margin)
Diana can also manage token consumption on behalf of the customer.
In this case, tokens are billed at cost plus a 15–20% margin to cover orchestration and infrastructure overhead.
This model simplifies billing while maintaining transparency.
Option 3 — Diana Native Models (Long-Term Strategy)
As the platform evolves, Diana may operate its own specialized models optimized for software engineering workflows.
This would allow:
- Deeper integration with development workflows
- Specialized training for code analysis
- Greater independence from third-party pricing volatility
However, operating proprietary models requires significant infrastructure investment and is therefore considered a long-term strategic direction.
Enterprise Pricing Strategy
Given the dependency on external model providers and the potential volatility of AI costs, Diana will focus primarily on a value-based enterprise model rather than competing on subsidized AI usage.
Diana is positioned not simply as a development tool, but as an AI-powered engineering contributor inside the team.
In many organizations, hiring a senior developer through a BPO strategy costs approximately:
- $7,000 USD per month
This cost does not include the additional infrastructure and tools required for that developer to operate effectively.
Diana replaces several of those tools while simultaneously increasing the productivity of the development team.
Based on this positioning, Diana's enterprise platform will be offered in the following tiers:
| Plan | Monthly Price | Projects Included |
|---|---|---|
| Starter Enterprise | $2,000 USD | Up to 1 project |
| Growth Enterprise | $5,000 USD | Up to 3 projects |
| Scale Enterprise | $8,000 USD | Up to 5 projects |
For organizations managing larger portfolios, Diana will offer tailor-made deployments, with additional project capacity available at:
- $2,000 USD per additional project
These custom deployments may also include dedicated infrastructure environments implemented with Diana's infrastructure partners.
This approach allows Diana to scale naturally alongside the engineering footprint of the company.
Diana CLI for Individual Developers
Alongside the enterprise platform, Diana will also offer Diana CLI as an individual developer tool.
This version is designed for:
- Independent developers
- Small teams
- Engineers who want to use Diana within their existing infrastructure
Pricing for Diana CLI will range between:
- $200 – $500 USD per month
Token consumption in the CLI will operate through a rebuy model, where developers purchase additional tokens as needed.
Diana will apply a 20% margin on token top-ups to cover infrastructure orchestration and operational costs.
Strategic Focus
While the CLI provides value to individual developers, the primary strategic focus of Diana will remain the enterprise platform.
Enterprise deployments generate the greatest economic impact and provide the most stable long-term business model.
By positioning Diana as a scalable engineering contributor rather than simply a tool, the platform aligns directly with the economic realities of modern software teams.
Organizations are not purchasing tokens or infrastructure.
They are investing in:
- Increased engineering output
- Reduced security risk
- Faster development cycles
- Simplified tooling infrastructure
In this context, Diana becomes not just another tool in the stack, but a productive member of the engineering team.