Innovate. Connect. Empower.
Making advanced technology accessible from small villages to global cities.

Centre for Information Technology India (CITI) is a growing technology organization founded in October 2022 by Amaan Ahmad (Founder & CEO). Inspired by real-world IT service operations, we build practical, scalable solutions that bridge digital divides and empower institutions, local businesses, and emerging developers.

We believe that meaningful innovation is not about hype—it’s about delivering accessible, secure, and purposeful technology.

Make modern technology intuitive, affordable, and impactful for everyone—rural entrepreneurs, schools, creators, and developers.

A connected ecosystem where localized innovation meets global standards—fueling economic and educational uplift through open, secure, AI-driven digital infrastructure.

Innovate. Connect. Empower.

• Artificial Intelligence (LLMs, agentic tools, AI-assisted workflows)
• Web3 (smart contracts, Solana-based challenge & reward systems)
• Application & Infrastructure Security
• Automation & Bots (operational augmentation)
• Full-Stack Engineering (TypeScript / Python / Rust / Go depending on project)
• Gamified Learning & Esports Platforms

We emphasize pragmatic adoption over trend-chasing. Every tool must justify its operational and user impact.

AI-driven assistant for local businesses to build marketing strategies, campaign outlines, and customer engagement flows using structured prompts and Google Gemini integration.

Key Concepts:

• AI-generated campaign briefs
• Localization-aware recommendations
• Extensible plugin layer (planned)

A Web3-powered coding challenge platform built on Solana.

• On-chain reward distribution
• Verifiable contribution metrics
• Competitive + educational environment
• (Roadmap) Anti-cheat + integrity scoring

Want to contribute? See “Contributing” below.

1. Accessibility First (UI clarity > feature noise)
2. Security by Default (threat modeling before feature rollout)
3. Modularity & Extensibility (plugin-oriented internal services)
4. Observability (logs, metrics, traces before scale)
5. Open Collaboration (transparent roadmaps and issue-first planning)

Planned High-Level Stack (Example)
 ┌───────────────────────────────────────────┐
 |              Frontend (Web)              |
 |  Next.js / React / Tailwind / Vite       |
 └──────────────┬───────────────────────────┘
                │
 ┌──────────────▼───────────────────────────┐
 |            API / Service Layer           |
 | FastAPI / Express / tRPC / gRPC          |
 | Auth, AI Orchestration, Business Logic   |
 └──────────────┬───────────────────────────┘
                │
 ┌──────────────▼───────────────────────────┐
 |        AI + Automation Components        |
 | Prompt Pipelines / Vector Search / LLMs  |
 | Gemini / Open Source Models / RAG        |
 └──────────────┬───────────────────────────┘
                │
 ┌──────────────▼───────────────────────────┐
 |      Web3 Layer (CodeCup Specific)       |
 | Solana Programs / Wallet Integration     |
 └──────────────┬───────────────────────────┘
                │
 ┌──────────────▼───────────────────────────┐
 |         Data & Persistence Layer         |
 | Postgres / Redis / S3 / IPFS (selective) |
 └───────────────────────────────────────────┘

We welcome engineers, designers, security researchers, educators, and growth collaborators.

1. Browse open issues (good first issue labels coming soon).
2. Propose enhancements via RFC-style discussion (create a discussion or issue template).
3. Fork → Branch → PR (ensure tests & lint pass).
4. Security issues: DO NOT open a public issue. Email us (see below).

Planned Labels:

• status:needs-triage
• type:feature / type:bug / type:security
• good-first-issue
• help-wanted
• blocked / in-progress

We prioritize secure development lifecycles.
If you discover a vulnerability:

• Email: [email protected]
• Provide reproduction steps, impact summary, and suggested mitigation.
• We will acknowledge within 72 hours (update this SLA if needed).

Add the popular metrics after creating repositories:

![GitHub Org Stats](https://github-readme-stats.vercel.app/api?username=Centre-for-Information-Technology-India&show_icons=true&orgs=Centre-for-Information-Technology-India)
![Top Languages](https://github-readme-stats.vercel.app/api/top-langs/?username=Centre-for-Information-Technology-India&layout=compact&langs_count=8)

Or use:

• https://github.com/anuraghazra/github-readme-stats
• https://github.com/lowlighter/metrics

(Adjust dates once internal planning is finalized.)

Create a .github repository (this one) for shared workflows, ISSUE_TEMPLATEs, and FUNDING.yml.

• CODE_OF_CONDUCT.md
• CONTRIBUTING.md
• SECURITY.md
• FUNDING.yml (if donations/patronage planned)
• ISSUE_TEMPLATE / PULL_REQUEST_TEMPLATE
• Dependabot configuration (dependency security)
• GitHub Actions:
  • CI (lint + test)
  • SAST (CodeQL)
  • License scanning
  • Auto-label (triage bot)

• Practical Innovation > Flashy Hype
• Reliability & Trust > Velocity Alone
• Continuous Learning & Mentorship
• Inclusion Across Languages & Regions
• Ethical Use of AI & Data

• Star the repos you like to support visibility
• Open an issue with an idea or problem
• Share feedback on early prototypes
• Join community discussions

You can help us build technology that genuinely reaches underserved audiences.

Different projects may adopt different licenses (e.g., MIT for libraries, AGPL for platform services, proprietary for internal tooling).
Each repository includes its own LICENSE file—review before contributing.

• Replace all placeholder domains/emails
• Add banner + logo images
• Confirm badges render correctly
• Trim roadmap to publicly-safe items
• Link actual repos once created
• Add real metrics widgets

Built with intention. Maintained with integrity. Focused on impact.

_{© 2022–Present Centre for Information Technology India. All rights reserved.}