Pricing that reflects how you deploy
Aveya is priced by deployment model and rollout scope, not by document count or per-query pricing. Many teams start with a pilot, then move into a managed or private deployment once value is proven.
How pricing works
- Deployment model: Managed or Private
- Rollout scope: users, teams, and integrations
- Support level: standard or priority
Procurement documentation (DPA, subprocessors, security pack) available on request. USD pricing available for US and international engagements.
Three ways to get started
Most teams begin with a pilot, then move into Managed Deployment or Private Deployment once value is proven.
Recommended start
Design Partner Pilot
A fixed-scope engagement to prove value on real documents, workflows, and deployment conditions. Designed to convert into Managed Deployment or Private Deployment.
NZD $15k–$25k
Fixed scope · 4–8 weeks
- Defined use case and measurable success criteria
- Knowledge and deployment configuration for your environment
- Security pack and procurement support included
- Rollout path agreed before pilot closes
Pilot converts to Managed Deployment or Private Deployment after the engagement. Scope is agreed upfront.
Managed Deployment
Aveya-hosted. Fastest path to value for teams that want governed intelligence without managing infrastructure.
NZD $2.5k / month
Typical mid-market: NZD $5k–$8k / month
- Tenant isolation and role-based access control
- Evidence-backed outputs with source visibility
- Standard support and monitoring
- Clear path to Private Deployment later
Best when security requirements do not require customer-tenant deployment. Migration to Private Deployment can be scoped later.
Private Deployment
Runs inside your Azure tenant. Best for regulated environments and organisations that need full control over identity, networking, and data residency.
NZD $5k / month
+ implementation from NZD $20k · Azure infrastructure billed to your subscription
- Runs in your Azure tenant
- Identity and network remain under your control
- Data residency and security posture aligned to your standards
- Enterprise rollout and security review support
Platform subscription covers licensing and support. Azure infrastructure is billed directly to the customer's Azure subscription. Typical Azure costs: NZD $1.5k–$4k / month depending on usage.
What affects the price
Pricing is scoped to your rollout, not forced into rigid tiers that do not reflect how enterprise deployments actually work.
Primary factors
- Deployment model
- Rollout size
- Solution scope
- Support level
Scoped separately
- Custom connectors and advanced integrations
- Bespoke networking or security architecture
- Dedicated success management
- Azure infrastructure for Private Deployment
Implementation & rollout
Pilots and Private Deployments include an implementation phase. Managed Deployment can start quickly, with implementation available where needed.
What's included
- Environment setup and deployment
- Knowledge source connection and configuration
- Access controls and identity integration where required
- Success criteria and rollout plan agreed upfront
Scope is confirmed before work starts. No surprise additions.
Typical timelines
- Pilot: 4–8 weeks
- Managed Deployment: days to start, implementation optional
- Private Deployment: 2–6 weeks depending on networking, identity, and review depth
Common questions
Do you charge per document or per query?
Pricing is based on deployment model and rollout scope, not document count or per-query billing.
Do you train models on our data?
No. Customer data is used for retrieval and reasoning, not to train Aveya or third-party foundation models.
Can we start on Managed and move to Private later?
Yes. Many teams start on Managed, then migrate later as security and governance requirements mature.
Is pricing available in USD?
Yes. NZD is shown publicly, but USD pricing is available for US and international engagements.
Do you provide a DPA and subprocessor list?
Yes, as part of evaluation or pilot/procurement review.
Who pays for Azure infrastructure on Private?
Azure costs are billed directly to the customer's subscription and estimated during scoping.
Want a straight answer on cost?
Share your use case, deployment preference, and rough rollout size. We'll reply with a realistic range.