LogoLogo
Github
  • 🚀Getting Started
    • About Jugalbandi Manager
  • Introduction
    • About OpenyAI
    • What is Jugalbandi?
    • Why dive in: How will this playbook help you?
    • Importance and Relevance of Jugalbandi
    • Key Principles powering Jugalbandi
    • Demystifying Jugalbandi: What Jugalbandi isn’t?
  • Breaking Down Jugalbandi's Anatomy
    • Jugalbandi Manager: Your companion for building and managing AI services
    • Jugalbandi’s Key Services
    • Key Features for Enhancing Security and Privacy
  • Building with Jugalbandi
    • Technical Guide
      • explanations
        • JB Manager Architecture
        • Explanations
      • how-tos
        • Local Development
        • Write Your Own Bot
        • How to Guides
      • references
        • Dependencies
        • FSMOutput
        • References
        • Speech and Translation
        • Azure Storage
        • Whatsapp
        • Telegram
        • example-grievance-bot
          • Example Grievance Bots
      • tutorials
        • Tutorials
        • Quickstart
    • Getting Started
    • Local Development / Writing your own bot
    • Dependencies
    • Configuring the FSM to modify flows
    • Cost of building with Jugalbandi
    • Tips and Best Practices / FAQs (Including best practices for creating a knowledge base)
  • Use cases of Jugalbandi
    • Jugalbandi for Access to Legal Information
    • Jugalbandi for Govt. Schemes
    • Accessing Legal Services
    • Jugalbandi for Grievance Redressal
    • Climate Action with Wildlife First
    • Affordable Housing with Bandhu
    • Paralegal Services with Nyaya Mitra
    • UNESCO X Jugalbandi
  • Is Jugalbandi Manager Applicable to your Use case?
    • The versatile applications of Jugalbandi
    • Some other example use cases
  • Possibilities and Future Directions
    • Potential Technological Advancements
    • Jugalbandi Studio: Building with AI has never been more accessible
  • Community and Collaboration
    • Understanding the community-led spirit of our mission
    • Our current collaborators and community
  • Get Involved
    • How can volunteers contribute?
    • How can maintenance of the stack be open-sourced?
    • Technical Support and Contact Information
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Building with Jugalbandi

Cost of building with Jugalbandi

PreviousConfiguring the FSM to modify flowsNextTips and Best Practices / FAQs (Including best practices for creating a knowledge base)

Last updated 9 months ago

Was this helpful?

Accessing the Jugalbandi stack is and will remain free, through the project’s GitHub To be able to utilise the stack to build and offer solutions, any individual or organisation needs to consider the cost of operating the application and the associated data & infrastructure.

The key considerations in budgeting for a conversational service is as follows:

  1. Estimating the usage and plan to scale

  • The amount of people using the service, how often they use it and the complexity of their queries will determine the associated costs of the cloud infrastructure and services that will be required for solutions such as Jugalbandi to operate

  • For example, if 100 users send 30 messages each day, an estimated ₹656 per month would have to be budgeted for processing these messages using LLMs such as GPT-4o mini or 3.5.

  • Start small and add more resources as needed. This helps control costs and scale efficiently.

  • Depending on the nature of the use case, cloud service providers are known to offer negotiated contracts to access their services at subsidised rates.

  1. Monitoring data transfer and storage needs

  • Calculate how much data will need to be stored including user data, message logs and media files. This should also include the costs of encrypting and masking sensitive information.

  • The data in and out of cloud services, would have to be routinely monitored in accordance with the regional regulations on data protection and privacy.

  1. Human Resources

  • Depending on the complexity of the use case, data scientists, data engineers and full stack developers may be needed to implement the solution as per the requirements.

  1. Communication Costs

  • Based on the medium of communication with users, there may be additional costs incurred through third party service providers.

  • While the exact cost will vary based on the chosen service provider, at an estimated Rs. 0.3 per session, the same example from above of 100 users sending 30 messages a day would cost an additional ~Rs. 1000 a month over whatsapp.

The following table indicates the costs associated with deploying and operating a platform with Jugalbandi manager:

Cost Category
Service Required
Indicative Cost (as of July 2024, and all costs are subject to the terms of the service provider)
Notes

Cloud Infrastructure

Compute

~Rs. 10 per hour per VM

Running compute resources. The cost will vary based on usage

Storage

~Rs. 2 per GB

Storing user data and media. Estimated: ₹166.71 per month (assuming 100 GB)

Event Hubs for Kafka

~Rs. 120 per processing hour

Queue management for messaging between the various services of the platform.

Vector Databases

~Rs. 25 per hour

Scalable databases for AI models

Landing Zones

Can vary based on the chosen service providers

A one-time cost for the initial setup of cloud resources

Embedding Models

₹0.008336 to ₹0.010836 per 1000 tokens

Creating chunks of the provided knowledge bases to be consumed by AI models

Speech Processing

₹83.35 to ₹1,250.27 [per million characters or audio hours]

Converting speech to text, text to speech, and processing text.

LLMs

GPT-3.5 Turbo Tokens

₹0.125 (Input) + ₹0.167 (Output) per 1000 tokens

Processing user messages for AI responses. Estimated: ₹656 per month for a 100 users with 30 messages each

Technical implementation team: Data Scientists, Data Engineers & Full-Stack Devs

Whatsapp/Communication Channel Integration and Communication Services

Data handling, transfer, security and compliance costs

repository.