Commercial model
Pricing built for enterprise rollout, not generic plan pages.
Naneware pricing is structured around module families, operational scope, integration depth, governance needs, and support expectations across products and solutions.
Scoped around environments, integrations, transaction volume, and governance requirements.
Packaging supports phased rollout across products, solutions, and support commitments.
Platform modules, solution delivery, and production support can be scoped together or independently.
What is priced
Commercial scope follows the operating model
Pricing reflects the live platform surface: modules, environments, volumes, governance needs, admin coverage, and the amount of delivery or support Naneware is expected to own.
How teams start
Most programs begin with a foundation bundle
The typical first step is an identity and gateway foundation, then payment, workflow, analytics, or evidence modules are added according to the real service model rather than a predefined upsell ladder.
What grows price
Governance and rollout complexity matter
Costs usually move when integrations multiply, environments expand, support posture tightens, or audit, privacy, and evidence requirements become central to the operating model.
Foundation modules
Identity and trust foundation
Typical starting package for organizations that need gateway control, OIDC, MFA, onboarding, session governance, and admin identity operations before adding deeper workflows.Included surfacesNane Gateway • Nane Auth • Admin identity zone
Transaction modules
Money movement and service operations
Scoped around wallets, collections, disbursements, approvals, reminders, notifications, and workflow choreography for finance-heavy or service-heavy operations.Included surfacesNane Pay • Nane Notify • Nane Workflow • Nane Schedule
Review-ready controls
Governance and evidence layer
Used when the commercial scope must cover evidence retention, document lifecycle, privacy posture, export, forensics, and audit-backed reviewability from the start.Included surfacesNane Vault • Nane Audit • Admin audits zone
Operational insight
Analytics and secure discovery
Added when teams need KPI reporting, anomaly detection, archived reports, embedded insights, or permission-filtered search across platform artifacts and operational data.Included surfacesNane Lytics • Nane Search
Products
Platform modules priced by operating scope.
Products are typically packaged by module family, environment posture, tenant model, transaction profile, evidence requirements, and admin control expectations.
Custom quote
Nane Gateway
Tenant-aware edge routing, auth enforcement, rate limiting, and service orchestration at the control-plane boundary.
View productCustom quote
Nane Auth
IAM, OIDC, MFA, onboarding, device trust, and policy-aware access for regulated operating environments.
View productCustom quote
Nane Pay
Wallets, collections, disbursements, approvals, and callback-driven payment operations in one governed flow.
View productCustom quote
Nane Vault
Secure documents, evidence sealing, WORM retention, OCR and verification, and controlled retrieval across services.
View productCustom quote
Nane Notify
Email, SMS, push, webhook, and in-app delivery for transactional messaging, alerts, and escalations.
View productCustom quote
Nane Audit
Forensic audit ingestion, integrity verification, retention, compliance reporting, export, and lifecycle alerting.
View productCustom quote
Nane Lytics
Cross-service analytics, anomaly detection, reporting, and embedded insights backed by Kafka-driven ingestion.
View productCustom quote
Nane Workflow
Approval orchestration, SLA automation, event choreography, and service-task execution across the platform.
View productCustom quote
Nane Schedule
Bookings, reminders, and calendar-aware scheduling for service operations and customer-facing workflows.
View productCustom quote
Nane Search
Permission-filtered indexing and retrieval so teams can search across services without breaking access boundaries.
View productSolutions
Delivery solutions scoped by execution complexity.
Solution pricing usually reflects discovery, integration boundaries, rollout milestones, data movement, change management, and production-readiness requirements.
Engagement scope
Platform implementation
End-to-end rollout for identity, payments, messaging, workflow, analytics, and governance modules with production-readiness gates.
View solutionEngagement scope
Integration architecture
API design, gateway policy, tenant-aware edge patterns, eventing, and cross-service orchestration for real operating stacks.
View solutionEngagement scope
Workflow automation
Approval flows, SLA rules, event choreography, escalation logic, and operational policy automation across teams and services.
View solutionEngagement scope
Operational governance
Auditability, evidence retention, compliance reporting, admin governance, and enterprise operating controls that stand up in review.
View solutionImplementation support
Launch and operator enablement
Best for teams adopting Naneware for the first time and needing discovery, rollout sequencing, configuration, operator training, and go-live support.
Production operations
Run with structured support
Best for active environments that need agreed response posture, environment support, release coordination, and regular governance review.
Mission-critical posture
High-governance operating model
Best for high-volume or evidence-sensitive programs that need tighter support expectations, review-ready controls, and closer operational coordination.
Pricing FAQs
Questions teams ask before commercial scoping.
Naneware is positioned for enterprise delivery, so pricing is scoped around module families, environments, integration depth, governance requirements, transaction profile, and support expectations rather than flat self-serve plans.
Next step
Start with the right conversation.
Use the demo flow for platform walkthroughs, the contact flow for commercial scoping, or support if you are already operating Naneware environments and need production help.